Windows
Mac
Linux
HTTPS tunnels with
built-in Let's Encrypt certificates for web applications.
TCP tunnels for other applications.
TLS tunnels for end-to-end encryption.
Subdomain: Instantly
get persistent custom subdomains.
Custom domain: Use your own domains with built-in HTTPS
certificates.
Password authentication with HTTP Basic authentication.
Bearer token /
key based authentication.
IP whitelisting for restricted access.
Live debugger:
Inspect HTTP requests on the fly. View requests, responses, headers,
etc.
Header manipulation: Change HTTP request headers before they
arrive at your server.
USA
Europe
Asia
Make your developement experience smoother by unlocking the full potential of Pinggy.
Pinggy relies on SSH remote port forwarding. The option
-R 0:localhost:8000 in the command only implies
that connections to the public URL given by pinggy are
forwarded to your localhost:8000.
No other port than the one specified by you can be accessed by Pinggy or by anyone through the public URLs provided by Pinggy.
You can read more about the -R option of openssh
client
here. If you are using a different ssh client, then refer to its
documentation.
If the ssh command prompts you for a password you can just press enter (a blank password). Or you can type in something random and press enter.
ssh-keygen
a.pinggy.io is routed to the Pinggy server
nearest to your location. Currently we have our servers in
USA, Sweden, and Singapore.
Pinggy's free plan has a tunnel timeout of 60 minutes. If the tunnel is closed by you or reaches the time limit, starting a new tunnel will generate a new URL.
To obtain a permanent or persistent URL, or to use your own domain, you must subscribe to Pinggy Pro.
Yes. Current versions of Windows, Mac, as well as almost all Linux distributions come with openssh client pre-installed. Therefore Pinggy will just work out of the box.
To learn more about using Pinggy on Android read our blog post.
You can use TCP and TLS tunnels for free with Pinggy. Click on "Advanced Settings" on the top of the homepage, and select TCP.
Read our guide on long running tunnels here.
The most common reason for this is that an existing tunnel with the same token is active.
Terminate your existing tunnel with the same token. You can do so from the Active Tunnels option in the dashboard.
You can also use the Force option in the dashbaord.
Pinggy does read tunnel traffic for providing the Web Debugger feature.
Use TLS tunnels for Zero trust mode, where Pinggy cannot read your data. In this case your traffic is end-to-end encrypted.