Create TCP Tunnels with Pinggy

Create a tunnel using a single command.

This command present user with a URL and a TCP port. Port allocation changes per connection. However, one can reserve a port on https://dashboard.pinggy.io

TCP tunnel ssh -p 443 -R0:localhost:8000 tcp@free.pinggy.io
How a Pinggy TCP tunnel worksClients connect to a public TCP port. Pinggy forwards the bytes as they are through the encrypted SSH tunnel, so protocols with their own encryption, like SSH or a database over TLS, stay encrypted end to end.PRIVATE NETWORKYour machinePINGGY EDGEPinggy*.a.pinggy.linkINTERNETlocalhost:8000Your clientsssh, psql, rdpssh:443tcp:40527SSH, database, RDPbehind NAT or firewallpublic TCP portIP whitelistbytes pass as isconnect to host:portencrypted SSH tunnelyour bytes, as is How a Pinggy TCP tunnel worksClients connect to a public TCP port. Pinggy forwards the bytes as they are through the encrypted SSH tunnel, so protocols with their own encryption, like SSH or a database over TLS, stay encrypted end to end.PRIVATE NETWORKYour machinePINGGY EDGEPinggy*.a.pinggy.linkINTERNETlocalhost:8000SSH, database or RDPpublic TCP portYour clientsssh, psql, rdpbytes pass through as isssh :443tcp :40527encrypted SSH tunnelyour bytes, as is

Clients connect to a public TCP port. Pinggy forwards the bytes as they are through the encrypted SSH tunnel, so protocols with their own encryption, like SSH or a database over TLS, stay encrypted end to end.

To pass the client’s original IP address to your upstream service, see the HAProxy PROXY Protocol guide.

Specific SSH Guides

If you want to SSH into a specific operating system, check out our step-by-step guides: