bisco/azionelab-v2
1
0
Fork 0
generated from bisco/codex-bootstrap
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: keep proxy healthy during tls pending

Browse Source
This commit is contained in:
bisco
2026-06-25 12:00:33 +02:00
parent 0a590989bb
commit 0302634094
4 changed files with 39 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/deployment.md
+4 -3
View File
@@ -42,9 +42,10 @@ is safe only when firewall/network policy makes the load balancer the sole NGINX
caller and it overwrites `X-Forwarded-*` headers.
For direct TLS, public DNS and inbound ports 80/443 must reach NGINX. Start with
`LETSENCRYPT_STAGING=1`; application HTTP returns 503 until a certificate exists, then
redirects to HTTPS. Switch to the production CA only after validating DNS and firewall
behavior, removing only the staging certificate volume when necessary.
`LETSENCRYPT_STAGING=1` and set `WP_URL` to the final HTTPS URL. Application HTTP
returns 503 until a certificate exists, then redirects to HTTPS. Switch to the
production CA only after validating DNS and firewall behavior, removing only the
staging certificate directory when necessary.
## State and rollback