certificate expired qubes.notset.fr

[profeshish]

How to file a helpful issue

Qubes OS release

4.0

Brief summary

the certificate for the domain that qubes uses to upgrade its distro has had an expired certificate since the 18th, visited the website manually and looked at the certificate and it is expired.

Steps to reproduce

-run sudo qubes-dom0-update -y qubes-dist-upgrade from dom0 terminal -should give a certificate error

Expected behavior

Actual behavior

[Minimalist73]

qubes.notset.fr is not the official Qubes repository, it's a personal repository from a Qubes team member. I'm not sure why you are using that in dom0. Since you are trying to install qubes-dist-upgrade, I guess you are trying to upgrade to a newer Qubes version. You should backup all your qubes with Qubes Backup and restore them on a clean 4.2 installation.

https://www.qubes-os.org/doc/upgrade/4.2/#clean-installation

[andrewdavidwong]

@fepitre

[andrewdavidwong]

@alimirjamali wrote in a forum post:

That domain is hosted by fepitre and hosts repositories of unsupported Qubes OS versions. adw has mentioned fepitre in the issue comments but not received a reply. Looking at the domain right now shows proper valid Let’s Encrypt certificate. Most probably with proper auto-renewal using certbot or similar. Looking at Certificate issuing history, shows proper and timely renewals. I believe the issue to be invalid. The only possibility that comes to mind would be if user had been trying to update an ancient version of Qubes OS which did not have ISRG Root X1 root certificate in updatevm but only DST Root CA X3. In that case, user should update via http, hopefully to a newer Qubes OS version.

[github-actions[bot]]

This issue has been closed as "not applicable." Here are some common examples of cases in which issues are closed as not applicable:

• Help and support requests (please see Help, support, mailing lists, and forum)
• Questions (please see Help, support, mailing lists, and forum)
• Discussion issues (please see Help, support, mailing lists, and forum)
• Bug reports for behavior that is already working as intended
• Enhancement requests to improve things that are already working as intended
• Issues that rest on mistaken assumptions or misunderstandings
• Issues that do not provide enough information
• Issues that are not actionable

We respect the time and effort you have taken to file this issue, and we understand that this outcome may be unsatisfying. Please accept our sincere apologies and know that we greatly value your participation and membership in the Qubes community.

Regarding help and support requests, please note that this issue tracker (qubes-issues) is not intended to serve as a help desk or tech support center. Instead, we've set up other venues where you can ask for help and support, ask questions, and have discussions. By contrast, the issue tracker is more of a technical tool intended to support our developers in their work. We thank you for your understanding.

If anyone reading this believes that this issue was closed in error or that the resolution of "not applicable" is not accurate, please leave a comment below saying so, and we will review this issue again. For more information, see How issues get closed.