Crypt-LE
acme-companion
Crypt-LE | acme-companion | |
---|---|---|
1 | 32 | |
348 | 7,272 | |
- | 0.5% | |
2.7 | 7.4 | |
about 1 year ago | 5 days ago | |
Perl | Shell | |
Artistic License 2.0 | 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.
Crypt-LE
-
Help me understand Wildcard Certs
Normally you can use the same .csr forever if the domain is the same - I normally use LE64 to generate let's encrypt certificates (which can do wildcards also), but if you're purchasing a certificate rather than generating a free one, and you want to generate it right in IIS, you can follow a guide like this. If you generate a wildcard cert like *.domain.com, you can use it for all your subdomains but NOT generally for domain.com itself (depending on your application). You can use the same certificate for all applications provided they support whatever format the certificate is in; mostly these will be in PEM-style anymore so you have the whole cert chain in one file.
acme-companion
-
Wireguard (docker-compose) has stopped being able to connect to the internet.
My hunch is that because I decided to include the acme-companion image in this nginx setup, that maybe it has something to do with the SSL certs? The only other thing I could think of is that I had to combine the networks in order for nginx-proxy and Sonarr both to be able to see my transmission instance via:
-
Add https to docker app
Probably want acme with nginx https://github.com/nginx-proxy/acme-companion
-
Beginner questions about deploying node.js app on Beanstalk
setting up letsencrypt with nginx-proxy and acme-companion
-
Further investigating 403 – access forbidden by rule
I'm experiencing a weird situation, and am not sure how to go about finding a solution. I am running the nginx-proxy container (https://github.com/nginx-proxy/nginx-proxy) together with the acme-companion container (https://github.com/nginx-proxy/acme-companion) to provide https connections to all my different applications under different subdomains on the same host (currently, for testing purposes: only two other nginx containers with a plain html page).
-
What is the correct way to have my webapp in one container and the webserver in another?
We use the nginx-proxy docker image with its acme-companion to have an auto configuring SSL reverse proxy, so it's really easy to deploy images (we do it based on a merge PR into protected release branches).
-
adding an SSL cert to a docker container
Use a reverse proxy to handle TLS/SSL encryption. I find nginx-proxy with companion easy to use, just follow steps 1, 2, 3.
-
502 Bad Gateway: Nginx Reverse Proxy + Docker + Let's Encrypt + Wordpress
Where I'm running into issues is with the two stacks I have deployed - one is a wordpress stack which uses the wordpress image along with a db image (going by the docs here), and the other is the nginx-proxy and acme-companion (going by the docs here).
-
dockerfile for httpd
Just use nginx-proxy and the LetsEncrypt companion as reverse proxy to handle TLS/SSL in front of your web server.
-
nginx-proxy-manager abandoned?
You can simply use this proxy container which automatically generates nginx config based on envs set in your containers. There is also a companion container which takes care of your certs. https://github.com/nginx-proxy/nginx-proxy https://github.com/nginx-proxy/acme-companion
-
Tools for automation and daily tasks
https://github.com/nginx-proxy/acme-companion https://github.com/nginx-proxy/docker-gen https://github.com/projectdiscovery/dnsx https://github.com/projectdiscovery/httpx https://github.com/projectdiscovery/mapcidr https://github.com/debauchee/barrier https://github.com/stedolan/jq https://github.com/ddosify/ddosify https://github.com/kubernetes-sigs/kind https://github.com/mailcow/mailcow-dockerized https://github.com/motiv-labs/janus
What are some alternatives?
caddy-cloudflare - Caddy with integrated support for Cloudflare DNS-01 ACME verification challenges.
docker-compose-letsencrypt-nginx-proxy-companion - Automated docker nginx proxy integrated with letsencrypt. [Moved to: https://github.com/evertramos/nginx-proxy-automation]
Netdot - Network Documentation Tool
nginx-proxy - Automated nginx proxy for Docker containers using docker-gen
mod_md - Let's Encrypt (ACME) in Apache httpd
Docker Compose - Define and run multi-container applications with Docker
HandyAcme - A TypeScript Client implements ACME (RFC 8555)
Nginx Proxy Manager - Docker container for managing Nginx proxy hosts with a simple, powerful interface
sslmgr - A layer of abstraction the around acme/autocert certificate manager (Golang)
docker-letsencrypt-nginx-proxy-companion - LetsEncrypt companion container for nginx-proxy [Moved to: https://github.com/nginx-proxy/docker-letsencrypt-nginx-proxy-companion]
lego - Let's Encrypt/ACME client and library written in Go
nginx-proxy-automation - Automated docker nginx proxy integrated with letsencrypt.