<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[N8N Security]]></title><description><![CDATA[<p dir="auto">Hi everyone,</p>
<p dir="auto">n8n instances are targets for automated attacks and brute-force attempts. Now, I know that Cloudron offers the <code>"proxyAuth": {}</code> feature in the <code>CloudronManifest.json</code> for custom-packaged apps, which puts the Cloudron login screen in front of the app.</p>
<p dir="auto">My question is:</p>
<ul>
<li>Is there a way to enable proxyAuth for the official App Store version of n8n? (e.g., via a manual config change or a CLI flag?)</li>
</ul>
<p dir="auto">Ideally, it would be amazing if we could protect the main UI/API via Cloudron Auth, accepting that I have to double-log-in, while explicitly keeping certain webhook paths <code>/webhook/...</code> open so that external services can still trigger workflows. We would still be vulnerable, but with this feature less likely the victim of an automated attack...</p>
<p dir="auto">Thanks!</p>
]]></description><link>https://forum.cloudron.io/topic/14892/n8n-security</link><generator>RSS for Node</generator><lastBuildDate>Sat, 18 Apr 2026 07:12:00 GMT</lastBuildDate><atom:link href="https://forum.cloudron.io/topic/14892.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 14 Jan 2026 10:48:27 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to N8N Security on Wed, 14 Jan 2026 11:15:35 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/teiluj" aria-label="Profile: Teiluj">@<bdi>Teiluj</bdi></a> said in <a href="/post/118492">N8N Security</a>:</p>
<blockquote>
<p dir="auto">Would this obfuscate the n8n frontend, at least partially?</p>
</blockquote>
<p dir="auto">Yes, but security via obscurity is useless.</p>
<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/jorrg" aria-label="Profile: jorrg">@<bdi>jorrg</bdi></a> said in <a href="/post/118493">N8N Security</a>:</p>
<blockquote>
<p dir="auto">So the only thing that I presume would change that if some automated scraper comes passing by my IP asking: "Do you run N8N?" my server would answer: "Please log in with your cloudron details" instead of "Sure I am running this N8N version"</p>
</blockquote>
<p dir="auto">If your IP is scraped it will not even reply with N8N but would return Cloudron.<br />
They would need to know the subdomain of your N8N Cloudron app, which is also possible from e.g. the SSL/TLS certificate if wildcard is not used.<br />
Example for <code>cloudron.io</code> <a href="https://www.merklemap.com/search?query=cloudron.io&amp;page=0" target="_blank" rel="noopener noreferrer nofollow ugc">https://www.merklemap.com/search?query=cloudron.io&amp;page=0</a></p>
<p dir="auto">Anything that is publicly accessible in the World Wide Web is subjected to access attempts.<br />
And again, if N8N would use the custom OIDC plugin, the brute force would just move to a new target, the OIDC login.</p>
<p dir="auto">We are planning to add per app IP-Whitelisting.<br />
With that, apps could be gated behind e.g.: the Cloudron VPN app.<br />
This would be a reliable way to block public access.</p>
]]></description><link>https://forum.cloudron.io/post/118500</link><guid isPermaLink="true">https://forum.cloudron.io/post/118500</guid><dc:creator><![CDATA[james]]></dc:creator><pubDate>Wed, 14 Jan 2026 11:15:35 GMT</pubDate></item><item><title><![CDATA[Reply to N8N Security on Wed, 14 Jan 2026 11:10:01 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/teiluj" aria-label="Profile: Teiluj">@<bdi>Teiluj</bdi></a> said in <a href="/post/118491">N8N Security</a>:</p>
<blockquote>
<p dir="auto">However, in the meantime, maybe you've seen this post about OIDC and n8n from <a class="plugin-mentions-user plugin-mentions-a" href="/user/luckow" aria-label="Profile: luckow">@<bdi>luckow</bdi></a> ?</p>
</blockquote>
<p dir="auto">Haven't seen it, before!</p>
]]></description><link>https://forum.cloudron.io/post/118498</link><guid isPermaLink="true">https://forum.cloudron.io/post/118498</guid><dc:creator><![CDATA[jorrg]]></dc:creator><pubDate>Wed, 14 Jan 2026 11:10:01 GMT</pubDate></item><item><title><![CDATA[Reply to N8N Security on Wed, 14 Jan 2026 11:00:30 GMT]]></title><description><![CDATA[<p dir="auto">Yeah, I know.</p>
<p dir="auto">The thing that I was worried about were automated scrapes for N8N.</p>
<p dir="auto">So the only thing that I presume would change that if some automated scraper comes passing by my IP asking: "Do you run N8N?" my server would answer: "Please log in with your cloudron details" instead of "Sure I am running this N8N version"</p>
]]></description><link>https://forum.cloudron.io/post/118493</link><guid isPermaLink="true">https://forum.cloudron.io/post/118493</guid><dc:creator><![CDATA[jorrg]]></dc:creator><pubDate>Wed, 14 Jan 2026 11:00:30 GMT</pubDate></item><item><title><![CDATA[Reply to N8N Security on Wed, 14 Jan 2026 11:00:24 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/james" aria-label="Profile: james">@<bdi>james</bdi></a> Would this obfuscate the n8n frontend, at least partially?</p>
]]></description><link>https://forum.cloudron.io/post/118492</link><guid isPermaLink="true">https://forum.cloudron.io/post/118492</guid><dc:creator><![CDATA[Teiluj]]></dc:creator><pubDate>Wed, 14 Jan 2026 11:00:24 GMT</pubDate></item><item><title><![CDATA[Reply to N8N Security on Wed, 14 Jan 2026 10:59:26 GMT]]></title><description><![CDATA[<p dir="auto">Hi <a class="plugin-mentions-user plugin-mentions-a" href="/user/jorrg" aria-label="Profile: jorrg">@<bdi>jorrg</bdi></a> - I am also interested generally on the idea of a Cloudron proxyAuth in front of a publicly accessible Cloudron app, to prevent the kind of scenario you describe.</p>
<p dir="auto">This kind of functionality seems to be high on demand for Cloudron (see <a href="https://forum.cloudron.io/topic/14226/app-proxy-questions-and-proxy-authentication-possible-improvement-suggestions">here</a> and <a href="https://forum.cloudron.io/topic/14536/add-additional-cloudron-proxy-auth-option-on-apps/3">here</a> for example)</p>
<p dir="auto">However, in the meantime, maybe you've seen <a href="https://forum.cloudron.io/topic/14852/unofficial-n8n-oidc-for-self-hosters?_=1768387968871">this post</a> about OIDC and n8n from <a class="plugin-mentions-user plugin-mentions-a" href="/user/luckow" aria-label="Profile: luckow">@<bdi>luckow</bdi></a> ?<br />
Hopefully this could help in this particular case, even if not officially supported by Cloudron (yet?)</p>
]]></description><link>https://forum.cloudron.io/post/118491</link><guid isPermaLink="true">https://forum.cloudron.io/post/118491</guid><dc:creator><![CDATA[Teiluj]]></dc:creator><pubDate>Wed, 14 Jan 2026 10:59:26 GMT</pubDate></item><item><title><![CDATA[Reply to N8N Security on Wed, 14 Jan 2026 10:55:35 GMT]]></title><description><![CDATA[<p dir="auto">Hello <a class="plugin-mentions-user plugin-mentions-a" href="/user/jorrg" aria-label="Profile: jorrg">@<bdi>jorrg</bdi></a></p>
<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/jorrg" aria-label="Profile: jorrg">@<bdi>jorrg</bdi></a> said in <a href="/post/118489">N8N Security</a>:</p>
<blockquote>
<p dir="auto">Is there a way to enable proxyAuth for the official App Store version of n8n? (e.g., via a manual config change or a CLI flag?)</p>
</blockquote>
<p dir="auto">Unfortunately, no.</p>
<p dir="auto">Also, the only thing this would do is move the brute force from N8N to the Cloudron Proxy Auth.<br />
So nothing really changes.</p>
]]></description><link>https://forum.cloudron.io/post/118490</link><guid isPermaLink="true">https://forum.cloudron.io/post/118490</guid><dc:creator><![CDATA[james]]></dc:creator><pubDate>Wed, 14 Jan 2026 10:55:35 GMT</pubDate></item></channel></rss>