I used an shared hoster for my website and want now to move to my own server with Traefik and Let's Encrypt.
The Problem is, that the shared hoster uses also Let's Encrypt and I can't access the certificate on the shared hoster. Is there a way of revoke or overwrite the certificate. Traefik can't create a new certificate after changing the A Record to the new host.
Traefik can't create a new certificate after changing the A Record to the new host.
Whatever the reason for that is (and you've given us literally nothing to go on to help figure it out), it has nothing to do with an existing cert for your domain.
Unfortunately you're not giving us much to work with. Too vague, too little details. Please answer the questionnaire you should have been provided with when you opened this thread in the #help section:
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:
I ran this command:
It produced this output:
My web server is (include version):
The operating system my web server runs on is (include version):
My hosting provider, if applicable, is:
I can login to a root shell on my machine (yes or no, or I don't know):
I'm using a control panel to manage my site (no, or provide the name and version of the control panel):
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):
Yes, you are absolutely right. That was far too little. I was already too much into problem solving that I assumed too much for given.
in my head my question was also aimed at whether two certificates can get in the way. Since I am suddenly requesting for the same domain with a different private key. In addition, I also chose the wrong tag with Help.
After I restarted the Traefik container, everything worked fine.
But I would still be interested in how Let's Encrypt handles it when I suddenly request a certificate with a new server for an already certified domain. Are there no problems with the verification?