How-to: HTTPS for ALL your containers using reverse proxy and internal CA, no more published ports!

• lego

  55 7,290 8.9 Go

  Let's Encrypt/ACME client and library written in Go

  

If I was issuing my own certs signed by my own CA and copying them to each device (my openwrt router, my IPMI interface, etc) I think I would still get real certs with something like lego and copy those over instead.

• acme.sh

  280 36,617 8.9 Shell

  A pure Unix shell script implementing ACME client protocol

  

Even though acme.sh makes life much easier the whole system is not a walk in the park either. There definitely is a learning curve but once you have got set up everything up and automated renewals it's smooth sailing. That's how I see it.

• InfluxDB

  www.influxdata.com featured

  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.

  

• docker-swag

  295 2,539 9.1 Dockerfile

  Nginx webserver and reverse proxy with php support and a built-in Certbot (Let's Encrypt) client. It also contains fail2ban for intrusion prevention.

  

spend the $10/year to buy a domain and create a wildcard cert for all your services to publish behind swag: https://docs.linuxserver.io/general/swag

• labca

  4 290 8.5 Go

  A private Certificate Authority for internal (lab) use, based on the open source ACME Automated Certificate Management Environment implementation from Let's Encrypt (tm).

Suggest a related project