Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
I ran this command:
It produced this output:
My web server is (include version): Apache 2.2
The operating system my web server runs on is (include version):CentOS 6
My hosting provider, if applicable, is:
I can login to a root shell on my machine (yes or no, or I don’t know): yes
I’m using a control panel to manage my site (no, or provide the name and version of the control panel): No
The version of my client is (e.g. output of
certbot --version or
certbot-auto --version if you’re using Certbot): certbot-auto version 0.30.0
I just upgraded my certbot client and, although no errors were reported on screen, reported all successful, our websit no longer works. IS browser reports:
Version:1.0 StartHTML:000000215 EndHTML:000001485 StartFragment:000000961 EndFragment:000001435 StartSelection:000000961 EndSelection:000001431 SourceURL:res://ieframe.dll/invalidcert.htm?SSLError=117440512
Your PC doesn’t trust this website’s security certificate.
The website’s security certificate is not yet valid or has expired.
The hostname in the website’s security certificate differs from the website you are trying to visit.
Error Code: DLG_FLAGS_INVALID_CA
Expires on: Mar 26, 2014
Current date: Jan 23, 2019
then lists PEM encoded chain
If I go to https://www.maglin.com with chrome, I get the “Your connection is not private” message
Clicking Advanced reports:
The server could not prove it is www.maglin.com; its security certificate is not trusted by your computer’s operating system. This may be caused by a misconfiguration or an attacker intercepting your connection.
If I click on the Not secure button beside the URL, one of the options is: Certificate (invalid). If I click on this, it says
This CA Root certificate is not trusted. To enable trust, install this certificate in the Trusted Root Certificate Authorities store.
What is that?
Initially I thought that SSL had just not been enabled and tried a certbot-auto renew (I can’t recall now if it was this one or not, but I did get prompted to enable SSL, so I chose that. Then prompted to redirect all HTTP to HTTPS, and chose that. Can’t get to any pages on our website : www.maglin.com.
Our site is set up as a virtual host under Apache.
Curious that Chrome is taken to the Apache server root when entering www.maglin.com.
I am at a loss to determine what went wrong. As I said, certbot-auto reports all ok