b1f02ae567e5043f28aab7c1d504c71dbbff492f
haproxy-letsencrypt-docker.md
| ... | ... | @@ -307,8 +307,7 @@ You're on your own with the container, but haproxy and certbot config we can do |
| 307 | 307 | Make sure the new domain's A record is pointing at haproxy's IP. |
| 308 | 308 | |
| 309 | 309 | Add the new domain to haproxy.conf: |
| 310 | -``` |
|
| 311 | -... |
|
| 310 | +```... |
|
| 312 | 311 | acl logs_hdr hdr(host) -i new.domain.com |
| 313 | 312 | ... |
| 314 | 313 | use_backend new-container if logs_hdr |
| ... | ... | @@ -324,8 +323,7 @@ Log into the letsencrypt container: |
| 324 | 323 | `docker exec -ti letsencrypt bash` |
| 325 | 324 | |
| 326 | 325 | Then run certbot with the new domain: |
| 327 | -``` |
|
| 328 | -certbot --standalone --expand \ |
|
| 326 | +```certbot --standalone --expand \ |
|
| 329 | 327 | -d "domain1.example.com" \ |
| 330 | 328 | -d "domain2.example.com" \ |
| 331 | 329 | -d "new.domain.com" |