• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:
    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Issue Lets Encrypt with custom Domain (Proxy Pass)

A

Attackwave

New Pleskian
Hi,

when I use my domain vserver.mydomain.de and ProxyPass to connect to my control panel,
then the following errors occurre.

Domain settings for https:
ProxyPass "/" "http://127.0.0.1:8880/"
ProxyPassReverse "/" "http://127.0.0.1:8880/"


Lets Encrypt error for mydomain.de:
Code: 
Internal error ;-P
<html>
<head><title>502 Bad Gateway</title></head>
<body bgcolor="white">
<center><h1>502 Bad Gateway</h1></center>
<hr><center>nginx</center>
</body>
</html>
<!-- a padding to disable MSIE and Chrome friendly error page -->
<!-- a padding to disable MSIE and Chrome friendly error page -->
<!-- a padding to disable MSIE and Chrome friendly error page -->
<!-- a padding to disable MSIE and Chrome friendly error page -->
<!-- a padding to disable MSIE and Chrome friendly error page -->
<!-- a padding to disable MSIE and Chrome friendly error page -->

Lets Encrypt error for vserver.mydomain.de:
Code: 
Fehler: Could not issue a Let's Encrypt SSL/TLS certificate for vserver.mydomain.de.

The authorization token is not available at https://vserver.mydomain.de/.well-known/acme-challenge/s2nb7YHjqbUuP23pUfOFodhwltkX6QVBDkm_PZOZVL8.
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/HoLOrG7-fXlhaB-V9Mz_32gkUoNLjhnRuIJzM5TkqB8.
Details:
Type: urn:acme:error:unauthorized
Status: 403
Detail: Invalid response from http://vserver.mydomain.de/.well-known/acme-challenge/s2nb7YHjqbUuP23pUfOFodhwltkX6QVBDkm_PZOZVL8: "<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta http-equiv="x-ua-compatible" content="ie=edge">
"

Lets Encrypt works with https://vserver.mydomain.de:8443.

Is there a chance to make it working with ProxyPass?
 
Last edited:
i have the same error its because lets encrypt couldn't connect to ./well-known directory when proxypass is active?
i tried to add
Code: 
# Statically serve all files in .well-known, which is the location where letsencrypt stores the proof file
location /.well-known/ {
    root /var/www/vhosts/domain.com/httpdocs/;
}

without any success i'm looking forward
 
That config seems to work (at least on the first view! ;-)) in my case...

123.jpg



Maybe "ProxyPreserveHost On" is NOT mandatory...?? (Thank you for your feedback...:))

-> I've got that idea from HERE: Error installing Certbot with Apache reverse proxy to NodeJS
 
You must log in or register to reply here.

Similar threads

L
Issue ( authorization token is unavailable ) Could not issue/renew Let`s Encrypt certificates
Replies
7
Views
532
Leta
L
M
Resolved Lets Encrypt not issuing certs for subdomains
Replies
2
Views
364
mendip_discovery
M
H
Resolved Problem with install Let's Encrypt SSL/TLS certificate
Replies
6
Views
417
HungLuu
H
D
Issue Lets Encrypt Not Successful over port 80
Replies
8
Views
2K
Daiv
D
M
Issue Wordpress MU alias domains with Let's Encrypt - hit the error: Order cannot contain more than 100 DNS names
Replies
1
Views
175
Kaspar
K
Back
Top