mirror of
https://github.com/nginx-proxy/nginx-proxy
synced 2025-07-11 22:44:22 +02:00
4c8f22ebcc
Currently any ACME challenge for unknown virtual host returns 503. This is inconvenient because if the user does not use wildcard certificates, then the user must match the configuration of certificate renewal script to what virtual hosts are enabled at the time. This must be done automatically, because due to short certificate lifetime the renewal script runs automatically. Additionally, enabling a previously disabled virtual host forces certificate renewal. Accordingly, it's worthwhile supporting unknown virtual hosts for the purposes of passing ACME challenges. This is done by introducing a global ACME_HTTP_CHALLENGE_ACCEPT_UNKNOWN_HOST variable to control this. |
||
|---|---|---|
| .. | ||
| acme_root/.well-known/acme-challenge | ||
| certs | ||
| compose.base.override.yml | ||
| test_acme-http-challenge-location-accept-unknown-host.py | ||
| test_acme-http-challenge-location-accept-unknown-host.yml | ||
| test_acme-http-challenge-location-disabled.py | ||
| test_acme-http-challenge-location-disabled.yml | ||
| test_acme-http-challenge-location-enabled-is-default.py | ||
| test_acme-http-challenge-location-enabled-is-default.yml | ||
| test_acme-http-challenge-location-legacy.py | ||
| test_acme-http-challenge-location-legacy.yml | ||