@gerard said in Restore v7.7.2 (Ubuntu 22.04) backup to v8.0.0 (Ububtu 24.04) system: The release notes state an "initial support for 24.04" that doesn't sound like it's fully supported yet. It should mostly work but we are just being a bit cautious here There's a limit to how many VPSs we can test the installation on. We tested on the popular ones and seems to work, but one never knows. The upgrade path for you would be to upgade to v8. Then later in 2-3 weeks time when v8 is considered more stable, you can migrate to a fresh ubuntu 24 with cloudron backups.

Sorry, but I am not following how name resolution is dependent on port 22. Name resolution uses UDP port 52 and is completely different from SSH which is TCP port 22 .

@linuxpowerhouse no worries, welcome to cloudron

This was resolved overnight - I am not sure how, but now the volume shows again normally. However, it opened up a new problem with Nextcloud, which I have posted in a new thread there.

@mmtrade Okay, after a thorough analysis of my account. I have a VPS the cheapest, where I could not change the IP address. It remains technical support to solve this and as you in which you manage the server you have the task of securing the server.

Actually docker pull ubuntu is just a test pulling a random common image. This is not required for Cloudron. I was just trying to rule out some issues.

https://my.hussainwh.info works for me. Note that for https://hussainwh.info to work, you have to install an app on that domain. When there is no subdomain , it's called the bare/naked/apex/root domain .

Praise for Cloudron's backup system: This is amazing! Digital Ocean charges 30% of the cost of the droplet for daily backups. If your droplet uses Cloudron, you can just use the built in backup to R2 for free and could even have it backup multiple times per day. So cool. Amazing cloudflare is offering so much free storage with r2 as well. I guess eventuallly they may change this but Cloudflare makes integrations so easy it seems trivial to just switch things over to s3 or Backblaze if that time comes. That said, I guess I haven't had to restore from a backup before so this is more just praise for the setup ease but I have faith in Cloudron team based on care I see with the product and in this forum!

@girish Finally, I would like to say that I haven't quite figured out what the problem was. I had used Cloudron bare metal. In the last few days I switched to Windows Server and have Cloudron running in a Linux VM via Hyper V. I then assigned a manual IP there and the problem no longer occurs. I guess it would have been fixed before with a manual IP as well.

This is not possible, no. The structure of data of both the apps are quite different. Also, when you backup Cloudron apps, the code is not part of the backup. LAMP app is sort of a special case here since the code is part of the "data" and part of backup . You should be able to migrate it manually though. Import database and copy over the needed files.

@girish Thanks for answering, I will try it and if I still face any issue, I will update by starting my own thread.

@girish it works! Thanks a lot.

you can check it your self with GRC shields up https://www.grc.com/x/ne.dll?bh0bkyd2

Thank you @girish , this worked. For those coming through in the future note that cloudron-support may ask you to reboot and run again, keep an eye out for it.

Many thanks, after deleting config file for freshrss the restart of nginx went OK.

@humptydumpty thanks for the info! Cloudron should not be affected, no. We don't rely on name servers IPs. Also, I think this is for people having vanity nameservers, which Cloudron does not support.

Thank you @girish - I'll test with v8 and report back thereafter in case of need.

Thank you @girish - Sounds promising. Looking forward to v8.

@girish Hello, no the backup sometimes fails with this error but I don't have any more information. I suspect the bandwidth because I have several servers which backup at night to the same destinations even if the times are staggered, it can happen that the backups are in parallel.

I can now say safely that the backuptask crashes while working with Immich. Maybe I should choose different setting? I switched to Backblaze recently and I am currently using rsync. Maybe there is a way to do this more efficiently considering that there are so many files to upload? I was assuming rsync might be more efficient than a tarball because it only syncs the changes, but I might be wrong?