• 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 Verifying Let's Encrypt when not using root domain or DNS

Brandon Turpin

Basic Pleskian
I have customers point their cname for www to me (because I do not want to deal with the ip addresses changing on everyone as I grow), and they have a domain redirect from the root domain to the www. So when they visit the site it will always go to the www cname.

If you visit the .well-known/acme-challenge url on the www domain it is there, but there is no way to access it on the root domain. I do not have my customers point their dns because most of them have other dns settings they manage elsewhere. We only do the website.

How can I get the Let's Encrypt certificate to verify from the www domain? Since I do not have access to their dns I can not add the DNS authorization.
 
Back
Top