6bb568da7ee60ee76fcb6c4b382220f68777f235
haproxy-letsencrypt-docker.md
| ... | ... | @@ -181,7 +181,6 @@ backend domain1 |
| 181 | 181 | |
| 182 | 182 | backend domain2 |
| 183 | 183 | server domain2-1 container2:3000 resolvers docker check |
| 184 | - |
|
| 185 | 184 | ``` |
| 186 | 185 | |
| 187 | 186 | What's going on here then? |
| ... | ... | @@ -307,7 +306,8 @@ You're on your own with the container, but haproxy and certbot config we can do |
| 307 | 306 | Make sure the new domain's A record is pointing at haproxy's IP. |
| 308 | 307 | |
| 309 | 308 | Add the new domain to haproxy.conf: |
| 310 | -```... |
|
| 309 | +```text |
|
| 310 | +... |
|
| 311 | 311 | acl logs_hdr hdr(host) -i new.domain.com |
| 312 | 312 | ... |
| 313 | 313 | use_backend new-container if logs_hdr |
| ... | ... | @@ -323,7 +323,8 @@ Log into the letsencrypt container: |
| 323 | 323 | `docker exec -ti letsencrypt bash` |
| 324 | 324 | |
| 325 | 325 | Then run certbot with the new domain: |
| 326 | -```certbot --standalone --expand \ |
|
| 326 | +```bash |
|
| 327 | +certbot --standalone --expand \ |
|
| 327 | 328 | -d "domain1.example.com" \ |
| 328 | 329 | -d "domain2.example.com" \ |
| 329 | 330 | -d "new.domain.com" |