[stunnel-users] My home ISP blocking ssh protocol

Peter Pentchev roam at ringlet.net
Thu Dec 12 22:13:50 CET 2019

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

Matt, FWIW, I agree with what pepak at 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


Peter Pentchev  roam@{ringlet.net,debian.org,FreeBSD.org} pp at storpool.com
PGP key:        http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint 2EE7 A7A5 17FC 124C F115  C354 651E EFB0 2527 DF13
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://www.stunnel.org/pipermail/stunnel-users/attachments/20191212/10719022/attachment.sig>

More information about the stunnel-users mailing list