E: The repository 'https://mirror.mva-n.net/mariadb/repo/10.4/ubuntu focal Release' no longer has a Release file


I wanted to update my server, but I obtain this error:

# apt update
Get:1 http://mirrors.online.net/ubuntu focal InRelease [265 kB]
Hit:2 http://mirrors.online.net/ubuntu focal-updates InRelease
Hit:3 http://mirrors.online.net/ubuntu focal-backports InRelease
Hit:4 http://ppa.launchpad.net/ondrej/apache2/ubuntu focal InRelease
Hit:5 http://ppa.launchpad.net/jonathonf/vim/ubuntu focal InRelease
Hit:6 https://nginx.org/packages/mainline/ubuntu focal InRelease
Hit:7 http://ppa.launchpad.net/ondrej/php/ubuntu focal InRelease
Ign:8 https://mirror.mva-n.net/mariadb/repo/10.4/ubuntu focal InRelease
Hit:9 https://apt.hestiacp.com focal InRelease
Err:10 https://mirror.mva-n.net/mariadb/repo/10.4/ubuntu focal Release
  404  Not Found [IP: 443]
Hit:11 http://security.ubuntu.com/ubuntu focal-security InRelease
Reading package lists... Done
E: The repository 'https://mirror.mva-n.net/mariadb/repo/10.4/ubuntu focal 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.

What should I do, please?


Could be the repo was momentarily down. It looks like it’s back up. Rerunning the update should complete.

1 Like

I read: E: The repository ‘mirror - MvA focal Release’ no longer has a Release file.

There is no ‘release file’, the server is reachable.

nano /etc/apt/sources.list.d/mariadb.list

And change the url out with:

Or any other version:


It works, but it seems it’s not the same version of MariaDB. No problem?

13 packages can be upgraded. Run 'apt list --upgradable' to see them.
[email protected]:/etc/apt/sources.list.d# apt list --upgradable
Listing... Done
galera-4/unknown 26.4.11-focal amd64 [upgradable from: 26.4.9-focal]
initramfs-tools-bin/focal-updates 0.136ubuntu6.7 amd64 [upgradable from: 0.136ubuntu6.6]
initramfs-tools-core/focal-updates,focal-updates 0.136ubuntu6.7 all [upgradable from: 0.136ubuntu6.6]
initramfs-tools/focal-updates,focal-updates 0.136ubuntu6.7 all [upgradable from: 0.136ubuntu6.6]
libmariadb3/unknown 1:10.4.23+maria~focal amd64 [upgradable from: 1:10.4.22+maria~focal]
mariadb-client-10.4/unknown 1:10.4.23+maria~focal amd64 [upgradable from: 1:10.4.22+maria~focal]
mariadb-client-core-10.4/unknown 1:10.4.23+maria~focal amd64 [upgradable from: 1:10.4.22+maria~focal]
mariadb-client/unknown 1:10.4.23+maria~focal all [upgradable from: 1:10.4.22+maria~focal]
mariadb-common/unknown 1:10.4.23+maria~focal all [upgradable from: 1:10.4.22+maria~focal]
mariadb-server-10.4/unknown 1:10.4.23+maria~focal amd64 [upgradable from: 1:10.4.22+maria~focal]
mariadb-server-core-10.4/unknown 1:10.4.23+maria~focal amd64 [upgradable from: 1:10.4.22+maria~focal]
mariadb-server/unknown 1:10.4.23+maria~focal all [upgradable from: 1:10.4.22+maria~focal]
mysql-common/unknown 1:10.4.23+maria~focal all [upgradable from: 1:10.4.22+maria~focal]

It is a newer version …

10.4.23 vs :10.4.22

Hi there. I have the same issue during “apt-get update” for mirror - MvA

There was another conversation about this issue in a closed topic previously:
Repository error

This issue happened again this month too. I’ve reinstalled HestiaCP again after OS-rebuilt and it had encountered this error during installation too, it seems its about MariaDB. but my phpmyadmin works flawlessly after installation! Should I reinstall my hestiaCP again later after their SSL issue fixed again or not? what’s that package exactly?

It has been an issue quite often It should resolve it self…

what happens if this issue happens during --force installation? Should I reinstall later?

The issue has been resolved on repository side, which was not related to or in range of hestia. The update process is working properly, tested on ubuntu 18.04 and 20.04.

UPDATE: 10.3 and 10.4 are working properly, 10.5 and 10.6 are still buggy. We’re monitoring the situation.

UPDATE2: We reached out to mva with a request to fix their repository.


Update3: MVA replied to our request, they are currently checking their repo and will report back asap.

1 Like

Update4: mva has resolved the issue, we’re currently implementing another way to use the mariadb repository.