On Thu, Dec 12, 2019 at 02:42:49PM -0500, Christopher Schultz wrote:
Matt,
On 12/12/19 13:43, Matt Thomas wrote:
Not sure if you have read the first post, or maybe i didnt add it, but i have tried port 22,5022,8022, 25565, 47506 and 443 haha.
It wasn't clear if you were changing the port number of the sshd service (on your server) or the port you had open on your firewall/router. I suspect that your ISP is blocking incoming connections to port 22. The port number you use for sshd on the server is not relevant.
Er... the server *is* running at his home; that was in the original post.
Matt, FWIW, I agree with what pepak@seznam.cz said in one of the first replies - you will most probably be able to wrap an SSH connection in a TLS connection managed by stunnel. Of course, this will require some additional setup on the client side, too - there will need to be another stunnel instance there that will accept "cleartext" traffic (actually SSH traffic from the SSH client) and send it to the stunnel server to "decrypt" (convert back into SSH traffic) and send to the SSH server locally.
G'luck, Peter