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

**URL:** <https://community.n8n.io/t/activation-key-email-submit-not-working-docker-self-host/193185>\
**Category:** Questions\
**Created:** [September 24, 2025, 1:54am UTC](https://community.n8n.io/t/activation-key-email-submit-not-working-docker-self-host/193185 "2025-09-24T01:54:48Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![saventis2](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/saventis2/32/122821_2.png) [@saventis2](https://community.n8n.io/u/saventis2)\
**Post date:** [September 24, 2025, 1:54am UTC](https://community.n8n.io/t/activation-key-email-submit-not-working-docker-self-host/193185/1 "2025-09-24T01:54:49Z")

</div>

* * *

# 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:

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:**

- **Browsers:**

- **Networking:**

- **Logs (`docker logs n8n`):**

- **Other attempts:**

* * *

## 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.

---

<div class="post-metadata">

**Author:** ![Naufal\_Fayyadh](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/naufal_fayyadh/32/122498_2.png) [@Naufal\_Fayyadh](https://community.n8n.io/u/Naufal_Fayyadh)\
**Post date:** [September 24, 2025, 2:24am UTC](https://community.n8n.io/t/activation-key-email-submit-not-working-docker-self-host/193185/2 "2025-09-24T02:24:36Z")

</div>

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.

```bash
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.

1. 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.
2. Try to hard reload (Ctrl/Cmd-shift-r) or incognito. If needed, you can go to DevTools → Application → Clear storage → Clear site data.
3. Container has to reach the internet. You can use this inside the container:

```bash
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.

1. 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! 😊🙌

---

<div class="post-metadata">

**Author:** ![saventis2](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/saventis2/32/122821_2.png) [@saventis2](https://community.n8n.io/u/saventis2)\
**Post date:** [September 24, 2025, 7:44am UTC](https://community.n8n.io/t/activation-key-email-submit-not-working-docker-self-host/193185/3 "2025-09-24T07:44:10Z")

</div>

Oh dude you are awesome

I can’t believe I missed that

Thank you all sorted now

---

<div class="post-metadata">

**Author:** ![Naufal\_Fayyadh](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/naufal_fayyadh/32/122498_2.png) [@Naufal\_Fayyadh](https://community.n8n.io/u/Naufal_Fayyadh)\
**Post date:** [September 24, 2025, 9:45am UTC](https://community.n8n.io/t/activation-key-email-submit-not-working-docker-self-host/193185/4 "2025-09-24T09:45:18Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![system](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/system/32/195824_2.png) [@system](https://community.n8n.io/u/system)\
**Post date:** [October 1, 2025, 9:45am UTC](https://community.n8n.io/t/activation-key-email-submit-not-working-docker-self-host/193185/5 "2025-10-01T09:45:45Z")

</div>

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.