• 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.

Resolved Can't get Let's Encrype SSL for a temporary domain

glglchn

New Pleskian
I am having problem installing SSL from Let's Encrypt for a temporary domain. Any help is appreciated.

I added a temporary domain in Plesk to build a site before going live. However, I was not able to access the site, even the Plesk default page, due to potential security issue:

xxxxx.plesk.page has a security policy called HTTP Strict Transport Security (HSTS), which means that Firefox can only connect to it securely. You can’t add an exception to visit this site.

So I tried to add a Let's Encrypt SSL certificate, but it repeatedly failed, even though DNS is enabled in DNS Settings under Hosting & DNS and the txt record for the certificate is added. The detail of the error message is as the following:

Invalid response from https://acme-v02.api.letsencrypt.org/acme/authz-v3/xxxx

Details:

Type: urn:ietf:params:acme:error:unauthorized

Status: 403

Detail: No TXT record found at xxx.plesk.page

When I use the NSLookup to check for the DNS record, the query was refused.
 
Since you dont manage the DNS for plesk.page, you cannot use wildcard certificates.
Generate one with only the domain, no wildcard/subdomains etc
 
I too am looking for a way around this. I am setting up a staging environment for a WordPress multi-site using subdomains which requires wildcard SSL certification. Is there no other option for this?
 
@robskinn, no, unfortunately there is no workaround, because you must own the plesk.page zone to set a wildcard DNS record there. But that would apply to all other users globally, too. I suggest to get a cheap real domain name, then you can easily use wildcards, because you are in control of the domain.
 
Back
Top