Upgrade Failure

[pete82]

Hi All.

I have a self-hosted install that i use every so often to visualize API data for troubleshooting when required.

About two months ago i decided to upgrade retool. when complete i simply checked that the retool webpage loaded but did not log in and left it at that.

Just tried accessing the onprem instance earlier this week however it was telling me that the account i use did not exist and could not password reset either as the account was not found.

This led me to believe that there might have been a second instance loading.

When checking the containers i found the following.
Is there a way to revert to the old containers that are there? I assume the working ones are the 3 that were exited 2 months ago.

I also believe i might have broken my yml file while i was looking around as now when i try to load the site using

sudo docker compose up -d

i get an error stating (root) Additional property db-connector is not allowed.

Any help would be greatly appreciated.

Thanks

[Darren]

Hi @pete82! Welcome back to the community.

It sounds like this was a significant upgrade! For future reference, we generally recommend upgrading to each stable release in sequence instead of skipping ahead several versions. Which version were you running previously and what did you try upgrading to?

It's hard to know how the previous containers may have been affected, but you should be able to bring them back up individually with docker commands instead of docker compose. Specifically, the command is docker start CONTAINER_ID.

If you want to share your yml files via DM, I'd be happy to take a look!