I tried to update my self-hosted n8n instance from 0.200.0 to 0.202.1 via docker compose (worked well mayn times):
- docker-compose pull
- docker-compose down
- docker-compose up -d
After the update my site showed only the message “Bad Gateway”, nothing else …
In the past it was showing this message only for a few seconds and when I reloaded the page it was gone.
But this time it stayed. I am no expert in server stuff, so I reverted my server back to the last backup and it works again on 0.200.0, but I would like to stay updated.
Is anyone able to help me? What can I check to get it up and running?
Thx a lot!
Information on your n8n setup
- n8n version: 0.200.0
- Database you’re using: mySQL
- Running n8n with the execution process [own(default), main]: ?
- Running n8n via Docker
I probably don’t have the answer - but when I have issues with my n8n container I check a few things:
Have you enabled any n8n logging in your compose file ?
Are you using the traefik reverse proxy or just a non-exposed container ?
Do you see any messages if you don’t execute the compose detached (no -d) ?
Ok so that’s the 0.200.0 version running, anything different in the message when you switch to 0.202.1, You mentioned that 0.200.0 was the working release.
Anything significant in the traefik compose ? hint you might want to avoid posting any public dns information…
Thx for your input, I need to find the right time to try the install again, may take some days …
No problem
Just fyi I run active multiple N8N releases from my docker compose - I keep a labelled known release e.g. 0.200.0 and another one on a different port running :latest , that way I can do basic checks before switching containers/versions etc, but it depends on your requirements/disk availability.
You have to use unique traefik naming and ports, dns e.g. n8n1. , n8n2. , callbacks etc and they don’t/can’t share the hidden n8n / sql db etc… at least I don’t think it would be wise to do flow/DB sharing.
