search

Eugeny / tabby-connection-gateway

Connection gateway for Tabby Web
https://tabby.sh
MIT License
116 stars 24 forks source link

connection issue while trying to ssh trough web interface #22

Closed TomErnst1972 closed 2 months ago

TomErnst1972 commented 2 months ago

Hi,

I successfully set up tabby-web and now wanted to host my own connection gateway. This is my docker command ad the error when I insert wss://my.internal.ip.address:9000 in the settings.

As soon as i try to open a ssh session on the same network, this happens:

[root@buildhost tabby-web]$ docker run -e TABBY_AUTH_TOKEN=redacted -p 9000:9000 ghcr.io/eugeny/tabby-connection-gateway:master --token-auth --host 0.0.0.0
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 (400 Bad Request)
INFO:websockets.server:connection closed
INFO:websockets.server:connection failed (400 Bad Request)
INFO:websockets.server:connection closed
INFO:websockets.server:connection failed (400 Bad Request)

any ideas or suggestions?

What is the exact URL for the connection gateway in tabby web? is above with an ipaddress right? Or can i add some debug settings to the docker command?

best regards, Tom

TomErnst1972 commented 2 months ago

found out myself: i used wss:// instead of ws://. after putting a reverse proxy in front of it with SSL Termination, i was able to set it up correctly.

when i tried with ws://ip.add.ress first, it gave me an error, when tabby-web was already being served via https. 

Failed to construct 'WebSocket': An insecure WebSocket connection may not be initiated from a page loaded over HTTPS.