Cloudron Forum

oh that is true, I forgot about Cloudron 7 not being supported/tested on Ubuntu 24. So then yes you have to first install Ubuntu 22, then restore Cloudron, then update Cloudron, then follow the guide at https://docs.cloudron.io/guides/upgrade-ubuntu-24/

Hello @leemuljadi I am happy to hear this worked out as intended. If there is anything we could improve in the documentation please let me know.

@skeats you could attempt it yourself. The app is already broken so what can go wrong. There is no guide for a manual restore since this is something that should not be necessary. But in this case, sadly is. If you are not comfortable doing the following, you can contact support@cloudron.io and link this topic in the request. But you will still need to upload the backup to the cloudron server into a given location from the support. Now to the gist of it. The idea would be to install a new Lampstack app. (What is lampstack? Do you mean the LAMP app? Or is this a custom app? I just assume now you are talking about the LAMP app) Copy the extracted backup to your Cloudron server e.g. /tmp/manual-restore/ In that backup included is the Database as an .sql file and the /app/data/ files. To import the Database you would need to follow either https://docs.cloudron.io/guides/import-mysql/ and then copy all files of /tmp/manual-restore/ app-backup/data/into/home/yellowtent/appsdata/APPID/data/` This would be the "manual" way.

Thinking about it some more, changing the dashboard domain before the IP switch is probably not the best idea as it would require an A record change in the DNS. The dry-run method would appear to be the best way to go.

We discussed this problem here, I had this problem just few days ago: https://forum.cloudron.io/topic/12632/tarextract-pipeline-error-invalid-tar-header/

Is this happening midway and has there already been some data restored at /home/yellowtent/boxdata/mail/... or is this the first file which fails there? Also what are the permissions and owner for /home/yellowtent/boxdata/ ?

@SansGuidon said in Some struggles with Cloudron migration: pebkac What? Googling . . . PEBKAC stands for "Problem Exists Between Keyboard and Chair". It's a tech support term, often used humorously or dismissively, to indicate that a problem is caused by user error rather than a technical issue. In essence, it's attributing the problem to the user's actions or lack of understanding, rather than a software or hardware malfunction. AHHHHH! I know the German version "Das Problem sitzt vor dem Bildschirm" litteral translation "The problem is sitting in front of the screen". Nice one @SansGuidon said in Some struggles with Cloudron migration: it makes actually sense to refresh the guide reader about the network requirements Good point! Just a "remember your Network setup!" with a link to the other doc would be enough. Right? @SansGuidon said in Some struggles with Cloudron migration: Also maybe not everyone is willing to rely solely on Cloudron config for the security. Hetzner gives lot more power to users and control, and Cloudron sometimes feels a bit too vague. Let me be brutally honest with you. German mode enabled. 99% of users that use Cloudron do not have the knowledge and experience to proivde that. What Cloudron provides is enough for the 99%. Generally speaking, not targeted towards you. IMO everything further is "expert mode" and the expert should know what to do. And if the expert does not know how, he should either learn or pay. @SansGuidon said in Some struggles with Cloudron migration: As a power user (DevOps) and busy dad, Cloudron feels both nice or confusing/limited at times depending what I want to do I get that That is the gilded cage experience and to some extent necessary to keep support low. If you are working in DevOps, I've built multiple customer solutions with Cloudron, Cloudron Gitlab, Cloudron DockerRegistry and the Gitlabrunner to fully automate, development, staging and production deployments. It is possible, but you need a firm grasb on what Cloudron does and how it does things. Then you can make it do some crazy things. @SansGuidon said in Some struggles with Cloudron migration: The mounts issues errors were for most related to network. The message must be clearer. Error message improvment. Everyone can benifit from that. Should there be a normal message with a button "more details" for power users like you and me? @SansGuidon said in Some struggles with Cloudron migration: I could use Hetzner for DNS but we have already a long term subscription with Hostinger for several domains so we are anyway still stuck a bit. Also I could argue that putting all my eggs on same provider is risky. I had an outage with Contabo in the past where both VPS and Backups location were impacted. this kind of situation is a pain in the ass. Egg Basket, agreed. If not Hetzner, some other supported DNS provider that fits your needs so you get rid of the manuall labor? => https://docs.cloudron.io/domains/ My top picks in no order are: https://desec.io/ Cloudflare Hetzner DigitalOcean @SansGuidon said in Some struggles with Cloudron migration: And I wanted to contribute this thread in the hope to open a debate about this and improve the overall experience. Yes please! Always and more of that. What ever you find that is "meh", report it in the forum. Everyone benefits.

Here the issue was that the e-mails have been moved to the new cloudron server only partially, and the new folder wasn't created in this case, so when I tried to move this in Thunderbird, it failed. So, this is solved now

@ekevu123 yes, the registry holds the images and enabling backups for it will keep the images. I think one issue might be though that because the order of apps is not defined/random , custom apps might fail to restore if the registry app restore after them. For this, the feature request you mentioned in another post will help. For the moment, workaround is just to click restore on custom apps again after the registry has restored.

Apparently, this has resolved itself, except for other, more specific issues, but I will open new threads for these to resolve them separately.

@joseph You can go ahead and close this thread. Yes, I did install the same version as my backup, but unfortunately, that didn’t help. In the end, I had to reinstall the server completely and upgrade to 8.3.1 again. It’s clear that backups need to be properly saved. Thanks for your help anyway.

It worked after I have reset my ssh keys and entered a new one during restoring.

@javiergutzp have you seen https://docs.cloudron.io/backups/#move-cloudron-to-another-server ?

(From https://forum.cloudron.io/topic/13362/restoring-app-backup-improvements)

For the first one, I guess you are suggesting a real rsync between the existing files and the remote. I think the issue is that rsync itself relies on a remote rsync service. Cloudron's rsync is strictly speaking not rsync, more like "individual files are synced as opposed to tarball". Even with sshfs, one cannot know for sure if there is a remote rsync service running. The second one looks like it can be fixed . I will should split this post though

It's fine to keep the post around, helps others in the future @igaudette said in Custom app database wiped after migration: Looks like the backup is not backing up the database of the custom apps, is it possible? FWIW, the backup strategy is the same for custom apps and apps from app store. The only difference is that one uses a customer docker image/registry and the ones from the appstore use a appstore provided docker image/docker hub.

@stevespaw said in Question: Moving apps to volume: How does this affect backup? All apps backed up as normal? I guess you mean you symlinked appdata (atleast, from your post history) ? If so, yes all apps are backed up as normal . And if I restore - I assume that the same mount points need to be in place -, but will the restore work normally then? Yes, correct.

@scooke in my case, you've to reupload the private key instead of using the backup config.