Cloudron Forum

Yeah, I think that was the problem. I have no idea what password was used because I tried quite a few of them! I ended up just biting the bullet and taking another backup with the proper password. It seems like it's working. Thanks for your help.

The process is essentially the same as normal updates:

fetching new release tarball extracting and replace old release run the upgrade script

We have an internal hotfix tool for development which performs those steps, if run from within a git tree with the target release tag checked out. Mostly this is not provided automatically to those Cloudrons is, that we haven't tested the release jump much, so we don't want to risk users being offline until we have time to potentially fix some edge case on that server.

@girish Thanks for responding so quickly! I'll need to revisit my DNS knowledge to get that up and running. Doesn't seem too crazy to do. Thanks for the link, and also for actually trying to answer Daniel's question inside your link. Too many times people say "just don't do that" or, "do this other thing instead". Drives me insane 🙂

@girish Yeah I was starting to think that as well. I'll give it a shot and report back. Thanks!