search

libresh / compose-haproxy

HAproxy for libre.sh v1
GNU Affero General Public License v3.0
33 stars 10 forks source link

LE cert requires haproxy restart when new domain is added #7

Closed edrex closed 6 years ago

edrex commented 7 years ago

For example:

core@libre /$ sudo libre provision -a github.com/indiehosters/nextcloud -u nextcloud.pdxhub.org -s

At this point the server has a self-signed cert

subject=/C=FR/ST=Some-State/L=flers/O=Internet Widgits Pty Ltd/OU=Timothee/CN=Timothee/emailAddress=timothee@unteem.org
issuer=/C=FR/ST=Some-State/L=flers/O=Internet Widgits Pty Ltd/OU=Timothee/CN=Timothee/emailAddress=timothee@unteem.org

It appears that the let's encrypt process succeeded, so I guess haproxy isn't picking up the cert.

Restarting haproxy picks up the cert.

core@libre / $ cd /system/haproxy && sudo libre restart

Known issue?

edrex commented 7 years ago

Realizing this may be "by design" and I should just be running libre reload on haproxy after adding a domain. Is this expected behavior?

edrex commented 7 years ago

https://cbonte.github.io/haproxy-dconv/1.7/management.html#4

pierreozoux commented 7 years ago

Strange, this shouldn't happen because of these lines: https://github.com/indiehosters/docker-haproxy/blob/master/docker-entrypoint.sh#L10-L13

Is it the first cert or the following?

pierreozoux commented 6 years ago

I'll close this for now as it is old, but feel free to reopen if needed.