Community license key request always returns 403 error - self-hosted Docker

Questions
1

Hi everyone,
I’m running a self-hosted n8n instance and I’m unable to register for the free community license key. Every time I try, I get this error:
“Failed to register community edition: Request failed with status code 403”
My setup:
n8n version: 2.13.4
Deployment: Docker with PostgreSQL
OS: Ubuntu (home server)
Tried with multiple email addresses (existing Gmail, new Gmail)
What I’ve already tried:
Multiple different email addresses
Added dns: 8.8.8.8 to the n8n Docker container
Verified that the container can reach license.n8n.io (connection successful, returns 404 on root which is expected)
Checked the database for existing license entries — none found
Checked environment variables for existing license keys — none found
Curl output from the server to license.n8n.io:
Connection successful, SSL handshake OK, HTTP/2 404 — so the server can reach the license server fine.
Database check:
sqlSELECT * FROM settings WHERE key LIKE ‘%license%’;
– Returns 0 rows
Any idea what could be causing the 403? Is my instance ID or IP somehow blocked? Happy to provide any additional info.
Thanks!

2

The 403 error often happens when the license server can’t verify your instance. A few things to check: (1) Try restarting the n8n container after DNS changes—sometimes the DNS config doesn’t apply immediately. (2) Verify your instance can reach https://license.n8n.io:443 (not just port 80). (3) Check if your ISP or firewall is blocking outbound connections to Intuit/n8n servers. (4) If you’re behind a corporate proxy, configure HTTP_PROXY / HTTPS_PROXY env vars. (5) As a last resort, reach out to n8n support with your instance ID and logs—they might be able to whitelist your instance.

3 Likes
3

Welcome to the n8n community @jesseoomen
I’d check next is whether your instance is sending consistent metadata across restarts, also try upgrading to the latest n8n version and retrying, just to rule out any incompatibility with the current license flow.

1 Like
4

Hi Benjamin and Tamy,

Thank you both for your quick responses and suggestions! I tried everything recommended. Since the issue persists, I’ve decided to reach out to n8n support directly with my instance ID and logs. Will update this thread once I hear back!

Thanks again, Jesse

1 Like
5

Hi everyone,

Just wanted to update this thread. The issue has been resolved with the help of n8n support.

The root cause was that the standard registration flow through the n8n UI was failing due to a 403 error from the license server. The workaround that worked was running the registration directly via curl from the server:

curl ‘https://enterprise.n8n.io/community-registered’
-X POST
-H ‘content-type: application/json’
–data-raw ‘{
“email":"[email protected]”,
“instanceId”:“your-instance-id”,
“instanceUrl”:“http://your-instance-url”,
“licenseType”:“community-registered”
}’

This returned the license key via email which could then be activated by clicking the activation link in the email, or manually via Settings > Usage and Plan > Enter activation key.

Thanks to Benjamin and Tamy for their suggestions, and to the n8n support team for their help!

Jesse

2 Likes