Cloudron Forum

Ah, thanks! I was already running 8.0.5, but the upgrade to 8.0.6 got stuck. /home/yellowtent/box/setup/start.sh came up with an unbound error. I was able to start box manually and start all apps, but the backup volume did not mount. After installing unbound-anchor, I was able to run /home/yellowtent/box/setup/start.sh without errors, and now the backup is working again.

This seems to be targeting the desktop flavor of Ubuntu 24.04. So this does not directly apply to Cloudron. For Cloudron, please follow https://docs.cloudron.io/guides/upgrade-ubuntu-24/

Many thanks, all. I missed that bit of the documentation.

I'll definitely backup; I'm running on bare hardware, and didn't even do myself the courtesy of running Cloudron in a VM. I may... use this as an opportunity to change that.

Either way, this is all I needed. Thank you!

We haven't added a way to add custom persistent iptables rules . For SSH though, just move it port 202 and disable root auth and password auth. This usually cuts down all bots to 0.

Ok that file is showing regular checks but no packages marked for upgrade. I will keep an eye on this. Thanks for the support.

@nebulon Thanks to you and @girish for explaining this.

@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.

@alwi said in Ubuntu-server 24.04:

pardon. https://gnulinux.ch/windows-11-produktschluessel

Um, that's irrelevant, the correct link was https://gnulinux.ch/cloudron-1-einfuehrung

Thanks, it's solved. No disk wasn't changed. It's running on AWS.

You can also check apt list --upgradable | grep security if those are actually security updates.

@girish Thanks for the quick reply, 👍.

In case anyone else needs this on 22.04, I followed these steps and was able to get the system to boot with full disk encrypted drive with the private key coming from the tpm and no password needing to be typed.

I don't think this uses the same libraries as the new option in 23.10 so I expect that when 24.04 comes out I will do a fresh OS install to use the better supported FDE TPM integration from that version going forward but as a stop gap I am happy with this for now.

@scooke said in Can't start upgrade from Ubuntu 20.04 to Ubuntu 22.0x because of "no development version of an LTS available" error:

This has an interesting bit about the -d. https://askubuntu.com/questions/1412543/how-does-exactly-do-release-upgrade-d-work#:~:text=The command do-release-upgrade,version of an LTS available. .

wow, great link.

@robw I have fixed the guide to remove the -d flag. Thanks for reporting.

This has not been tested by us at least and given that 23.04 is not an LTS there is probably no big rush if at all to support it.

Yes, anyone attempting the install, even locally, is useful to grab the log and get a sense of the changes and how the installer might need to be modified.

So go ahead, even if it doesn't work, it's useful data.

No fear!

We can't change the doc page yet atleast until 7.5 is stable. Also, 18.04 is still supported to install pre-7.4 releases.

tl;dr - If you have the above problem apt install python3-magic . Then, run apt update . On another server, unattended-upgrades package was missing as well (!) Not sure how because Cloudron installs it at install time. So, install it and run unattended-upgrade -d.

@necrevistonnezr Thank you for your answere.
I am just tryin to learn things step for step and take my time 🙂
added you in discord 🙂

Okay i never was been here before in this forum.
this is sad what trolls are tryin

i just here to improve my skills at the points where there are. clearly i am a little bit late with 29 to focus an such beginner things other learn with 15-19 but its never to late i guess 🙂

@benborges Ah ok. Maybe you can wait for 7.3. Please update to that and try to update again and we can debug further. There are some cgroup v2 related fixes for Ubuntu 22 in 7.3 which affect docker container creation, it's possible you hit that case.

@bubonicfred said in Submit Cloudron to Ubuntu for Publication:

You can install snapd on non-ubuntu systems. Though I have no idea if they have any advantage over flatpak or appimage.

Yep, except it turns that we want to get away from snap instead of adopting it for some reasons mentioned here above, so well that's a choice 😉