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. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
My domain is:mk1.contrado.cloud
My web server is (include version): CentOS 7
The operating system my web server runs on is (include version): CentOS 7
My hosting provider, if applicable, is: N/A
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): 1.30.0
This is a playground VM, so I'm not too bothered about it. Just can't quite figure out why when I load the website up it over https it is showing up as a certificate for localhost.localdomain.
It's running Apache/httpd web server
There is nothing on this server other than an index.html file
I've set up Let's Encrypt countless times, but never seen this one before.
I've opened up on the CentOS 7 firewall both HTTP and HTTPS
I have a feeling that it's likely due to a few incorrect configs while playing with this VM that something was done in the wrong order and things have got tied in a bit of a knot.
Not sure what the best way of debugging this one is to get it working.
Certbot was installed via snap.
I'd prefer not to bin off the VM and start from scratch - even though I know this would fix the problem. I'd like to debug it to get it working.