🥳 Auto Encrypt: 5.1.1 released
• Fixed: Issue #26¹: Regression: AutoEncrypt HTTPS server does not start using new certificates upon renewal
https://codeberg.org/small-tech/auto-encrypt
Many thanks to zanecodes² for catching this rather fundamental bug.
Here’s a quick post-mortem:
Implementing support for IP Address certificates³ (see Web Numbers⁴) meant that we had to stop using `SNICallback`. This necessitated two changes:
1. Provisioning the TLS certificates before starting the server instead of on first hit.
2. Manually setting a new secure context for the running server so that newly-provisioned certificates are used on future connection attempts without having to restart the server.
While I had implemented the first, I hadn’t implemented the second.
This update fixes that.
(In case you’re wondering how I didn’t notice this before, given that Auto Encrypt is used in @small-tech/https⁵, which is used in Kitten⁶, which all our sites at Small Technology Foundation⁷ run on, the change coincided with the implementation of daily scheduled restarts on Kitten production servers⁸ to give their JSDB databases⁹ a chance to compact their data (e.g., actually delete deletes and prune stale updates from the append-only log.)
¹ https://codeberg.org/small-tech/auto-encrypt/issues/26
² https://codeberg.org/zanecodes
³ https://codeberg.org/small-tech/auto-encrypt/commit/116cb9cbf7d2059a578248796886c504963f740f#diff-a77b15c0d64cf6111e025645e562faf8ccabb9d7
⁴ https://ar.al/2025/06/25/web-numbers/
⁵ https://codeberg.org/small-tech/https
⁶ https://kitten.small-web.org
⁷ https://small-tech.org
⁸ https://codeberg.org/kitten/app/commit/a4a11839faf0091dd65040f2be5b85910f5a1849
⁹ https://codeberg.org/small-tech/jsdb
#AutoEncrypt #https #TLS #LetsEncrypt #IPAddresses #WebNumbers #SmallTech #SmallWeb