docker-compose-letsencrypt-nginx-proxy-companion
DISCONTINUED
acme-companion
Our great sponsors
docker-compose-letsencrypt-nginx-proxy-companion | acme-companion | |
---|---|---|
1 | 32 | |
2,106 | 7,229 | |
- | 0.9% | |
8.2 | 7.6 | |
almost 3 years ago | about 1 month ago | |
Shell | Shell | |
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.
docker-compose-letsencrypt-nginx-proxy-companion
-
How do I remove the "on Plex" crap from my users home screen? The only thing its ever done is confuse my users. I thought Plex just released a new feature to allow you to manage users Home Screen.
git clone https://github.com/evertramos/docker-compose-letsencrypt-nginx-proxy-companion.git
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?
What are some alternatives?
ABJC-tvOS - ABJC is A Better Jellyfin Client
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]
zammad-docker-compose - Zammad Docker images for docker-compose
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.
goaccess-for-nginxproxymanager - GoAccess Docker Image for Nginx Proxy Manager and more...
docker-nginx-certbot - Automatically create and renew website certificates for free using the Let's Encrypt certificate authority.
caddy-docker-proxy - Caddy as a reverse proxy for Docker