I normally set up N8N behind a load balancer, and normally install an HTTPS certificate on the load balancer. Today was the first time I can remember that I tried to set up an N8N instance that would be accessible directly, so no HTTPS.
I spent 45 minutes trying to diagnose why I was able to log in but then getting “There was a problem loading init data” on my screen instead of a blank canvas for new workflows.
The solution was to set N8N_SECURE_COOKIE=FALSE in my environment.
Please note that this version contains a breaking change. HTTP connections to the editor will fail on domains other than localhost. You can read more about it here.
Because of all the different ways people setup n8n with various load-balancers and reverse-proxies, unfortunately there is no reliable way to detect this properly. most people don’t set N8N_PROTOCOL on n8n with their reverse-proxy setup. This is why we could not rely on any of the existing flags, and had to add a new one.
We should definitely update the docs to document N8N_SECURE_COOKIE better.
Hello, I have install n8n for the first time a few weeks ago, and I’m stuck in this situation, I have it install on node on a windows pc and want to access on another in the seme network, but it opens on this page.
I have try using a certificate and setting the environment variable, but neather work.
What more can I try?
