BAD GATEWAY after UPDATE

[kalazino]

Hello and thanks for sharing your project.
I tried to upgrade but after that I get a BAD GATEWAY.
I'm thinking of doing a new installation, but I don't know how to restore the database (I performed the backup as per procedure)
Thank you

[eduardogsilva]

You do not need to make a new installation.
You probably just didn't updated your docker-compose.yml file. Check the upgrade instructions and do not skip this step.

You may also check your docker logs for the error messages.

[kalazino]

It appears that the postgres and routerfleet containers are unable to start

[eduardogsilva]

check the logs for each container that is not starting, but it does look like that you did not upgraded your docker-compose.yml file.

this message should be there in routerfleet container logs.

Do not skip this step, please check again the upgrade instructions.

Cheers.

[kalazino]

This is the log for container postgres

I'm running docker on Alpine distro.
could this be the problem?

[kalazino]

Postgres version 16 is specified in your docker-compose file.
I modified the file with:
image: postgres:latest
and it seems to work

[eduardogsilva]

I've detected the issue that the postgres:latest upgraded the current installs from 16 to 17. This was breaking the container, so I locked the version to 16.

Since you have a "new install", you got the opposite problem.
I have to think how I'm going to deal with this now.

[eduardogsilva]

I've created an issue with this bug. I decided to pin the version 16 since I believe that this is the most used version at this moment.

#46