check_ssl_cert
https-portal
| check_ssl_cert | https-portal | |
|---|---|---|
| 4 | 9 | |
| 355 | 4,375 | |
| - | - | |
| 8.8 | 5.6 | |
| 18 days ago | 4 months ago | |
| Shell | Ruby | |
| GNU General Public License v3.0 only | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
check_ssl_cert
-
Encrypted traffic interception on Hetzner and Linode targeting Jabber service
https://github.com/matteocorti/check_ssl_cert
- Find Expiring SSL Certs using curl, Go and Perl
-
Never have an SSL certificate expire again
Wouldn't it be easier to just put it in your existing monitoring system?
* https://github.com/matteocorti/check_ssl_cert
* https://exchange.nagios.org/directory/Plugins/Network-Protoc...
- SSL error detection/expire bash script
https-portal
- Vaultwarden + SSL
-
Which reverse proxy are you using?
HTTPS-PORTAL has everything I need.
- Looking for recommendations for a reverse proxy
-
Never have an SSL certificate expire again
If you use LetsEncrypt and Docker, I can recommend HTTPS Portal to automatically manage your SSL certs: https://github.com/SteveLTN/https-portal
I use it for my blog and have never had any issues with certs being renewed well in advance of their expiration date.
-
Harbormaster: The anti-Kubernetes for your personal server
This looks awesome!
What I couldn't immediately see from skimming the repo is:
How hard would it be to use a docker-based automatic https proxy such as this [1] with all projects?
I've had a handfull of docker-based services running for many years and love the convenience. What I'm doing now is simply wrap the images in a bash script that stops the containers, snapshots the ZFS volume, pulls newer versions and re-launches everything. That's then run via cron once a day. Zero issues across at least five years.
[1] https://github.com/SteveLTN/https-portal
-
What is best practice for serving multiple docker container on port 443?
HTTPS-PORTAL [DockerHub, GitHub]
-
Only allow communication within docker-compose network?
You're welcome! I might sound "advertise-y" here, but perhaps you can look into Nginx Proxy Manager or Https-Portal as well since they do involve Nginx.
-
Docker angular frontend with express backend in same file
For the nginx reverse proxy I use this https proxy. It sits on top of all my containers, enables and renews https automatically with let’s encrypt and has very good defaults.
-
Containers and Local SSL Certificates: Can I share 1 Local Certificate Across Multiple Containers?
You can use https://github.com/SteveLTN/https-portal. You’ll be up and running in 5 minutes.
What are some alternatives?
Revssl - A script that automates generation of OpenSSL reverse shells
swarmpit - Lightweight mobile-friendly Docker Swarm management UI
dehydrated - letsencrypt/acme client implemented as a shell-script – just add water
Nginx Proxy Manager - Docker container for managing Nginx proxy hosts with a simple, powerful interface
certspotter - Certificate Transparency Log Monitor
docker-swag - Nginx webserver and reverse proxy with php support and a built-in Certbot (Let's Encrypt) client. It also contains fail2ban for intrusion prevention.
nginx-proxy-automation - Automated docker nginx proxy integrated with letsencrypt.
caddy-docker-proxy - Caddy as a reverse proxy for Docker
docker-compose-letsencrypt-nginx-proxy-companion - Automated docker nginx proxy integrated with letsencrypt. [Moved to: https://github.com/evertramos/nginx-proxy-automation]
caddy-docker - Source for the official Caddy v2 Docker Image
NPushOver - Full fledged, async, .Net Pushover client
Portainer - Making Docker and Kubernetes management easy.