I did make a domain name change for an existing domain (same name but different tld from .fr to .com) on the same IP, same machine, same server, same everything but the name. DNS is already propagated and ok, site with new name up and running, I tried to obtain new certs for the new domain but it’s like the system thinks I’m still on the old domain (see error below). I then erased the .well-known folder and all certs and re-generated self-signed certs, and then requested again Let’s Encrypt certr, same, still the same error like there is some kind of cache somewhere … any idea ?
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: asking for cert
My web server is (include version):Apache 2.4
The operating system my web server runs on is (include version): Debian 9
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):