Hey @barbuse,
I didn’t want to directly expose n8n over the internet. As I have a VPN setup, I planned on accessing n8n through the VPN as if I was on the local network.
I’m having similar setup, but instead of VPN I’m using wireguard-based mesh-network (in my case it’s Tailscale). Each node in mesh Tailscale network is getting IP in reserved range (100.65..), traffic between the nodes is encrypted.
I then configured DNS of my n8n domain to point to this “internal” 100.65.X.X IP Address and configured my n8n deployment to be exposed only to tailscale0 network interface (so it only accepts requests that are sent to 100.65.X.X IP).
In this way, you can access n8n webhooks from your computer (assuming it is part of Tailscale mesh network) using DNS-name. I have not tried it in OAuth redirect use-cases, but I assume this should work.
WDYT?
Regards,
Serg