Upgrading MariaDB on the Enhance Control Panel is generally a smooth process. However, in rare cases, you may encounter connectivity issues when reaching the MariaDB repositories. These issues are typically related to either IPv4 or IPv6 connectivity, not on your server, but on the MariaDB repository side.
If you run into the following error during an update:
E: The repository ‘https://dlm.mariadb.com/repo/mariadb-server/11.4/repo/ubuntu noble Release’ no longer has a Release file.
N: Updating from such a repository can’t be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
…don’t panic. Below are some tried-and-tested solutions you can attempt before looking into alternative approaches.
Solution 1: Clear and Refresh Repository Lists
In some cases, cached repository data may be causing the issue. You can clear the MariaDB list files and refresh the package index:
rm /var/lib/apt/lists/*mariadb*
apt update
apt upgrade
Solution 2: Force IPv6
Conversely, if IPv4 connectivity is problematic, forcing IPv6 may resolve the issue:
sudo apt -o Acquire::ForceIPv6=true update && sudo apt -o Acquire::ForceIPv6=true upgrade -y
Solution 2: Force IPv4
If the MariaDB repo is experiencing IPv6 connectivity issues, you can force your server to use IPv4 for the update process:
sudo apt -o Acquire::ForceIPv4=true update && sudo apt -o Acquire::ForceIPv4=true upgrade -y
Final Notes
- These solutions address the most common connectivity problems encountered when updating MariaDB on Enhance Control Panel.
- If none of the above works, the issue may be on the MariaDB mirror itself, in which case waiting for a resolution from their side or switching to an alternative mirror may be necessary.
- And of course, if you’d rather not troubleshoot this alone, don’t hesitate to reach out to the GOZEN Support Team. We’re here to help.
