Setup Multisite Configuration with Let's Encrypt and no Reverse Proxy

Community wiki Sysadmins
,
21

You likely need to change just the part having to do with the certificates.

Oh. Wait.

It sounds like recent changes to the way that the NGINX configuration is managed that this bit is now in a different file:

   # do not redirect all hosts back to the main domain name
    - replace:
        filename: "/etc/nginx/conf.d/discourse.conf"
        from: /if \(\$http_host[^\}]*\}/m
        to: ""

Yes. Here’s the new place:

I think that changing that filename to /etc/nginx/conf.d/outlets/server/20-https.conf will solve the redirect problem. You’ll also need to make the changes about how the certificate is requested, though if it’s working, I guess you might not need to change it.

1 Like
22

Thanks @pfaffman! Can’t get it working so far. Though I probably just ran into the Certificate limit as well, re-building with changes to the config file…

Gonna study the proxy stuff now :sob:

23

If you did, you can just add another subdomain to the list (and the DNS record) and you’ll start a new rate limit.

1 Like
24

Maybe I was just duped again by the browser cache :face_with_spiral_eyes: In any case, I switched that server to the default multisite setup, with caddy as reverse proxy. In the end it’s also straightforward and one thing I actually like is that the certificates are for each domain then (and not all domains shared on one certificate).

Have another server to update, I’ll try the adjustments another time with that one to see what’s necessary..

Thanks again!

1 Like