SSL Certificate Error: DNS Challenge used another IP address


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., 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:
We are using Let’s Encrypt as a plugin on Plesk and found the following when trying to generate an SSL certificate for the domain via GUI. We have used certificates from other vendors in the past.
I have used nslooked & dig using several different DNS providers and all return the correct IP address of
Question is why does it seem that Let Encrypt is trying to contact

It produced this output:
Error: Could not issue a Let’s Encrypt SSL/TLS certificate for .

Your domain in Plesk is hosted on the IP address(es): , but the DNS challenge used another IP address: .
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
Type: urn:acme:error:unauthorized
Status: 403
Detail: Invalid response from []: 404

My web server is (include version): Apache

The operating system my web server runs on is (include version): Cento 6.9

My hosting provider, if applicable, is: We are the provider

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 12.5.30 Update 76


The authorization is for the name, for which is the correct IP address.

Plesk is trying to get a certificate for, it’s failing, and Plesk is saying “Could not issue a Let’s Encrypt SSL/TLS certificate for”

Do you know why? Is the domain set as an alias in Plesk? Are you requesting a certificate for both domains?


It’s actually the other way around in plesk. is an alias for
I’d missed that key part, I’ll see if we can get the DNS for .com changed, unfortunately we do not control the DNS.
Thanks for your help


This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.