Team,
Last night our Retool on premise was throwing 502 errors on the UI and when we tried to restart the Retool docker container via following the given article (Deploy Self-hosted Retool on Amazon EC2 | Retool Docs), it reset everything.
How can we resolve this? It will deeply impact a lot of things if data is not restored, we created a lot of apps/resources. Last working timestamp should be fine for us for any restoration
Hey @_Kamlesh_Meghwal since you are self-hosted there is unfortunately no way for the Retool team to restore your instance's DB.
That being said I can help walk you through some steps to determine what caused this behavior. Do you mind running docker system df -v for me and confirming what is in the Local Volumes space usage section? Would you also mind having the user who restarted the docker container run history on the machine that executed these instructions and copy/paste them in this post?
The commands above will do the following: