Error getting LE cert in Plesk - looking for token in the wrong place?


#1

Hi all,

Trying to get a cert issued on this domain - myhalto.com

It’s on a Plesk managed server using the Plesk LE extension.

When I try to issue a cert for this domain I get the following error;

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

The authorization token is not available at http://myhalto.com/.
The token file '/var/www/vhosts/myhalto.com/httpdocs//' is either unreadable or does not have the read permission.
To resolve the issue, correct the permissions on the token file to make it is possible to download it via the above URL.
See the related Knowledge Base article for details.
Details
Invalid response from https://acme-v01.api.letsencrypt.org/acme/authz/E-w_yE2SmOkXLaBrINV6YV6ZUGLfZZWpsSeAN-PsFTI.
Details:
Type: urn:acme:error:unauthorized
Status: 403
Detail: Invalid response from http://halto.co.uk/.well-known/acme-challenge/Av4egpsRz8F9KCcnLYiF_utA8wsaceQ5dfZag3RiGhU: "<!DOCTYPE html>
<html class="no-js seed-csp4" lang="en">
<head>
<meta charset="utf-8">
<title></title>

<meta name="vie"

It appears to be looking for the auth token in the wrong directory?

The .well-known and acme-challenge directories are being generated in httpdocs and I can view the token if I manually put it’s location in the address bar.

Any ideas what the cause is? I successfully generated a certificate for another subscription on this server 2 days ago. I have tried disabling the .htaccess and any apache/nginx directives (there are none).


#2

Have a look to the URL which the ACME server tries to access.
Do you have a redirect from myhalto.com to halto.co.uk?


#3

Ah wood for the trees moment - hadn’t even seen that it was querying the alias - fixed by fixing the duff implementation of the SANs

Thank you


#4

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.