<a name="p-394108-hi-everyone-im-setting-up-a-new-self-hosted-n8n-instance-using-docker-on-windows-and-im-consistently-getting-an-error-403-when-trying-to-claim-the-free-community-license-key-i-have-spent-a-lot-of-time-troubleshooting-this-and-believe-the-issue-is-not-with-my-local-setup-anymore-my-setup-n8n-version-n8n-n8n-database-sqlite-default-running-on-docker-desktop-on-windows-using-wsl-2-backend-how-im-running-n8n-using-the-official-docker-composeyml-with-a-bind-mount-for-data-n8nhomenoden8n-here-is-the-extensive-list-of-troubleshooting-steps-i-have-already-taken-1-initial-error-the-first-time-i-ran-docker-compose-up-it-failed-due-to-a-port-conflict-on-5678-2-restart-success-after-a-pc-restart-the-port-was-free-and-n8n-started-successfully-i-was-able-to-create-an-owner-account-3-first-403-error-when-i-tried-to-claim-the-license-i-got-the-403-forbidden-error-for-the-first-time-4-vpn-networking-issues-i-am-in-a-region-that-requires-a-vpn-clash-client-on-windows-for-stable-international-connections-5-dns-fix-i-tried-setting-a-custom-dns-8888-in-the-docker-engine-settings-but-the-403-error-persisted-6-docker-proxy-configuration-i-configured-the-docker-proxy-to-point-to-my-clash-clients-port-http1270017897-but-it-failed-i-corrected-the-address-to-httphostdockerinternal7897-which-is-the-correct-way-for-a-container-to-reach-the-windows-host-7-a-breakthrough-after-setting-the-proxy-to-hostdockerinternal-the-error-changed-from-403-forbidden-to-client-network-socket-disconnected-this-proved-the-container-was-now-correctly-routing-traffic-to-my-clash-proxy-8-proxy-allow-lan-setting-i-realized-the-socket-disconnected-error-was-because-my-clash-client-was-rejecting-connections-from-the-docker-container-which-it-sees-as-a-lan-device-i-enabled-the-allow-lan-connections-setting-in-clash-9-back-to-403-after-enabling-allow-lan-the-socket-disconnected-error-went-away-but-i-was-back-to-the-original-403-forbidden-error-10-vpn-node-switching-my-conclusion-was-that-my-vpns-ip-address-was-being-blocked-by-the-n8n-license-server-i-have-tried-switching-to-many-different-server-nodes-japan-singapore-us-etc-but-every-single-one-results-in-a-403-error-11-complete-reset-to-be-absolutely-sure-it-wasnt-an-account-issue-i-completely-reset-my-n8n-instance-by-running-docker-compose-down-and-manually-deleting-the-n8n-data-directory-after-setting-up-a-new-owner-account-the-403-error-still-occurs-my-conclusion-question-after-all-this-i-am-almost-certain-that-my-local-setup-and-docker-networking-are-now-configured-correctly-the-issue-seems-to-be-that-a-wide-range-of-my-vpn-providers-ip-addresses-are-being-blocked-by-the-n8n-license-servers-firewall-is-this-a-known-issue-are-there-specific-regions-or-vpns-that-have-trouble-with-this-is-there-any-other-way-to-activate-the-community-license-or-any-advice-on-what-to-try-next-thanks-in-advance-for-your-help-1" class="anchor" href="#p-394108-hi-everyone-im-setting-up-a-new-self-hosted-n8n-instance-using-docker-on-windows-and-im-consistently-getting-an-error-403-when-trying-to-claim-the-free-community-license-key-i-have-spent-a-lot-of-time-troubleshooting-this-and-believe-the-issue-is-not-with-my-local-setup-anymore-my-setup-n8n-version-n8n-n8n-database-sqlite-default-running-on-docker-desktop-on-windows-using-wsl-2-backend-how-im-running-n8n-using-the-official-docker-composeyml-with-a-bind-mount-for-data-n8nhomenoden8n-here-is-the-extensive-list-of-troubleshooting-steps-i-have-already-taken-1-initial-error-the-first-time-i-ran-docker-compose-up-it-failed-due-to-a-port-conflict-on-5678-2-restart-success-after-a-pc-restart-the-port-was-free-and-n8n-started-successfully-i-was-able-to-create-an-owner-account-3-first-403-error-when-i-tried-to-claim-the-license-i-got-the-403-forbidden-error-for-the-first-time-4-vpn-networking-issues-i-am-in-a-region-that-requires-a-vpn-clash-client-on-windows-for-stable-international-connections-5-dns-fix-i-tried-setting-a-custom-dns-8888-in-the-docker-engine-settings-but-the-403-error-persisted-6-docker-proxy-configuration-i-configured-the-docker-proxy-to-point-to-my-clash-clients-port-http1270017897-but-it-failed-i-corrected-the-address-to-httphostdockerinternal7897-which-is-the-correct-way-for-a-container-to-reach-the-windows-host-7-a-breakthrough-after-setting-the-proxy-to-hostdockerinternal-the-error-changed-from-403-forbidden-to-client-network-socket-disconnected-this-proved-the-container-was-now-correctly-routing-traffic-to-my-clash-proxy-8-proxy-allow-lan-setting-i-realized-the-socket-disconnected-error-was-because-my-clash-client-was-rejecting-connections-from-the-docker-container-which-it-sees-as-a-lan-device-i-enabled-the-allow-lan-connections-setting-in-clash-9-back-to-403-after-enabling-allow-lan-the-socket-disconnected-error-went-away-but-i-was-back-to-the-original-403-forbidden-error-10-vpn-node-switching-my-conclusion-was-that-my-vpns-ip-address-was-being-blocked-by-the-n8n-license-server-i-have-tried-switching-to-many-different-server-nodes-japan-singapore-us-etc-but-every-single-one-results-in-a-403-error-11-complete-reset-to-be-absolutely-sure-it-wasnt-an-account-issue-i-completely-reset-my-n8n-instance-by-running-docker-compose-down-and-manually-deleting-the-n8n-data-directory-after-setting-up-a-new-owner-account-the-403-error-still-occurs-my-conclusion-question-after-all-this-i-am-almost-certain-that-my-local-setup-and-docker-networking-are-now-configured-correctly-the-issue-seems-to-be-that-a-wide-range-of-my-vpn-providers-ip-addresses-are-being-blocked-by-the-n8n-license-servers-firewall-is-this-a-known-issue-are-there-specific-regions-or-vpns-that-have-trouble-with-this-is-there-any-other-way-to-activate-the-community-license-or-any-advice-on-what-to-try-next-thanks-in-advance-for-your-help-1"> Hi everyone, I’m setting up a new self-hosted n8n instance using Docker on Windows and I’m consistently getting an “Error 403” when trying to claim the free community license key. I have spent a lot of time troubleshooting this and believe the issue is not with my local setup anymore. **My Setup:*…

Error 403 when trying to claim a license key

jabbson September 25, 2025, 8:01pm 2

Hello

see if you have the same problem:

The workaround was to run your instance with --tunnel flag to get the key and then again without it to apply it. Read the answers and suggestions.