You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
That's a thing I definitely missed in the baseline confg for n8n. v0.2.15 will ship with secure cookies disabled out-of-the-box since http://localhost is where the service will run in most supported scenarios
Setting it with harbor config set N8N_SECURE_COOKIE false doesn't have effect.
Aha, I knew that the freedom of harbor config will eventually make someone try something like this. It's intended only for the env vars explicitly managed by Harbor (and they are all automatically prefixed by HARBOR_ when retrieved or written in the current profile.
But I agree that something like this is needed and my hands were also reaching out for something similar a few times, so v0.2.15 now comes with harbor env exactly for such purpose:
harbor env n8n n8n.secure_cookie false
Alternatively, you can override it manually in the editor of choice:
open $(harbor home)/n8n/override.env
Setting in the main .env would also work, but you'd risk loosing it after one of the updates, since the file is actively merged/cleaned with the profiles/default.env during updates (you could use profiles to re-apply though)
Hi,
I installed n8n, then its homepage asks for
N8N_SECURE_COOKIE=false
.Setting it with
harbor config set N8N_SECURE_COOKIE false
doesn't have effect.Thank you
The text was updated successfully, but these errors were encountered: