Symptoms
The following error is shown in Plesk when attempting to renew a Let's Encrypt certificate:
The authorization token can not be found at http://example.com/.well-known/acme-challenge/29nXDraTqxzU4Bn8Mz5uCIAgokxqPruRYDbNzAbGK0A .
To fix the problem, make the token file available at this URL.
For more information, see the related Knowledge Base article.
details
Invalid response from https://acme-v02.api.letsencrypt.org/acme/authz/I7LAbA5g8AI7uHfy-G2IEWUKlEmxeLpCxSMorQcsv-g.
Details:
Type: urn: ietf: params: acme: error: unauthorized
Status: 403
Detail: Invalid response from http://example.com/.well-known/acme-challenge/29nXDraTqxzU4Bn8Mz5uCIAgokxqPruRYDbNzAbGK0A: "<! DOCTYPE html> n <! - [if lt IE 7]> <html class = "no-js lt-ie9 lt-ie8 lt-ie7 "> <! [endif] -> n <! - [if IE 7 ]> <html class = "no-js lt-ie"
The authorization token is not available at http://example.com/.well-known/acme-challenge/-atKzNLhilfuQkFtA6ZnjjW1rEMn6IRyrnkR_n65OD8.
To resolve the issue, make sure that the token file can be downloaded via the above URL.
See the related Knowledge Base article for details.
Details
Invalid response from https://acme-v02.api.letsencrypt.org/acme/authz-v3/12994896260.
Details:
Type: urn:ietf:params:acme:error:unauthorized
Status: 403
Detail: Invalid response from https://webmail.example.com/.well-known/acme-challenge/-atKzNLhilfuQkFtA6ZnjjW1rEMn6IRyrnkR_n65OD8 "<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">n<html><head>n<title>404 Not Found</title>n</head><body>n<h1>Not Found</h1>n<p"
Cause
The Nginx rewrite rules set in Domains > example.com > Apache & Nginx Settings > Additional nginx directives are not allowing Let's Encrypt to load the token.
Resolution
-
Back up (copy and paste) the Nginx rewrite rules from Domains > example.com > Apache & Nginx Settings > Additional nginx directives to a text document, remove it from the Additional nginx directives section and click OK.
-
Renew the Let’s Encrypt certificate in Domains > example.com > Let's Encrypt.
-
Return back the nginx rewrite rules to Domains > example.com > Apache & Nginx Settings > Additional nginx directives.