• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue Security Advisor issue

mattd29

New Pleskian
I have installed security advisor, added cp.domain.co.uk to the DNS and its working but I still get this

Error: IMPORTANT NOTES:
- The following errors were reported by the server:

Domain: cp.domain.co.uk
Type: unauthorized
Detail: Invalid response from
http://cp.domain.co.uk/.well-known/acme-challenge/DU9okEpkiFtsBgV1e9GDZ1w3RsFSSgsLD4WyfWVZmyw:
"<HTML>
<HEAD>
<TITLE>404 Not Found</TITLE>
<BASE href="/error_docs/"><!--[if lte IE 6]></BASE><![endif]-->
</HEAD>
<BODY>
<H1>No"

To fix these errors, please make sure that your domain name was
entered correctly and the DNS A record(s) for that domain
contain(s) the right IP address.
Failed authorization procedure. cp.domain.co.uk (http-01): urn:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from http://cp.domain.co.uk/.well-known/acme-challenge/DU9okEpkiFtsBgV1e9GDZ1w3RsFSSgsLD4WyfWVZmyw: "<HTML>
< HEAD>
< TITLE>404 Not Found</TITLE>
< BASE href="/error_docs/"><!--[if lte IE 6]></BASE><![endif]-->
< /HEAD>
< BODY>
< H1>No"
 
Check your DNS whether it includes a wildcard-subdomain for your domain. That might be missing so that Let's Encrypt claims a DNS error. The domain that you want a certificate for must point to the IP address of the host in the DNS record.

Example: You are pointing domain.co.uk and *.domain.co.uk to the IP address of the host = everything will work find. But if you are only point domain.co.uk to your host, the host might be able to deliver subdomains, but DNS check by Let's Encrypt will fail.
 
Check your DNS whether it includes a wildcard-subdomain for your domain. That might be missing so that Let's Encrypt claims a DNS error. The domain that you want a certificate for must point to the IP address of the host in the DNS record.

Example: You are pointing domain.co.uk and *.domain.co.uk to the IP address of the host = everything will work find. But if you are only point domain.co.uk to your host, the host might be able to deliver subdomains, but DNS check by Let's Encrypt will fail.

I've created the DNS record for the host its called cp.domain.co.uk and its an A record pointing to the IP address as is the domain.co.uk so they both resolve to the same place, am I missing something here ?
 
Back
Top