Issues upgrading to latest stable

Hi All

Have not upgraded for a while but decided to do so today.
I used the guide from here under the updating heading. Updated to latest stable.
Docker | n8n Docs

after trying to start the container again using the command listed on the upgrade
docker run --name=n8n -d docker.n8n.io/n8nio/n8n
I would find that it would start but the page was never accessible (page cannot be displayed).

I found however that if i removed the container again and this time used the command for starting n8n from the installation step then this would work.
docker volume create n8n_data

docker run -it --rm --name n8n -p 5678:5678 -v n8n_data:/home/node/.n8n docker.n8n.io/n8nio/n8n

With this method however i now receive the secure cookie message.

which file / file location do i need to add the n8n_secure_cookie=false to allow http connections?

I also found that if i now close my terminal window to my n8n server that the webpage is no longer contactable.

Cheers

Information on your n8n setup

  • n8n version: Was upgrading to the latest stable
  • Database (default: SQLite): default used in the setup guide
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker - on prem
  • Operating system: debian 5.10

To prevent this, the -d flag must be used (you did it with the first docker run, but not with the second). Alternatively, you could use Docker Compose.

Hi mate
thanks for that tip.
Any chance you know what file and its location i need to edit to add for
n8n_secure_cookie=false

cheers

Untested:

docker run -it --rm -d -e n8n_secure_cookie=false --name n8n -p 5678:5678 -v n8n_data:/home/node/.n8n docker.n8n.io/n8nio/n8n

But I recommend that you become familiar with docker compose. Instead of writing a long docker run command, you could then put everything in a compose.yaml file and run docker compose up -d.

Hey mate.

Sadly i tried that adding that to my run command earlier. It loads fine but the error persists.

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