N8n stuck at "Initializing n8n process" after update from version 1.95.0 to 1.97.0

I update n8n version from 1.95.0 to 1.97.0 and n8n stuck at “Initializing n8n process”.

In version 1.95.0 everything works correctly. If I try to run n8n for the first time, after initializing the n8n process, I will see the migration:

Initializing n8n process
n8n ready on ::, port 5678
Migrations in progress, please do NOT stop the process.
Starting migration InitialMigration1588102412422
Finished migration InitialMigration1588102412422
Starting migration WebhookModel1592445003908
Finished migration WebhookModel1592445003908
Starting migration CreateIndexStoppedAt1594825041918

But this does not happen after updating to 1.97.0.

I also tried to wait about 20 minutes for the process to complete, but it didn’t work.
I also tryed to deleted the SQLite database and reinstalled n8n.

What is the error message (if any)?

If I press Ctrl + C, this is the error I see:

Initializing n8n process
^CReceived SIGINT. Shutting down...

Stopping n8n...
There was an error shutting down n8n.
Cannot read properties of undefined (reading 'removeAllQueuedWorkflowActivations')

Contents of directory .n8n in container:

~ $ ls -la ~/.n8n/
total 16
drwxr-sr-x    1 node     node          4096 Jun 20 09:40 .
drwxr-sr-x    1 node     node          4096 Jun 20 09:41 ..
-rw-r--r--    1 node     node            56 Jun 20 09:40 config
-rw-r--r--    1 node     node             0 Jun 20 09:40 crash.journal
-rw-r--r--    1 node     node             0 Jun 20 09:40 database.sqlite
~ $

Thats logs i see when try to enable debug mode:

root:~ # docker run -e N8N_LOG_LEVEL=debug -it -p 5678:5678 n8nio/n8n:1.97.0
2025-06-20T09:47:11.052Z | info | No encryption key found - Auto-generating and saving to: /home/node/.n8n/config {"file":"instance-settings.js","function":"loadOrCreate"}
2025-06-20T09:47:13.235Z | info | Initializing n8n process {"file":"start.js","function":"init"}
2025-06-20T09:47:13.353Z | debug | Lazy-loading nodes and credentials from n8n-nodes-base {"nodes":481,"credentials":384,"file":"lazy-package-directory-loader.js","function":"loadAll"}
2025-06-20T09:47:13.361Z | debug | Lazy-loading nodes and credentials from @n8n/n8n-nodes-langchain {"nodes":93,"credentials":21,"file":"lazy-package-directory-loader.js","function":"loadAll"}

Information on your n8n setup

  • n8n version: 1.97.0
  • Database (default: SQLite): SQLite
  • n8n EXECUTIONS_PROCESS setting (default: own, main): main
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker 26.1.3
  • Operating system: Oracle Linux 8.10, kernel 5.15.0-101.103.2.1.el8uek.x86_64

Any help would be invaluable :folded_hands:

try rollign back to the previous stable version

I can roll back to the last stable version and it will work correctly. But what to do in the future when i try to updating to the next versions of n8n? I get the same problem described above.

I had the same issue it because of ipv6 that is the default now

You could fix this by settings env var :

N8N_LISTEN_ADDRESS=0.0.0.0

@Kent1 what is the impact of setting - N8N_LISTEN_ADDRESS=0.0.0.0
do you know what variable does?

[quote=“sandy4v, post:5, topic:135744”]
N8N_LISTEN_ADDRESS=0.0.0.0
[/quote]There is another post on a forum which says this property is needed for discoverability- bhyve - n8n running on podman in a bhyve ubuntu vm | The FreeBSD Forums