Appcd 3.1.0
Added
- Support for Ubuntu 24.04 (Noble Numbat).
Enhanced
- Reduced log verbosity for srs_milter service.
- Improvement to in-memory website data store for improved control panel performance on larger servers.
Appcd 3.1.0 released and supported Ubuntu 24.04 LTS.
DracoBlue changed the title to Appcd 3.1.0 released and supported Ubuntu 24.04 LTS..
I'm waiting for information from the first brave people who updated to Ubuntu 24.04 LTS 
Ok, my cluster is being hit very lightly today, so I am going to run updates immediately.
ansible script run, everything now up-to-date.
I will update one of our underutilized (as in 2 test sites) servers to 24.04 this evening, and report back.
Upgraded backup server to 24.04. No issues.
- Edited
It is not a good idea to upgrade Ubuntu 22.04 LTS before the release of 24.04.1 LTS.
I recommend waiting until the release of 24.04.1 LTS (scheduled for August 15th, 2024) before upgrading from Ubuntu 22.04 LTS. This ensures superb stability and minimizes potential compatibility issues with your apps.
Ok, I chose to test do-release-upgrade on an unused server in the cluster. It went well except that our Netplan yaml had the older gateway directive, and the actual interface name changed on boot of 24.04. This caused the network interface to be "lost" after upgrade.
Be sure to have net-tools installed in 22.04 to easily find the interface (ifconfig -a) once the update runs.
Change any net config yaml files (if you use cloud init) to the newer directives for the gateway (-to: default ; via ip of router).
After fixing that minor glitch, the server is up running 24.04, and seems to work without issue.
- Edited
DracoBlue I had enhance running on a 24.04 install since last week (upgraded enhance while still on 22.04) on one test VPS, I just renamed the apt sources file to .list today and replaced jammy with noble. All went great for me.
I have also tried a backup server first which is still on 22.04 because it dropped the btrfs partition and would not remount it when I upgraded a test one to 24.04.
- Edited
DracoBlue If you want to upgrade to 24.04
This is how I upgraded.
sudo apt list --upgradable
sudo apt update && sudo apt upgrade -y
reboot
I then used a second ssh port connection for stability
sudo ufw allow 1022/tcp
Make sure all tools are available before upgrade.
sudo apt install update-manager-core
Then I did
sudo do-release-upgrade -d
on two servers I included --allow-third-party as the provider has mirrors
You can select Y or N to remove old packages once finished or manually at a later date
check any third party sources are enabled (eg Ubuntu Pro) they are all under /etc/apt/sources.list.d/
ls -l /etc/apt/sources.list.d/
and reboot
- Edited
3.1.1 just released!
Also tested 24.04 on a new server and works well.
- Edited
My sources.list.d weren't functioning for the Enhance and Docker part after update from 22.04 to 24.04, so I made these files to comply with the 24.04 way of handling apt sources and now they do work:
/etc/apt/sources.list.d/enhance.sources
Types: deb
URIs: https://apt.enhance.com/
Suites: noble
Components: main
Signed-By: /usr/share/keyrings/enhance.gpg
/etc/apt/sources.list.d/enhance.sources
Types: deb
URIs: https://download.docker.com/linux/ubuntu/
Suites: noble
Components: stable
Signed-By: /usr/share/keyrings/docker-archive-keyring.gpg
I reinstalled and migrated the DNS, Backup and Mail servers on new 24.04 servers. CP and Web servers are still on 22.04. So far the 24.04 are working fine, no issues. CP and appcd on latest versions on all servers.
- Edited
rdbf Usually during the upgrade the sources get updated, if they don't update they will be named eg enhance.list.distUpgrade. Ubuntu Pro updated automatically.
To fix the sources you need to edit the file and replace jammy with noble and then save and rename to .list using the old format which will work or as you posted using that format.
If you just rename the .list.distUpgrade file to .sources then you will get an update error ---> Malformed stanza 1 in source list.
As I already upgraded the OS on a test VPS last week still using the 3.01 appcd, I just changed the apt list files from jammy to noble today for the new version.
Updated from the original sources and saved as .list
deb [arch=amd64, signed-by=/usr/share/keyrings/enhance.gpg] https://apt.enhance.com noble main
and
deb [arch=amd64 signed-by=/usr/share/keyrings/docker-archive-keyring.gpg] https://download.docker.com/linux/ubuntu noble stable
Probably should update the files to match the newer format though for future updates
In the docs still Ubuntu 22.04 LTS server as hardware requirement (https://enhance.com/docs/getting-started/installation-guide.html#installation-steps), does this mean that this is no longer the case?
I'm about to test the panel on a new server so I was wondering whether to go to 24.04 already.
