Issue Lets Encrypt with custom Domain (Proxy Pass)

Attackwave · Dec 28, 2017

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?

dj ramc · Aug 27, 2018

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

jmar83 · May 10, 2022

Same question here...

jmar83 · May 10, 2022

That config seems to work (at least on the first view! ;-)) in my case...

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

Issue Lets Encrypt with custom Domain (Proxy Pass)

Attackwave

New Pleskian

dj ramc

Basic Pleskian

jmar83

Regular Pleskian

jmar83

Regular Pleskian

Similar threads