Got Bad Gateway error after updating to v0.21.1
hello, just updated my dokploy to latest version from v0.20 , after waiting a while, cannot seem to get to dokploy UI, always returns Bad Gateway error. This is hosted on Oracle Cloud VM.Standard.A1.Flex . Any idea how to troubleshoot this? Restarting the instance does nothing.
6 Replies
I have exactly the same problem. Hosted on Hetzner Ubuntu 24.04.2 LTS
Log file in that container shows this:
{"log":"Main Server Error [Error [PostgresError]: column backups.userId does not exist] {\n","stream":"stderr","time":"2025-04-02T11:27:50.860522058Z"}
{"log":" severity_local: 'ERROR',\n","stream":"stderr","time":"2025-04-02T11:27:50.860546114Z"}
{"log":" severity: 'ERROR',\n","stream":"stderr","time":"2025-04-02T11:27:50.860549901Z"}
{"log":" code: '42703',\n","stream":"stderr","time":"2025-04-02T11:27:50.860552966Z"}
{"log":" position: '5510',\n","stream":"stderr","time":"2025-04-02T11:27:50.860556092Z"}
{"log":" file: 'parse_relation.c',\n","stream":"stderr","time":"2025-04-02T11:27:50.860559158Z"}
{"log":" line: '3722',\n","stream":"stderr","time":"2025-04-02T11:27:50.860562424Z"}
{"log":" routine: 'errorMissingColumn'\n","stream":"stderr","time":"2025-04-02T11:27:50.86056547Z"}
{"log":"}\n","stream":"stderr","time":"2025-04-02T11:27:50.860568496Z"}
Seems already opened as issue 1605 - https://github.com/Dokploy/dokploy/issues/1605
GitHub
broken on update to 0.21.1 - column backups.userId does not exist ...
To Reproduce After updating, server start fails with: Main Server Error [Error [PostgresError]: column backups.userId does not exist] { severity_local: 'ERROR', severity: 'ERROR', c...
I had the same issue with the last update and it turns out I had another process running on port 3000. Looks like this might be another issue but it’s worth checking your ports just in case
How can i upgrade then to the new version without access to the dashboard?
i think you can go to the terminal and do this: curl -sSL https://dokploy.com/install.sh | sh -s update
GitHub
Container Not Running After Upgrading Dokploy to v0.21.1 – Postgr...
To Reproduce Steps to Reproduce: Run Dokploy v0.21.1 on a VPS with Postgres, Next.js, and Go services. Upgrade Dokploy to the latest version. Restart the containers. Observe that the error occurs, ...