This is a very good solution for HTTP(S) tunneling - which is the most frequently needed tunnel. However if you want to play a game, or use SSH, then Pinggy tunnels are very simple to use. One command:
ssh -p 443 -R0:localhost:443 tcp@free.pinggy.io
Disclosure: Co-founder of pinggy.io here.
Edit: I meant TCP tunnels, UDP tunnels, or also TLS tunnels for end-to-end encryption.
What kind of usage limits?
A free session runs for 60 seconds after which it has to be restarted and the address changes.
You can get the address with an API call.. but we charge for convenience. Pays the infra bills.
*60 minutes
i love this! never understood why a proxy app was needed
So you don't know my IP (DDoS target), and because of NAT.
I think tonymet meant he didn't understand why cloudflare didn't allow using ssh -R instead of cloudflared to create the tunnel, not not using a tunnel at all.
cloudflared is a bit unique in that it makes multiple outbound connections to CF DCs to do the tunneling and fails over if a DC has an issue (or, more likely, when a DC is near-capacity and they need to divert lower-tier traffic away from it[0]). SSH would reintroduce a single point of failure to this.
Also, the _main_ use case of `cloudflared` tunneling is using it as a long-term way to host production websites on your own hostname. the ability to create ad-hoc tunnels is more of a gimmick / advertising opportunity.
0: https://github.com/judge2020/cloudflare-connectivity-test/wi...
precisely (thanks!)
any app will connect with an IP am I missing something . a socket is exactly (IP, port) (src, target) tuple
For me, it’s as much about ease of use as much as it is about minimizing attack surface area.
Also the lifetime I need the connection open. For something quick, ssh tunnel. For something normies use, reverse proxy. Ain’t trying to teach my parents about IP addresses and port numbers.
tredre3 explained it above