Help for owners
My self-hosted n8n is on the internet and I am not sure it is safe
Short answer
A self-hosted n8n holds logins to your other systems, so treat it like a vault. n8n documents the main controls: SSL, single sign-on and two-factor settings, blocking nodes, disabling the public API, SSRF protection, task-runner hardening and a built-in security audit. Check access and backups before changing settings.
Does this sound like your situation?
- n8n opens in a browser from anywhere and I do not know who can sign in.
- It runs on plain http, or its address is a bare IP and port.
- Several people share one login.
- Our API keys and passwords for other systems are stored inside it.
- A customer or auditor asked how n8n is secured and nobody knew.
Why does this happen?
n8n stores the keys to other systems
The point of n8n is that it can log in to your CRM, mail, accounting and payment tools. Whoever controls n8n can use those logins, so it deserves more care than a normal web tool.
Encryption in transit is not automatic
n8n documents two ways to get TLS. A reverse proxy such as Traefik or a network load balancer in front of n8n is the recommended one, and it should also handle certificate renewals. The other is passing certificate and key files to n8n directly, where you must keep the certificate renewed yourself.
Confirmed by docs.n8n.io
Extra entry points are left on
n8n recommends disabling its public REST API if you do not plan to use it. It also offers a switch to block specific nodes, and SSRF protection that stops nodes reaching internal network addresses, localhost services and cloud metadata endpoints. n8n says network-level protection stays the primary defence.
Confirmed by docs.n8n.io
Nobody ran the audit
n8n can run a security audit from its command line, its API or a node. It produces five risk reports and, among other things, lists credentials not used in any workflow.
Confirmed by docs.n8n.io
Sign-in and sharing are limited on the free edition
n8n lists SSO and sharing of workflows and credentials among the features that need a paid plan. On the Community edition only the instance owner and the user who created a workflow or credential can access it, which pushes people toward shared logins.
Confirmed by docs.n8n.io
What can I do about it today?
- Check the address starts with httpsIf your n8n opens on plain http, tell whoever manages it that it needs a certificate. Do not enter new passwords there until it does.
- List who has an accountOpen the user list and note anyone who has left or no longer needs access. Ask for those accounts to be removed.
- Stop sharing one loginEach person should have their own account so you can see who changed what.
- Make a list of the systems n8n can reachWrite down which accounts and API keys are stored in it. If n8n were compromised, these are the keys you would have to replace.
- Ask for a backup before any changeHardening settings can lock people out. A restorable copy, including the encryption key, comes first.
When should I bring someone in?
- n8n was ever reachable without HTTPS or a login.
- You suspect someone outside the company had access.
- A client or auditor needs written proof of how the instance is secured.
How do I handle it?
- Map the exposureI check how n8n is reached, who can sign in, which ports are open and what it is connected to.
- Run n8n's own auditThe audit's findings give me a list based on the product's documentation, not on guesswork.
- Fix access firstHTTPS behind a reverse proxy, individual accounts, removal of old users, and the public API off if it is unused.
- Limit what a workflow can reachWhere it fits, I turn on SSRF protection, block nodes nobody needs and keep network rules as the main barrier.
- Write it downYou receive a short written note of what is configured and where the key and backups are kept.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Is self-hosted n8n unsafe by default?
I cannot say that for your server. It depends on how it is exposed, who has accounts and what is open on the network. The audit and a review answer it.
Do I need a paid plan to be secure?
Not for everything. HTTPS, the public API switch, SSRF protection and the audit are documented as configuration. SSO and sharing need a paid plan.
Can I put n8n behind a VPN instead?
Often yes, but webhooks from outside services must still reach it. That needs a design, not a guess.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.
For your developer: the technical fixes
Certbot failed to authenticate some domains (authenticator: webroot). The Certificate Authority reported these problems:A Let's Encrypt certificate did not renew with Certbot502 Bad Gateway when proxy_pass uses https://nginx reverse proxy to an HTTPS backend fails the SSL handshakePossible SECURITY ATTACK detected. It looks like somebody is sending POST or Host: commands to Redis.Redis logs a possible security attack from POST or Host commands