n8n Future-Proof Access

This page adds a second way in without changing the working secure editor route. The primary access stays exactly as-is; this is a recovery path for when DNS, IP allowlists, or browser access changes in the future.
Primary path stays live
Fallback is separate

1) Current secure route

HTTPS
Let’s Encrypt
Do not change yet

Use the same working editor URL you already have today. This is the route that keeps n8n secured and usable right now.

Open current n8n

2) Private tunneled route

SSH tunnel
Local browser path
Alternative access

This button opens the local n8n endpoint that becomes available after you start the SSH tunnel. It is a different path from the public HTTPS URL and is the real fallback way in.

Open tunneled n8n

3) Future-proof recovery path

SSH tunnel
Independent of public IP allowlist
Use when needed

Open a tunnel through the VPS recovery SSH door, then browse locally to n8n. This is meant to stay usable even if the public IP or DNS path changes later. 

ssh -L 5678:127.0.0.1:5678 <SSH_USER>@2.25.203.214
# then open:
http://localhost:5678
Replace <SSH_USER> with the same SSH account you already use for admin/recovery access on the VPS.
This fallback page is additive only. It does not replace the current secure n8n setup and it does not remove any access you have now.
Back to Command Center