Cannot start N8N After upgrade

Describe the problem/error/question

Upgraded using docker compose pull and now n8n won’t start

What is the error message (if any)?

Attaching to n8n-docker-caddy-caddy-1, n8n-docker-caddy-n8n-1
n8n-docker-caddy-caddy-1  | {"level":"info","ts":1690492464.1327567,"msg":"using provided configuration","config_file":"/etc/caddy/Caddyfile","config_adapter":"caddyfile"}
n8n-docker-caddy-caddy-1  | {"level":"warn","ts":1690492464.1347919,"msg":"Caddyfile input is not formatted; run the 'caddy fmt' command to fix inconsistencies","adapter":"caddyfile","file":"/etc/caddy/Caddyfile","line":2}
n8n-docker-caddy-caddy-1  | {"level":"info","ts":1690492464.1377034,"logger":"admin","msg":"admin endpoint started","address":"localhost:2019","enforce_origin":false,"origins":["//localhost:2019","//[::1]:2019","//127.0.0.1:2019"]}
n8n-docker-caddy-caddy-1  | {"level":"info","ts":1690492464.1390557,"logger":"http","msg":"server is listening only on the HTTPS port but has no TLS connection policies; adding one to enable TLS","server_name":"srv0","https_port":443}
n8n-docker-caddy-caddy-1  | {"level":"info","ts":1690492464.1390955,"logger":"http","msg":"enabling automatic HTTP->HTTPS redirects","server_name":"srv0"}
n8n-docker-caddy-caddy-1  | {"level":"info","ts":1690492464.1412058,"logger":"http","msg":"enabling HTTP/3 listener","addr":":443"}
n8n-docker-caddy-caddy-1  | {"level":"info","ts":1690492464.1413248,"msg":"failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 2048 kiB, got: 416 kiB). See https://github.com/quic-go/quic-go/wiki/UDP-Receive-Buffer-Size for details."}
n8n-docker-caddy-caddy-1  | {"level":"info","ts":1690492464.1434236,"logger":"http.log","msg":"server running","name":"srv0","protocols":["h1","h2","h3"]}
n8n-docker-caddy-caddy-1  | {"level":"info","ts":1690492464.1442633,"logger":"tls.cache.maintenance","msg":"started background certificate maintenance","cache":"0xc0002653b0"}
n8n-docker-caddy-caddy-1  | {"level":"info","ts":1690492464.1448073,"logger":"http.log","msg":"server running","name":"remaining_auto_https_redirects","protocols":["h1","h2","h3"]}
n8n-docker-caddy-caddy-1  | {"level":"info","ts":1690492464.1448295,"logger":"http","msg":"enabling automatic TLS certificate management","domains":["n8n.renewedvision.com"]}
n8n-docker-caddy-caddy-1  | {"level":"info","ts":1690492464.1469524,"logger":"tls","msg":"cleaning storage unit","description":"FileStorage:/data/caddy"}
n8n-docker-caddy-caddy-1  | {"level":"info","ts":1690492464.1475797,"msg":"autosaved config (load with --resume flag)","file":"/config/caddy/autosave.json"}
n8n-docker-caddy-caddy-1  | {"level":"info","ts":1690492464.147618,"msg":"serving initial configuration"}
n8n-docker-caddy-caddy-1  | {"level":"info","ts":1690492464.1489124,"logger":"tls","msg":"finished cleaning storage units"}
n8n-docker-caddy-n8n-1    | Last session crashed
n8n-docker-caddy-n8n-1    | n8n ready on 0.0.0.0, port 5678
n8n-docker-caddy-n8n-1    | Migrations in progress, please do NOT stop the process.
n8n-docker-caddy-n8n-1    | Pruning was requested, but was not enabled

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Information on your n8n setup

  • n8n version: Ran docker compose pull from 0.224 self hosted on Digital Ocean
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
  • Operating system: Ubuntu

Hey @Jonathan_Sheehan,

That looks like the migrations be happening, Which version did you upgrade from and has it come back up now?

0.224 to latest and It has not come back up.

Ah I missed your reply on this one, Are you still seeing issues or did you get it resolved in the end?

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