Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

I get a connection error when opening SSH or Telnet with DDNSTO #173

Open
jiangjianghu opened this issue Sep 9, 2024 · 5 comments
Open

Comments

@jiangjianghu
Copy link

I can open the website, but I get an error when I click on Create SSH Connection, and I exit the configure SSH interface, which is also the case with telnet. Does anyone know why?
Sshwifty is disconnected from it's backend server: Error: Error: Connection is closed

@nirui
Copy link
Owner

nirui commented Sep 9, 2024

Hi,

Are you connecting directly to the Sshwifty instance or through a reverse proxy?

In the case of reverse proxy, it must support WebSocket in order to allow Sshwifty client (the web page) to connect with the server.

@jiangjianghu
Copy link
Author

Access is through a proxy, my host is in the LAN, ddnsto can access the website in the LAN through a domain name, but the websocket does not know whether it is supported

@nirui
Copy link
Owner

nirui commented Sep 9, 2024

Hi,

My guess is, if your reverse proxy is something like Nginx, then you need to enable WebSocket support on it as it's not usually enabled by default. Please take look: https://nginx.org/en/docs/http/websocket.html.

Though, other proxies such as Traefik may already has WebSocket enabled by default. In that case then maybe it's something else causing the problem. In such case I'll need more information in order to help you figure it out.

@jiangjianghu
Copy link
Author

I see, it may be the reason that ddnsto does not support websockets, so this may not be solved,

thank you

@nirui
Copy link
Owner

nirui commented Sep 9, 2024

I'm not really familiar with DDNSTO. Do they offer documentation or customer service for their users? Maybe you can inquire the company to see if they can help. WebSocket is fairly commonly used now days, makes no sense to not support it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants