Our great sponsors
-
greenlock-express.js
Free SSL and Automatic HTTPS (ACME / Let's Encrypt v2 client) for node.js with Express, Connect, and other middleware systems
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
I'd look into Caddy or Traefik. Both are reverse proxies. Even though you mentioned you want to avoid them I strongly recommend you reconsider.
No reverse proxy, proper integration: Add something like the greenlock-express npm module to your Node app. It will handle the SSL integration for you – create the certs, add them to your server config and renew them when necessary.
Reverse proxy, docker-style: If the services you run (in your case a Node app) live in a docker container, you can also use a Reverse Proxy that is built for docker or has docker integration. This can be Traefik, for nginx you can use the wildly popular nginx-proxy image or for Caddy there's caddy-docker-proxy.
Reverse proxy, docker-style: If the services you run (in your case a Node app) live in a docker container, you can also use a Reverse Proxy that is built for docker or has docker integration. This can be Traefik, for nginx you can use the wildly popular nginx-proxy image or for Caddy there's caddy-docker-proxy.
Related posts
- Let's Encrypt now supports ACME-CAA: closing the DV loophole
- How to securely reverse-proxy ASP.NET Core web apps
- Caddy is the first and only web server to use HTTPS automatically and by default
- nginx alternatives
- acme.sh runs arbitrary commands from a remote server · Issue #4659 · acmesh-official/acme.sh