Post

Automatic TLS cert provisioning are working via @letsencrypt.bsky.social using Go's `autocert` pkg (pkg.go.dev/golang.org/x...) so folks that sign up to use #Henhouse can have certificates for their own custom domains. #Henhouse #TLS #LetsEncrypt #ACME #GoLang #BuildInPublic

pkg.go.devautocert package - golang.org/x/crypto/acme/autocert - Go Packages

8/2/26, 8:20 pm1 repost4 likes

Kapil Agrawal

@netops2devops.net

8 Feb

Something I recently worked on. Works with any CA that supports external account binding github.com/esnet/acme-p...

github.comGitHub - esnet/acme-proxy: Solve ACME http-01 challenge without opening port 80 to the internet, obtain certs from an external certificate authority.Solve ACME http-01 challenge without opening port 80 to the internet, obtain certs from an external certificate authority. - esnet/acme-proxy

Blain Smith

@blainsmith.com

9 Feb

This is neat, thanks! I could see having Henhouse be configurable to use any ACME-compatible service, but defaulting to directly talking to Let's Encrypt as to keep the barrier of entry very low and not require running other services. Our goal is a single binary anyone can run.

Walt Skillset

@gremlin89.bsky.social

9 Feb

autocert is solid until you hit the rate limits. learned that one when spinning up too many test domains