https://github.com/sashee/letsencrypt-proxy-docker
SSL termination with Let's Encrypt inside a Docker container
https://github.com/sashee/letsencrypt-proxy-docker
Last synced: 23 days ago
JSON representation
SSL termination with Let's Encrypt inside a Docker container
- Host: GitHub
- URL: https://github.com/sashee/letsencrypt-proxy-docker
- Owner: sashee
- Created: 2016-04-19T07:55:19.000Z (about 9 years ago)
- Default Branch: master
- Last Pushed: 2016-05-13T12:10:48.000Z (almost 9 years ago)
- Last Synced: 2025-03-24T08:36:30.591Z (about 1 month ago)
- Language: ApacheConf
- Homepage:
- Size: 5.86 KB
- Stars: 37
- Watchers: 3
- Forks: 3
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
- awesome-starred - sashee/letsencrypt-proxy-docker - SSL termination with Let's Encrypt inside a Docker container (others)
README
# Dockerized Let's Encrypt Proxy
This is fully automated dockerized proxy that let's you add HTTPS termination with minimal config.
It uses Let's Encrypt for valid certificates and automation. It handles certification issuance as well as renewal.
It has minimal downtime every 2 months, when the Apache proxy is restarted to use the new certificate.
Docker hub link: [https://hub.docker.com/r/sashee/letsencrypt-proxy-docker/](https://hub.docker.com/r/sashee/letsencrypt-proxy-docker/)
## Usage
The image needs just a few configurations:
* Expose ports 80 and 443
* Add a network bridge to your service and call it _proxied_
* Set the hostname for the certificate
* Set the port your app is using
* Test it and then set production mode
An example config:
```
version: '2'
services:
proxy:
image: sashee/letsencrypt-proxy-docker
ports:
- "80:80"
- "443:443"
depends_on:
- angular
networks:
- proxy
environment:
# Set your host
#- HOST=
- PORT=80
# Set your email
#- EMAIL=
# Turn on production mode
#- MODE=PRODUCTION
links:
- angular:proxied
angular:
image: thanhson1085/angular-admin-seed
networks:
- proxy
networks:
proxy:
```
Change the `angular` part to your app, and update the `link` above.
## Production mode
Let's Encrypt limits the number of certificates issued for a given host every 7 days.
You should test your setup without setting the MODE, and if everything is ok, only then set it to PRODUCTION.
If you test with live certificates, then you can easily find yourself limited and then you have to wait a week to continue.
## Domain name
If you don't have a domain name, you can use [nip.io](http://nip.io) to test it out.
Please note that AWS domains are blacklisted and will not work.