• 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
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

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

D
Issue Lets Encrypt Not Successful over port 80
Replies
8
Views
493
Daiv
D
Nextgen-Networks
Issue Lets Encrypt - error in certificate renew process
2
Replies
21
Views
3K
Peter Debik
P
hansitheking
Resolved Let's Encrypt: Timeout during connect (likely firewall problem)
Replies
4
Views
6K
trialotto
T
T
Issue Unable to install Let's Encrypt certificate for temporary domain
Replies
5
Views
2K
Peter Debik
P
P
Question Renew Let's encrypt cert failed after added inbound rule for aws ec2
Replies
1
Views
686
Peter Debik
P
Back
Top