tabby-connection-gateway icon indicating copy to clipboard operation
tabby-connection-gateway copied to clipboard

Error 426 Upgrade Required

Open dnviti opened this issue 2 years ago • 3 comments

version: '3.9'
services:
  tabby-gateway:
    container_name: tabby-gateway
    image: ghcr.io/eugeny/tabby-connection-gateway:master
    environment:
      - TABBY_AUTH_TOKEN=<token>
      - HOST=0.0.0.0
      - PORT=9000
    command: "--token-auth --host 0.0.0.0"
    networks:
      - devops-stack-net

networks:
  devops-stack-net:
    name: devops-stack-net
    external: true

When i set the token in the application it does not work, gives me thie error: image

Logs

INFO:server:Token auth enabled
INFO:GatewayServer:Listening on 0.0.0.0:9000
INFO:websockets.server:server listening on 0.0.0.0:9000
INFO:websockets.server:connection failed (426 Upgrade Required)
INFO:websockets.server:connection failed (426 Upgrade Required)
INFO:websockets.server:connection failed (426 Upgrade Required)
INFO:websockets.server:connection closed
INFO:websockets.server:connection closed
INFO:websockets.server:connection closed
INFO:websockets.server:connection failed (426 Upgrade Required)
INFO:websockets.server:connection failed (426 Upgrade Required)
INFO:websockets.server:connection closed
INFO:websockets.server:connection closed
INFO:websockets.server:connection failed (426 Upgrade Required)
INFO:websockets.server:connection closed
INFO:websockets.server:connection failed (426 Upgrade Required)
INFO:websockets.server:connection closed
INFO:websockets.server:connection failed (426 Upgrade Required)
INFO:websockets.server:connection closed
INFO:websockets.server:connection failed (426 Upgrade Required)
INFO:websockets.server:connection closed
INFO:websockets.server:connection failed (426 Upgrade Required)
INFO:websockets.server:connection closed
INFO:websockets.server:connection failed (426 Upgrade Required)
INFO:websockets.server:connection closed
INFO:websockets.server:connection failed (426 Upgrade Required)
INFO:websockets.server:connection closed

dnviti avatar Oct 10 '22 22:10 dnviti

I have the same problem...

GuilhermeLouback avatar Nov 29 '22 13:11 GuilhermeLouback

It happens to me too. I'm change de tabby version, try to use tabby-web self hosted, tabby installed on desktop, try different version and I can't use it. I tried to use tabby-connection-gateway without token, I receive 426 upgrade Required.

denisprovsolutions avatar Apr 14 '23 13:04 denisprovsolutions

The same problem occurs when trying to use, my solution is as follows:

  1. nginx enables ssl http2,
  2. the token of tabby-connection-gateway uses 9 characters nginx config:
server {
        listen 80;
        server_name tabbygateway.mydomain.com;
        access_log /var/log/nginx/tabbygateway.static.a.log;
        error_log /var/log/nginx/tabbygateway.static.e.log;
        return 301 https://$server_name$request_uri;
}
server {
        listen 443 ssl http2;

        server_name tabbygateway.mydomain.com;
        access_log /var/log/nginx/tabbygateway.static.a.log;
        error_log /var/log/nginx/tabbygateway.static.e.log;

        add_header Strict-Transport-Security "max-age=31536000; includeSubDomains; preload" always;
        add_header X-Frame-Options SAMEORIGIN;
        add_header X-Content-Type-Options nosniff;

        ssl_certificate  /etc/nginx/cert/tabbygateway.mydomain.com.pem;
        ssl_certificate_key  /etc/nginx/cert/tabbygateway.mydomain.com.key;
        ssl_trusted_certificate /etc/nginx/cert/tabbygateway.mydomain.com.ca;
        ssl_session_timeout 5m;
        ssl_ciphers ECDHE-RSA-AES128-GCM-SHA256:ECDHE:ECDH:AES:HIGH:!NULL:!aNULL:!MD5:!ADH:!RC4;
        ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
        ssl_prefer_server_ciphers on;

        keepalive_timeout   70;
        ssl_session_cache   shared:SSL:10m;
        ssl_session_tickets on;
        ssl_stapling        on;
        ssl_stapling_verify on;

        location / {
                proxy_set_header Host $host:$server_port;
                proxy_set_header X-Real-IP $remote_addr;
                proxy_set_header X-Forwarded-Proto $scheme;
                proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
                proxy_pass http://tabbygateway:9000;
                proxy_http_version 1.1;
                proxy_set_header Upgrade $http_upgrade;
                proxy_set_header Connection "upgrade";
        }
}

my tabby-connection-gateway docker-compose config:

  tabbyweb:
    container_name: tabby-web
    image: xxxx/tabby-web:latest
    restart: always
    depends_on:
      - mariadb
      - tabbygateway
#    ports:
#      - 9090:80
    environment:
      - DATABASE_URL=mysql://xxxx:xxxxx@mariadb/tabby
      - PORT=80
      - DEBUG=False
      - DOCKERIZE_ARGS="-wait tcp://xxx:3306 -timeout 60s"
      - SOCIAL_AUTH_GITHUB_KEY=12faea7e3
      - SOCIAL_AUTH_GITHUB_SECRET=eb0cff1c
    # - APP_DIST_STORAGE="file:///app-dist"
    networks:
      - db_network
  tabbygateway:
    container_name: tabby-gateway
    image: xxxx/tabby-connection-gateway
    environment:
      - TABBY_AUTH_TOKEN=tabby12345678
    command: --token-auth --host 0.0.0.0
    networks:
      - db_network

shmilyyan avatar Jul 09 '23 15:07 shmilyyan