Bring back the tunnel feature in n8n v2 or provide a way to use it again. It was super useful for making n8n reachable from outside without messing with ports.
My use case:
I often run n8n on local machines or servers behind NAT/firewalls and need a quick public URL for webhooks and remote access. The tunnel made this super easy.
I think it would be beneficial to add this because:
Without the tunnel, accessing n8n externally requires extra setup like port forwarding, reverse proxies, or custom domains. Tunnel made life way easier.
Any resources to support this?
Are you willing to work on this?
Yes, I can help test or give feedback on implementation if needed.
hi @Enhesari2
Setting up a tunnel to your local setup can be really easy, by using some of the existing tunnel options (free/opensource) that are available.
Have you considered, reading up on the available community posts, that explain how-to tunnel setups:
Tnx for sharing!
Personally, I’m not really interested in adding extra tooling.
The built-in tunnel in v1 was simpler and felt more stable for quick setups and long-running instances.
Cloudflare Tunnel does exactly that with a single command, for free, and it’s more stable than the old built-in tunnel. I understand it adds another tool, but it’s still a 5-minute setup for a long-term solution.