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.
It produced this output: It produced a cert issued to virtualserver.me (the domain for my VPS server) and this causes browsers to think its an invalid certificate. I also tried generating the cert using apache 2.4 and nginx 1.14.
My web server is (include version): I tried with both Apache and nginx
The operating system my web server runs on is (include version): Ubuntu 18.04
My hosting provider, if applicable, is: AWS Lightsail
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 I use the command line
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot): 0.28.0
It definitely produced the correct certificate (4 times, in fact) but Apache is choosing not to use that certificate.
You need to take a look at your Apache configuration and see how each of your <VirtualHost *:443> are configured, and with what certificate.
One place to start:
grep -Ri SSLCertificateFile /etc/apache2
If you used certonly in your Certbot command, then Certbot wouldn't automatically install the certificate for you. You'd have to manually configure Apache to use it.
To do it automatically, you'd use certbot --apache instead of certbot certonly --standalone.
What does certbot certificates say? I agree with @_az’s impression that the server that you see when you visit the site in a browser is not the same certificate that Certbot has saved on the disk (and that your web server configurations are apparently pointed to).
What is virtualserver.me? Is that also your domain? Can we assume that you’re the only person using this VPS and that it’s not in some kind of container or behind some kind of reverse proxy or CDN?
I have several domains on my VPS. VirtualServer.me is the primary. AllThingsCyber.tech and CoreyHolzer.com are currently the two additional domains. I will be moving others over to the VPS as well but those sites are currently live at another hosting provider. I do not want to more them until I get this problem resolved.
To answer @rg305’s question. NGINX is the only server running right now and it’s handing both ports. I have both servers installed on the box so I can do some performance analysis before choosing one for production.
CH.com should not be redirecting to VS.me. I did not set it up that way. I will take a look at my DNS records and double check my web server configurations.
It's not your DNS setting. These are http redirects, so this is your vHost-definition. And - perhaps - the wrong vHost answers - with the wrong certificate.
OK, problem solved for nginx and it was a ubtk error. I had a bad symbolic link in my sites-enabled directory. There are multiple issues with apache at the moment but since they are not certificate related I will look for help in the proper community.