• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

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