acme-companion
docker-gen
Our great sponsors
acme-companion | docker-gen | |
---|---|---|
32 | 7 | |
7,229 | 4,355 | |
0.9% | 0.7% | |
7.6 | 8.4 | |
about 1 month ago | 9 days ago | |
Shell | Go | |
MIT License | 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.
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).
-
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
-
Trying to figure out how to update our SSL certificates for a couple of docker webapps using nginx
If you use Docker anyway, have a look at nginx-proxy and it's acme companion. When running on the same host, it will automatically find other containers via docker.sock and then route and create Let's Encrypt certificates for the (sub-)domain you add via env.
-
Help for Iran: How to host the signal-tls-proxy for iran behind a nginx
For the signal proxy, they are using nginx and letsencrypt already and the ports 80 and 443. My current setup already involves an nginx proxy as well as a certbot, so how can I host this signal proxy in my infrastructure?
docker-gen
-
Going to reinstall.. need ideas.
I've not got around to it, but I've always fancied creating a nice landing page that automatically updates as services come up/down, using the system jwilder created to make nginx-proxy, docker-gen. Could be a fun little project, anyway!
-
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
-
Easiest solution for local deployment?
Then to make deployment super easy we're using nginx-proxy which uses docker-gen (and the acme-companion for automatic SSL cert generation) to automatically re-configure an nginx reverse proxy to point to your containers.
-
Need help with a flexible configuration for Node and Nginx
I've now got a setup using docker where the reverse proxy configuration is within the container's configuration (using nginx-proxy, which uses docker-gen). That way I just set the host, path, etc. in my container config, deploy, and the nginx servers are re-configured accordingly. No need to worry about ports and IPs then either.
-
How do you manage and maintain the order of your container ports? It's a bit of a mess on my personal server
I use an automated nginx reverse proxy. What this does is setup an nginx reverse proxy which uses docker-gen (follow the advice of setting it up separately). docker-gen listens for docker events such as a container being run, inspects that container for the details it needs (port, host, etc.) then configures the nginx accordingly.
What are some alternatives?
docker-compose-letsencrypt-nginx-proxy-companion - Automated docker nginx proxy integrated with letsencrypt. [Moved to: https://github.com/evertramos/nginx-proxy-automation]
nginx-proxy - Automated nginx proxy for Docker containers using docker-gen
Docker Compose - Define and run multi-container applications with Docker
Nginx Proxy Manager - Docker container for managing Nginx proxy hosts with a simple, powerful interface
docker-letsencrypt-nginx-proxy-companion - LetsEncrypt companion container for nginx-proxy [Moved to: https://github.com/nginx-proxy/docker-letsencrypt-nginx-proxy-companion]
nginx-proxy-automation - Automated docker nginx proxy integrated with letsencrypt.
docker-letsencrypt-nginx-proxy-companion - Automated ACME SSL certificate generation for nginx-proxy [Moved to: https://github.com/nginx-proxy/acme-companion]
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.
caddy-docker-proxy - Caddy as a reverse proxy for Docker
nginxconfig.io - ⚙️ NGINX config generator on steroids 💉
Matrix-Docker-install - Dockerising a full Matrix server with Element (Riot) messaging, coTURN NAT traversal and Traefik(v2.2 / v2.3) proxy on RancherOS and Digital Ocean.
vaultwarden - Unofficial Bitwarden compatible server written in Rust, formerly known as bitwarden_rs