Apt update error

[R0GGER]

When I run apt update I get the error below…
OS: Debian 11.2

Please your help.

Ign:8 https://mirror.mva-n.net/mariadb/repo/10.6/debian bullseye InRelease
Err:9 https://mirror.mva-n.net/mariadb/repo/10.6/debian bullseye Release
  404  Not Found [IP: 195.65.111.42 443]
Reading package lists... Done
E: The repository 'https://mirror.mva-n.net/mariadb/repo/10.6/debian bullseye 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.

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

[R0GGER]

Uhm…

https://mirror.mva-n.net/mariadb/repo/10.6/debian bullseye Release

10.6 = Debian Buster

[Raphael]

… 10.6 is the mariadb version. There is no need to open a new thread, situation is still the same:

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

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.

[pluto]

Just a quick observation … I was having problems with this on all servers still running on mariadb 10.4, but later versions seemed OK. I decided to go ahead and upgrade the DB with the hestia script, as I was planning to do that anyway, and the problem went away as soon as I was on 10.6.
/usr/local/hestia/install/upgrade/manual/upgrade_mariadb.sh
I’m not suggesting that everyone do this, but as I was going to do it anyway, it solved the issue for me.
[Not that the failure to update was at all dangerous, just irritating.]

[eris]

The issue with apt errors was related to a syncing issue between the repo we used and the source…

We will adjust the apt repo to https://github.com/hestiacp/hestiacp/commit/4f6ce61e2ec31a4ac5575e5d807cc7c4ddc09ccf

[pluto]

OK, fair enough. In which case, I should mention that the URL added to apt by the upgrade_mariadb.sh script is also
deb [arch=amd64] https://mirror.mva-n.net/mariadb/repo/10.6/ubuntu focal main
So you might want to include that in your patch too.

[eris]

Good point

[R0GGER]

Problem solved. No errors.

$ apt update

Hit:1 http://security.debian.org bullseye-security InRelease
Hit:2 http://ftp.debian.org/debian bullseye InRelease
Hit:3 http://ftp.debian.org/debian bullseye-updates InRelease
Hit:4 https://packages.sury.org/apache2 bullseye InRelease
Hit:5 https://nginx.org/packages/mainline/debian bullseye InRelease
Hit:6 https://packages.sury.org/php bullseye InRelease
Hit:7 https://apt.hestiacp.com bullseye InRelease
Hit:8 https://mirror.mva-n.net/mariadb/repo/10.6/debian bullseye InRelease
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done

[nextcloudistcool]

same here
Index of /mirror/mariadb.org/repo/10.5/ubuntu/ focal Release
404 Not Found [IP: 80.237.136.138 80]

depot includes no release datafile
an update could not be started securely out of such data origin (depot)

[eris]

@nextcloudistcool

depot includes no release datafile

I assume you have used some translation software.

It should be fixed right now apt update should work If not:

https://dlm.mariadb.com/repo/mariadb-server/$mariadb_v/repo/$VERSION

Where mariadb_v = 10.x
And version = Debian or Ubuntu

[nextcloudistcool]

Thanks for you reply! Yes, it was a translation software: Me:) Only for information: The link you did send was 404 and the update possibility for mariadb did not wor for two further days. Today it runs! hopefully through.