This is a debian-based image which runs an apache and get's it SSL-certificates automatically from Let's Encrypt.
There are some things you have to care about in your apache-config if you want to use it with certbot:
- for every domain given in
DOMAINS
there must be a apache-vhost which uses this domain asServerName
orServerAlias
. Else certbot won't get a certificate for this domain. - this image contains a simple apache webserver. Therefore you can configure your vhosts like you ever did.
For an easy test-startup you just have to:
$ docker run -d --name apache-ssl birgerk/apache-letsencrypt
Now you have locally an apache running, which get's it SSL-certificates from Let's Encrypt.
The image will get letsencrypt-certificates on first boot. A cron-job renews the existing certificates automatically, so you don't have to care about it.
If you want to expand your certificate and you can remove the existing docker-container and start new one with the updated DOMAINS
-list. If you don't want to recreate the container you can execute the following commands:
$ UPDATED_DOMAINS="example.org,more.example.org"
$ docker exec -it apache-ssl /run_letsencrypt.sh --domains $UPDATED_DOMAINS
It's possible to configure the docker-container by setting the following environment-variables at container-startup:
DOMAINS
, configures which for which domains a SSL-certificate shall be requested from Let's Encrypt, default is""
. Must be given as comma-seperated list, f.e.:"example.com,my-internet.org,more.example.com"
.WEBMASTER_MAIL
, Let's Encrypt needs a mail-address from the webmaster of the requested domain. You have to set it, otherwise Let's Encrypt won't give the certificates. Default is""
. Must be given as simple mail-address, f.e.:"[email protected]"
.STAGING
, if set with a not-null string use Let's Encrypt Staging environment to avoid rate limits during development.
After letsencrypt did authenticate your domains and you got your certificates, you'll find your certificates under /etc/letsencrypt/live/<example.com>/
.
So your https-virtualhost should like:
<VirtualHost *:443>
ServerName example.com
ServerAdmin [email protected]
DocumentRoot /var/www/html
SSLCertificateFile /etc/letsencrypt/live/${VIRTUAL_HOST}/fullchain.pem
SSLCertificateKeyFile /etc/letsencrypt/live/${VIRTUAL_HOST}/privkey.pem
Include /etc/letsencrypt/options-ssl-apache.conf
</VirtualHost>