I’ve correctly configured sshd to listen on port 1723, that is:
Apparently, see logs below, it gets to the point that a connection (a tcp connection) is established, but doesn’t get through on the ssh level.
I need it to listen on port 1723 because, on a network I use often, it is the only allowed port besides 80 and the server already listens on 80 for web connections. I have never configured a VPN (port 1723 is usually a VPN port) on this server.
Any ideas? Any chance this is a problem from DigitalOcean’s side? Something within sshd?
This is what I get from the outputs/logs after the connection times out:
$ ssh -vvv Connection established. ... ssh_exchange_identification: read: Connection reset by peer
Log: sshd[xxx]: Did not receive identification string from x.x.x.x Netstat: tcp 0 39 x.x.x.x:1723 y.y.y.y:44983 ESTABLISHED 23401/sshd: [accepted]
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.
Click below to sign up and get $100 of credit to try our products over 60 days!