• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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