I have N8N installed via docker, and today I did an update. I don’t actually know what version I’m upgrading from because I’ve been pretty casual about it, but I know I’m upgrading to the current stable version. Last time I updated was sometime around February or March.
Now that I’ve started a container with the updated image, accessing N8N via the browser gives just this message: “n8n is starting up. Please wait”
Appears to be repeatedly crashing during the migration. I read somewhere that at least one of the updates between now and then would take a little time for the migration, but it’s been a few hours since I tried to start it, is this normal or am I in trouble? Can anyone point me in the right direction of things to try?
Looking at the container name are you actually using MySQL? It could be that clearing the execution_entity table (workflow logs) will sort it out.
Or as it is now showing a different message it could be that for some reason we are no longer able to connect to the database, is the database running ok?
It is using MySQL, which I now know was a bad choice – I’ll see if I can figure out how to clear that table. But I can confirm that the MySQL database is running.
I tried rolling it back to the previous version (0.198.2) but now my workflows are broken When I open it up a bunch of nodes are just missing. I’m going to take a backup of the database as it is now, clear that table, and try the new version again.
When I open it up a bunch of nodes are just missing. I’m going to take a backup of the database as it is now, clear that table, and try the new version again.
You could automate it with n8n and save them to git from the CLI tool or the API.