Enable HTTPS access
This manual supports docker-compose
only deployments.
- Create a
certs
directory underconfig/ssl-proxy
, e.g. for Unix/Linux-based OS:
mkdir config/ssl-proxy/certs
- Place your certificate and key under the newly-created directory, e.g.:
config/ssl-proxy/certs
├── mydomain.key
└── mydomain.pem
- Set your domain name and filenames of your key and certificates in
config/ssl-proxy/conf.d-ssl/nginx.conf
underserver
directive, e.g.:
...
server {
...
ssl_certificate /etc/nginx/certs/<your_certificate_filename>;
ssl_certificate_key /etc/nginx/certs/<your_key_filename>;
...
}
...
With the filenames from step 2 config will look like this:
server {
...
ssl_certificate /etc/nginx/certs/mydomain.pem; # set your certificate filename here
ssl_certificate_key /etc/nginx/certs/mydomain.key; # set your key filename here
...
}
...
- Enable
ssl-proxy
by editing yourcustom.env
configuration and adding thessl-proxy
mod:
COMPOSE_FILE=docker-compose.yml:mods/ssl-proxy.yml
-
Run
make up
in the project's root to update yourdocker-compose
deployment. -
Access Databand stack UI via
ssl-proxy
container and HTTPS.
Updated 9 months ago