Facebook
Twitter-
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!
-
We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies! -
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 Could not issue/renew Let`s Encrypt certificates
- Thread starter tanasis
- Start date
@Peter Debik , the 1st installation was OK.
The renew have problem. Not only for this domain, but for all domain im using in Cloudflare.
The renew have problem. Not only for this domain, but for all domain im using in Cloudflare.
When you do not use the built-in nameserver in your host, your host cannot update the TXT record for your SSL wildcards. In that case you must update their TXT records manually every three months. As that has not been done, SSL fails to renew, because the TXT record does not match the token that the Let's Encrypt trust center expects to validate domain ownership.
Can't be helped, validation for wildcard domains requires the TXT record in DNS as you have to prove more control over the host than with just a single domain.
Otherwise, with well-known only, you could generate a cert valid for subdomains outside of the scope belonging to you, so you have to prove that you could mess with their dns anyway as to enable you to get certs for any subdomain possible.
Otherwise, with well-known only, you could generate a cert valid for subdomains outside of the scope belonging to you, so you have to prove that you could mess with their dns anyway as to enable you to get certs for any subdomain possible.
