Our great sponsors
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
OP, this is a handy tutorial, but DNS validation would save you from having to mess with forwarding LetsEncrypt's HTTP validation through your proxy. If you're hosting your domain's authoritative DNS on a provider that supports DNS API access, switching certbot to DNS validation (or using a certbot alternative like acme.sh, which has excellent DNS validation support) will simplify your proxy configuration and also potentially shrink your local attack surface by removing a listening endpoint.
It's a slightly modified version of this one https://github.com/alexandrevicenzi/soho