Public | Automated Build

Last pushed: 3 years ago
Short Description
Short description is empty for this repo.
Full Description

This container is ment as a web-front when you dont have more than 1 ip-address available and can route web domains to spesific ips and from there to containers.
It will based on mounted configuration forward requests to another port/ip:port. From there, you can use another proxy to forward it on to the web-server container.


docker run -i -t -p 80:80 -p 443:443 -v $PWD/domains:/domains xeor/nginx-proxy-front


Put 1 folder per domain (vhost), inside the ./domains/ folder in the format domain_remote[:port], with one server.pem (or .crt), and server.key in.
The container watches this folder, so if you add a domain, it will be included without you having to restart the container.

  • If want this proxy for localhost, you will need to use --net host when starting the container..
  • Let this container take care of ssl, so the ports you proxy to, should be NON ssl/tls...
  • See the file for what it supports :)


  • example with cheapssl
  • self-signed (testing): openssl req -x509 -newkey rsa:2048 -keyout server.key -out server.pem -days 3650 -nodes
  • letsencrypt
    • Letsencrypt is installed, so all you need to do is make sure that /etc/letsencrypt is mounted and persitent and;
    • Go into the container, run something like /letsencrypt/letsencrypt-auto certonly --webroot -w /domains/your.domain_127.0.1.1/acme -d your.domain
    • Replace the cert files in /domains/your.domain_127.0.1.1/. with symlinks to matching certs in /etc/letsencrypt/live/... fullchain.pem to server.pem and privkey.pem to server.key


If you want to generate a strong dhparam, place it in /domains/dhparams.pem, like openssl dhparam -out /domains/dhparams.pem 2048 and we will use it..


  • Replace the nginx config template with a python template instead of ugly sed -e hacks
Docker Pull Command
Source Repository