Problem setting up Owner 401

Thanks, I shall try it. I forgot I had created this post here and just created a new tread Questions. Wow, my memory is worse than some president’s… ignore that thread… or should I maybe delete it and follow through here?

1 Like

I also got into same problem.
I am using kubernetes.

expliciting pointing the image to image: n8nio/n8n:1.31.0 resolved it

1 Like

It works, just rolled back from 1.31.2 to 1.31.0

Hey @eddy_wan & @Jeba_Prince,

From 1.32.0 if you are running n8n without HTTPS on a domain other than localhost, you need to either setup HTTPS, or you can disable the secure flag by setting the env variable N8N_SECURE_COOKIE to false.

Installing a new build using 1.31.0 worked for me with the same issue. Something is up with 1.31.2.

Can someone please point me where I do set “N8N_SECURE_COOKIE=false”?

Its work for me,
thanks Jon.

Hey @SoulReaver

It is an environment option so it would be set wherever you are currently setting those. If you are using Docker it would be the with the -e option

If I just add https:// to the ip:port … I get: “SSL_ERROR_RX_RECORD_TOO_LONG”
Where would I set N8N_SECURE_COOKIE env option to false?

I don’t use docker compose and my /.n8n/config only containes two lines with encriptionKey and tunnelsubdomain.

This is how I launch n8n:

sudo docker run -it
–restart always
–name n8n
-p 5678:5678
-v ~/.n8n:/home/node/.n8n
n8nio/n8n
start --tunnel

solved for me:

sudo docker run -it
–restart always
–name n8n
-p 5678:5678
-v ~/.n8n:/home/node/.n8n
-e N8N_SECURE_COOKIE=“false”
n8nio/n8n
start --tunnel

2 Likes

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.