Activation key email submit not working (Docker self-host)

[saventis2]

---

Activation key email submit not working (Docker self-host)

Summary
I’m running n8n in Docker and can’t get past the initial activation screen. When I enter an email address to receive the activation key, the submit button never completes or returns errors. I’ve tried multiple emails, browsers, and access methods — same result every time.

---

Environment

• Host OS: Debian 12 (Proxmox VM)

• Deployment: Docker single container

• Image: n8nio/n8n:latest

• Database: SQLite (default, on /data)

• Reverse proxy: (TLS handled there, also tested direct access)

---

Steps to reproduce

1. Start n8n container with volumes:

   • /srv/n8n/data -> /home/node/.n8n

   • /srv/n8n/files -> /data

2. Go to onboarding screen.

3. Enter valid email → click Submit.

Result:

• Button spins and never completes, or

• Browser console shows TypeError: Failed to fetch, or

• Network tab shows a 403 error.

---

What I’ve tried

• Different emails:

  • First with my main email.

  • Retried with another email (to rule out domain-specific issues).

  • Same failure both times.

• Browsers:

  • Chrome, Firefox, incognito/private windows.

  • Cleared cache.

  • Same behavior.

• Networking:

  • Behind reverse proxy → fails.

  • Direct access on http://SERVER:5678 → same.

  • Tested with Tailscale (direct IP and funnel) → still fails.

• Logs (docker logs n8n):

  debug | User settings loaded from: /home/node/.n8n/config
  error | Last session crashed
  
  

• Other attempts:

  • Verified volumes writable (echo into /data works).

  • Checked UID/GID permissions (1000:1000).

  • Restarted container/host multiple times.

  • Tried adding env vars (N8N_HOST, N8N_PROTOCOL, WEBHOOK_URL) — no change.

---

Issues observed

• Activation email submit never works (spins, failed to fetch, or 403).

• Logs always show “Last session crashed” on startup (not sure if related).

• Tried multiple setups (proxy/direct, browsers, reboots, envs) → issue persists.

---

Questions

1. Is this a known issue with the activation key request endpoint in recent builds?

2. Could the “Last session crashed” message be blocking the activation step?

3. Are there env vars required for the activation submit to work behind a proxy?

4. Is there a supported manual/offline way to apply a license key so I can proceed past this step?

---

Thanks

Appreciate any help! Happy to provide sanitized HAR logs or more details from docker logs if needed.

[Naufal_Fayyadh]

Hello saventis2, i’ll try my best to help yaa!

First of all, thank you for you question. This “Submit spins / 403 / Failed to fetch“ on the activation email step is almost always a front-end → API mismatch (base UR: or proxy) or egress/network block from the container. The “Last session crashed“ line is just a stale log after an unclean exit.. it doesnt block onboarding.

Maybe i have suggestions that may can help you:

1. Set correct base URLs (important behind a proxy). In your Docker env, set all three and restart.

N8N_PROTOCOL=https
N8N_HOST=your.domain.com
N8N_PORT=443
N8N_EDITOR_BASE_URL=https://your.domain.com/
WEBHOOK_URL=https://your.domain.com/

if you access via IP:port, set protocol/host/port to match that exact URL.

2. Disable proxy extras while testing. If you use Cloudflare/WAF/Bot Fight/CDN caching, you can turn them off for the n8n route and try to retest direct (no CDN). These can cause 403 on POSTs.
3. Try to hard reload (Ctrl/Cmd-shift-r) or incognito. If needed, you can go to DevTools → Application → Clear storage → Clear site data.
4. Container has to reach the internet. You can use this inside the container:

apk add --no-cache curl ca-certificates || apt-get update && apt-get install -y curl ca-certificates
curl -I https://example.com

# DNS test
getent hosts api.n8n.cloud || nslookup api.n8n.cloud

if TLS/DNS fails from the container, activation will spin forever.

5. Ensure host time is correct (TLS will fail if clock drifts).

Thats all i think that i can share to you, hope this will work and your problem can be solved!

[saventis2]

Oh dude you are awesome

I can’t believe I missed that

Thank you all sorted now

[Naufal_Fayyadh]

You’re welcome, keep up the good work! And if you dont mind, could you please mark that as solution? Thank you so much