Failed to register community edition: Request failed with status code 403

[ibrahim_shikh_hasan]

I’ve faced Failed to register community edition: Request failed with status code 403.

How can I get the license? where I’ve used many methods, but unfortunately I couldn’t find a solution.

[jabbson]

Alternatively, see if this answer can help:

Licence request failed 403 on community version running on localhost (http)

Hello everyone ! I have juste started n8n with the command “npx n8n”. The app is started on http://localhost:5678 When I try to have the free licence, I get the error : Failed to register community edition: Request failed with status code 403 My browser cache is clean, I don’t have VPN activated. Could it be because I don’t use https ? On that case, how can I activate https using npx ? Thanks for your help !

if you are behind a proxy, also this topic could be of help:

Unable to Register Community Edition – 400 Error with Valid Email and Working Proxy

Hi n8n team and community, I’m running into an issue trying to register my self-hosted Community Edition instance to unlock the free features (debug in editor, 1-day history, etc.). Setup Details: n8n version: 1.97.1 Install method: npm (global install) OS: Windows (via NVM) Database: PostgreSQL Proxy: Configured and working (confirmed via curl) Email used: Tried both corporate and personal Gmail Environment: .env includes http_proxy and https_proxy variables …

[NANYAN-01]

Yes, I also encountered the same problem. I deployed it using docker on the windows system. Is there a solution now?

[borjeee]

I ran into this error when running n8n locally with npx n8n.

The issue turned out to be that the license activation endpoint requires an HTTPS URL. By default, npx n8n serves over plain HTTP (http://localhost:5678), which causes the 403 error.

Solution: Run n8n with tunnel mode so it gets a valid HTTPS URL:

npx n8n start --tunnel

This provides a secure, HTTPS-accessible URL, and the license registration works without the 403 error.

If you don’t want to use the tunnel, another option is to set up your own HTTPS reverse proxy or SSL certificate for your local instance.

BUMP this so others can see.

[borjeee]

yup use tunnel, ‘http’ does not work, run this

npx n8n start --tunnel

[bennie1]

我也和你一样，朋友你解决了吗

[cfshow]

anyone able to get a community edition key?

[NANYAN-01]

I have already solved it. The solution is for your reference, and the activation code has been successfully applied for.

我已经解决啦，解决方案供大家参考，已经成功申请激活码。

步骤一：启动 ngrok 并获取 URL

1. 确保已安装 ngrok。如果没有安装，可从 ngrok 官网 下载适合你操作系统的版本。

2. 打开终端（在 Windows 上可使用命令提示符或 PowerShell，在 macOS 或 Linux 上使用终端）。

3. 运行命令启动 ngrok，将本地端口（假设 n8n 运行在本地 5678 端口）暴露到公网：

ngrok http 5678

1. 执行上述命令后，ngrok 会启动并显示类似如下的信息，其中 https://xxxxxx.ngrok.io 就是我们需要的公网 URL（复制这个 URL）。

Forwarding                    https://xxxxxx.ngrok.io -> http://localhost:5678

步骤二：在启动 n8n 的 Docker 命令中添加 WEBHOOK_URL

当使用 Docker 运行 n8n 时，通过环境变量来设置 WEBHOOK_URL。假设之前运行 n8n 的 Docker 命令类似：

docker run -it --rm -p 5678:5678 n8nio/n8n

现在，要添加 WEBHOOK_URL 环境变量，修改命令为：

docker run -it --rm -p 5678:5678 -e WEBHOOK\_URL=https://xxxxxx.ngrok.io n8nio/n8n

这里将 https://xxxxxx.ngrok.io 替换为你在步骤一中从 ngrok 获取到的实际 URL。

这样，通过这个公网链接申请激活码，就可以申请成功。

[marclittlemore]

Hey folks.

Sorry for the disruption. Some of our request from self-hosted users were being incorrectly blocked for a period of time. If you tried to sign up for the community registered license then you may have seen the 403 (forbidden) error.

You shouldn’t need to use the tunnel command any more but let us know if you’re still seeing issues.

[ibrahim_shikh_hasan]

Thank you all mates, the problem is solved from n8n team thanks for all

[drogfild]

Hi @marclittlemore

I’m using Proxmox home server and installed N8N with this Proxmox VE Helper-Scripts

I’m receiving 403 (forbidden) error like in the first image. Reinstalled it also and same thing.

Let me know if I can provide you some diag or more info.

[aegis301]

Yeah same problem here! Let me know if I can be of any help.

[DarkAvernus]

also adding to this that im getting a 403 error with open internet on self hosted. Using Unraid with image from community apps, although i expect the root cause is the same as the above people reporting the same issue.

[OrangeInkSpot]

I’m also getting 403 error, attempting to get a license using the same flow as the OP.

Using self-hosted in a lxc.

Edit:

It was awfully easy to just delete the lxc, find a competitor and move on.

[pwsh]

I too had the same issue with the 403 error inside a LXC container with the proxmox community script. Accessing from an nginx proxy via SSL resolved the issue. I also needed to enable websockets to prevent timeouts from occuring every few minutes.