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

fix: replace staging certificate on production switch

Browse Source
This commit is contained in:
bisco
2026-06-25 12:39:43 +02:00
parent 5bdf628a2e
commit a835900418
4 changed files with 42 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/deployment.md
+4 -2
View File
@@ -44,8 +44,10 @@ 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` 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.
production CA only after validating DNS and firewall behavior. When
`LETSENCRYPT_STAGING` changes from `1` to `0`, recreate the Certbot container; it
removes an existing staging certificate for the configured domain before requesting the
production certificate.
## State and rollback