Cloudron Forum

Hello @jcalag If you have an active cloudron subscription you can contact support@cloudron.io. When you have a restored state, which is failing on cloudron-support --troubleshoot that is where you should send the mail so we can have a look.

Hello Yes it seems to work thank you Thanks

Hello @potemkin_ai You could also check the Cloudron event log to see if and when the password was changed. Have you checked that?

@luckow not sure if that is the right expectation, you have to use env vars. Password is just one or the many config vars of an addon. Addons can change because of user actions. For example, a user changes the SMTP addon address, user changes internal ports of an addon, user changes oidc scopes etc. In many PaaS setups, they will cycle passwords periodically, so hard-coding will never work even if you don't move instance in the long run. The behavior is the same in all app deployment platforms - heroku, DO app. See https://devcenter.heroku.com/articles/add-ons#config-var-values-can-change for some rationale.

The mysql db was corrupt beyond repair. I reimported from a back up and things are good.

James, Thanks, that's useful, I can use that as a workaround. I will need a 20GB pool size to keep things running the way I want. Thank you. Lee

Closing this topic due to inactivity

I am generally not in the group of AI = bad, however it likely just lacks lots of knowledge about the Cloudron internals, which make recommendations often not very useful in this area (yet). Overall I am still not sure based on this thread why DNS was involved here and given that you hit 3 different addons with apparently diverse issues, maybe something unrelated to them individually caused the trouble. We will add a few more helpers to the cloudron-support script for the future, to hopefully get down to such issues faster. If you haven't deleted the server yet, maybe we could take a closer look via SSH, since you already invested much time in debugging. If you want that, please enable remote ssh support and send a mail to support@cloudron.io with your Cloudron details.

Turns out the mysql service wasn't starting, not too clear what the root cause was, but rebuilding it made it work again.

Ok, it seemed running the /home/yellowtent/box/setup/start.sh to trigger the migration after restoring the database (because of the ERROR 1046 (3D000) at line 22: No database selected i needed to add these two lines to the dump file: CREATE DATABASE box; USE box; Then it was able to backup the database and run the migration.

I guess that is solved via https://forum.cloudron.io/post/95877

Yep, as usual. It's user error. I was using the box config backup. I just had to adjust the backup path to point to the app. I figured out the correct path by logging into my Backblaze dashboard, browsed through the bucket (by date) and the file "name" is your path. Copy/paste into the import box along with the box settings and voila!

This was sorted out in support.

@joack said in Cloudron partial install but server seems active: I tried installing it on my recently updated ubuntu20.04 desktop As others warned, don't do this! It's not meant to be run this way. You can create a VM on your desktop and install it in the VM though. The error itself is happening because you probably are using MySQL already and this is conflicting with Cloudron installation.

@jonslab did you find what it was?

Closed due to inactivity

@cleveradmin OK, I reread your original post and understood now. You are offering your setup as a way to understand how to recover MySQL which is in some indeterminate state. In general, we don't attempt to recover databases unless it's super crucial. It's almost always just easy to recover from a backup and we also don't support setups with no backup. (IMO, MySQL recovery is very complicated and kind of arcane. Fixing one issue leads to another and it can take days really. So, not worth the effort.)

@girish haha true, just wanted to throw that in there

I have given these stable IPs now - https://git.cloudron.io/cloudron/box/-/commit/582994b9d646989b42e27dde1ae0c27bbb964834

@natzilla Ah ok, I think I will improve the docs to say how to exactly recover if mysql is not even running. The troubleshooting guide assumes mysql is running but corrupt.