Aral Balkan

Mastodon icon RSS feed icon P2P network icon

HTTPS Server: now with seamless Let’s Encrypt support

Note: HTTP Server is now Indie Web Server.
Screenshot of my terminal showing ~/ar.al: https-server live --global aral@ind.ie 📜 [nodecert] Local development TLS certificate exists. 🌍 [https-server] Using globally-trusted certificates. 👉 [https-server] (Globally-trusted TLS) HTTP → HTTPS redirection active. 🎉 Serving live on https://aral.hypha.dev

You can now also use globally-trusted Let’s Encrypt TLS certificates.

Yesterday, I introduced HTTPS Server as a development server. What a difference a day makes! Today, with seamless Let’s Encrypt support via the excellent Greenlock.js module1, HTTPS Server is ready for use as a secure Small Tech personal web server for development and deployment. It is a human-scale tool for creating and hosting single-tenant/personal web applications using Node.js.

With HTTPS Server you can:

  1. Develop using seamlessly-provisioned locally-trusted certificates.

  2. Develop/stage using seamlessly-provisioned globally-trusted certificates via a secure tunnel (e.g., with a pro or business plan at ngrok with custom domains).

  3. Deploy using seamlessly-provisioned and renewed globally-trusted certificates (e.g., via pm2).

I plan to expand on each of the above use cases in future posts.

In the meanwhile, we have one more small piece of the puzzle in our fledgling effort to build a bridge from surveillance capitalism to peerocracy.


  1. Although, what’s up with telemetry and tracking in a Node module? These “features” are turned off in HTTPS Server. [return]