SSL certificates don't seem to be written after 7.40.0 upgrade

SYSTEM INFORMATION
OS type and version Debian Linux 12
Usermin version 2.400
Virtualmin version 7.40.0
Theme version 25.01
Apache version 2.4.65
Package updates All installed packages are up to date

Hi there,

Since the last update, I’ve been encountering a possible bug when updating SSL certificates. When I update the certificate of a Virtual Server, Virtualmin shows no error…

…but in reality, the certificate is not updated.

My certificates are stored in the root directory of each Virtual Server. The corresponding files look like they have been modified…

… but they still contain the old certificate.

This happens on several different Virtual Servers (and actually on several different servers, all running Debian 11 or 12).

Check that certificates in the browser, are the dates updated?
I just tested and updated fine.

You screenshot shows todays dates 10th of sept.

Which “SSL certificate file” and “SSL private key file” are referenced on “Manage Virtual Server ⇾ Setup SSL Certificate” page?

Thank you for your replies (and sorry for not creating a new topic)!

Even though the files dates have indeed changed and match the attempts to update the certificates (suggesting that they were edited), the signed certificates were not updated and the old certificates are still in place. This is confirmed in the browser (that’s actually how I initially noticed it), which still shows the old certificates.

The file paths are correct in “Manage Virtual Server ⇾ Setup SSL Certificate”: /home/user/ssl.cert and /home/user/ssl.key.

For your information, these are DigiCert/RapidSSL certificates, but I don’t think that makes any difference. At this point, I’ve worked around the issue by manually editing the ssl.cert, ssl.combined, and ssl.everything files (+ restarting Apache).

Have you tried another browser just to make sure there is no browser caching issue, i have found chrome tends to cache some certificates and switching to firefox the issue is resolved. In tbis instance I have stopped chrome and restarted it an the new certificate is used

Yes, I did that (and yes, I also first suspected a caching issue). That wasn’t the explanation … and I should add that after manually editing the ssl.cert, ssl.combined, and ssl.everything files (+ restarting Apache and refreshing the sites in Chrome), the certificates were updated and the problem was fixed.

I know it’s strange. I’m starting to think it might be a mistake on my part with the new look of the “Manage Virtual Server ⇾ Setup SSL Certificate” page. At the next certificate renewal, I’ll check everything step by step to document it in case the problem happens again.

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.