Zane Matthew zanematthew

Running NGINX and CertBot Containers on the Same Host

The Problem

A lot of people run into the problem of running Let's Encrypt's CertBot Tool and an NGINX on the same container host. A big part of this has to do with CertBot needing either port 80 or 443 open for the tool to work as intended. This tends to conflict with NGINX as most people usually use port 80 (HTTP) or 443 (HTTPS) for their reverse proxy. Section 1 outlines how to configure NGINX to get this to work, and Section 2 is the Docker command to run CertBot.

1. NGINX Configuration

I use Docker Compose (docker-compose) for my NGINX server. My docker-compose.yml file looks something like this:

	[alias]
	# list aliases
	aliases = !git config --get-regexp 'alias.*' \| colrm 1 6 \| sed 's/[ ]/ = /'

	# list branches
	br = branch

	# show current branch - tried to use to get branch name for other aliases
	bn = !git rev-parse --abbrev-ref HEAD

	<?php
	/*
	Usage:
	$frag = new CWS_Fragment_Cache( 'unique-key', 3600 ); // Second param is TTL
	if ( !$frag->output() ) { // NOTE, testing for a return of false
	functions_that_do_stuff_live();
	these_should_echo();
	// IMPORTANT
	$frag->store();
	// YOU CANNOT FORGET THIS. If you do, the site will break.

	###############################################################################
	#
	# Apache virtual host 'no reboot needed' template.
	#
	# This apache virtualhost configuration allows a user to create development
	# sites on the fly. This will not work out of the box however, you will need
	# to replace the {variables} in this conf with values explained below. This
	# can be done with a script, or a simple find and replace in your favorite
	# editor.
	#

	#!/usr/bin/env bash

	# args
	MSG=${1-'deploy from git'}
	BRANCH=${2-'trunk'}

	# paths
	SRC_DIR=$(git rev-parse --show-toplevel)
	DIR_NAME=$(basename $SRC_DIR)
	DEST_DIR=~/svn/$DIR_NAME/$BRANCH

	[user]
	name = Ondrej Certik
	email = ondrej@certik.cz

	[color]
	ui = auto
	interactive = true

	[alias]
	ci = commit