You are not logged in.
After the webserver exited erroneously, the repositories are available through HTTP and HTTPS again.
The reason for the outage is Launchpad bug #1897561. A workaround has been implemented and the issue should not occur again. The server process died when certbot renewed the Let's Encrypt SSL certificate, and told the server process to reload, which is a trigger for this bug.
Music makes us braver
Offline
Is this why I get this (see below) when running apt update
Err:8 https://pkg.bunsenlabs.org/debian buster-backports Release
Certificate verification failed: The certificate is NOT trusted. The certificate issuer is unknown. Could not handshake: Error in the certificate verification. [IP: 78.47.156.207 443]
Reading package lists... Done
E: The repository 'https://pkg.bunsenlabs.org/debian buster-backports 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.
Offline
Is this why I get this (see below) when running apt update
Err:8 https://pkg.bunsenlabs.org/debian buster-backports Release Certificate verification failed: The certificate is NOT trusted. The certificate issuer is unknown. Could not handshake: Error in the certificate verification. [IP: 78.47.156.207 443] Reading package lists... Done E: The repository 'https://pkg.bunsenlabs.org/debian buster-backports 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.
This has been fixed now, but the reason for this error is different. Please see announcement https://forums.bunsenlabs.org/viewtopic.php?id=7226 for details.
Music makes us braver
Offline
I updated just before twoions post, without problems.
The cerificate is ok and https://eu.pkg.bunsenlabs.org/debian/di … ts/Release file is present.
// Regards rbh
Offline
Try to import BL apt-key again:
# wget https://pkg.bunsenlabs.org/debian/pool/main/b/bunsen-keyring_2020.10.10+bl9-1_all.deb
# dpkg -i bunsen-keyring_2020.10.10+bl9-1_all.deb
or
# wget -q https://eu.pkg.bunsenlabs.org/BunsenLabs-RELEASE.asc -O- | apt-key add -
Edit:
If still error, clean apt-cache and run apt-update again.
Last edited by rbh (2020-12-24 20:31:30)
// Regards rbh
Offline
@rbh This shouldn't be necessary. Sorry for butchering your post, but these were outdated package versions and an outdated URL, which I found best to remove from an announcement post.
Music makes us braver
Offline
@rbh This shouldn't be necessary.
Yeah, I guess the error @superos posted, was from before you fixed the error...
And I had an old adress to the apt-key...
Last edited by rbh (2020-12-24 20:42:07)
// Regards rbh
Offline
superos wrote:Is this why I get this (see below) when running apt update
Err:8 https://pkg.bunsenlabs.org/debian buster-backports Release Certificate verification failed: The certificate is NOT trusted. The certificate issuer is unknown. Could not handshake: Error in the certificate verification. [IP: 78.47.156.207 443] Reading package lists... Done E: The repository 'https://pkg.bunsenlabs.org/debian buster-backports 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.
This has been fixed now, but the reason for this error is different. Please see announcement https://forums.bunsenlabs.org/viewtopic.php?id=7226 for details.
Thanks. All fine now.
Offline