• 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 Could not issue a Let's Encrypt SSL/TLS certificate

Schoelje

New Pleskian
When I renew my domain's Let's Encrypt certificate I get this error:

Error: Could not issue a Let's Encrypt SSL/TLS certificate for example.net.

The authorization token is not available at http://example.net/.well-known/acme-challenge/some-has-code.
To resolve the issue, make it is possible to download the token file via the above URL.
See the related Knowledge Base article for details.
Details
Invalid response from https://acme-v01.api.letsencrypt.org/acme/authz/another-hash-code.
Details:
Type: urn:acme:error:unauthorized
Status: 403
Detail: Invalid response from http://example.net/.well-known/acme-challenge/some-hash-code [ip6.address]: 404

I verified that /var/www/vhosts/example.net/example.net/.well-known/acme-challenge/some-hash-code exists. However, a wget with the URL gives me a 404 not found.

This might have something to do with the fact that I have these additional Apache directives configuration to forward my plone site to the domain example.net, but I'm not sure:

RewriteEngine On
RewriteRule ^/(.*) http://example.net:1234/VirtualHostBase/https/%{HTTP_HOST}:443/Plone/VirtualHostRoot/$1 [P,L]

Does anybody know what's happening here and what can I do about it?

Note that example.net is not the actual domain name.
 
Last edited:
I was just able to renew the certificate for this domain.

First, I tried to add an Alias to the Apache directives but because of the existing rewrite this didn't work:

Alias /.well-known/acme-challenge/ /var/www/vhosts/example.net/example.net/.well-known/acme-challenge/

So, I added the alias to the nginx directives of the domain:
location /.well-known/acme-challenge/ {
alias /var/www/vhosts/example.net/example.net/.well-known/acme-challenge/;
}
 
Back
Top