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.
My domain is: quantummonk.com
I ran this command:plesk with letsencrypt link
It produced this output: Error: Could not issue a Let’s Encrypt SSL/TLS certificate for quantummonk.com .
Your domain in Plesk is hosted on the IP address(es): 188.8.131.52 , but the DNS challenge used another IP address: 184.108.40.206 .
Please check the actual DNS zone of your domain and make sure that the IP addresses in the DNS zone and for the hosting are the same.
Invalid response from https://acme-v01.api.letsencrypt.org/acme/authz/oemjbkz_x9SxUa5q_yZ2Ch6FuBpIbDGcQUI2gcdTg2U.
Detail: Invalid response from https://sites.google.com/a/heartvirtue.com/heart-virtue/ [2607:f8b0:400f:800::200e]: "\n<html "
My web server is (include version): cloudserverM
The operating system my web server runs on is (include version):debian 9 plesk onyx (now) was centos and ubuntu before that.
My hosting provider, if applicable, is:1and1ionos
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):plesk onyx
The version of my client is (e.g. output of
certbot --version or
certbot-auto --version if you’re using Certbot): I am not sure certbot was used in the plesk.
I apologize in advance for my ignorance of ssl in general.
I am learning server management by myself, to include dns ns ip ssl host and hostname etcs, it’s pretty confusing.
I have deployed and deleted multiple server configurations with different domain names which has released and assigned new static ip addresses each time… I have yet to learn how to keep my static IP between deployments but, I am at least on to the fact that i need to now. My keys of course are gone with each deployment. I can use all the help and advice you can give me. I assume if the ns stays the same and the ip changes then their is a problem otherwise if the ns and ip changes then a new cert can be generated… My immediate problem is for quantummonk.com. I am sure I will have the same problem in the near future for ironfortress.org.
I have a couple of domains on another server with your certs but I will be migrating them what will I need to do for them… websitebull.com and theavergearcher.com currently on linode with nginx and ubuntu and accessed only through ssh i.e manually acquired with certbot?