Traefik on contineroo.ch

Traefik 2.2 + Docker: Global entrypoint configuration

Wed, 25 Mar 2020 00:00:00 +0000

Introduction

With Traefik 2.2 it is now easier then ever to globally configure your entrypoints.

We will show you how you can define a global redirect to https and how to set a default certResolver. So you don’t have to set the https redirect in each docker-compose file.

Prerequisites

In order to follow along, you’ll need to read the advanced Traefik guide and the wildcard guide first!

Update Traefik Configuration

Change the entrypoints in the basic Traefik configuration file (/opt/containers/traefik/data/traefik.yml) as follows:

Traefik 2.0: Route external services through Traefik

Thu, 02 Jan 2020 00:00:00 +0000

Image Source

Introduction

In this tutorial we will show you how you can route non-Docker services through Traefik.

Let’s suppose you want to access your Pi-hole admin console (http://192.168.0.10:80/admin) by browsing to pihole.example.com.

Prerequisites

You have read our other articles:

and you use this Traefik configuration.

Make sure you configure in the providers section of your /opt/traefik/data/traefik.yml an external configuration file /config.yml.

Traefik 2.0: Paranoid about mounting /var/run/docker.sock?

Tue, 12 Nov 2019 00:00:00 +0000

Image Source

The Problem

If you have followed our previous guides, you mount the Docker Socket ( /var/run/docker.sock) into the Traefik container. If someone gets access into the Traefik container, they can gain full access to your host machine. This makes our paranoia level increase slightly…

The Solution

We found a nice little container (Socket-Proxy) which “filters” all requests to the Docker API. We can allow only get requests to the Docker API and restrict it to /containers/*.

Traefik 2.0: Wildcard Let's Encrypt Certificates

Tue, 12 Nov 2019 00:00:00 +0000

Image Source

Introduction

In this tutorial we will setup Traefik to obtain wildcard certificates from Let’s Encrypt. This requires DNS challenge to be setup. Usually Traefik obtains a certificate for every subdomain. We can simplify this process by telling Traefik to use a wildcard (*.example.com) certificate instead.

Prerequisites

Registered Domain
Authoritative DNS Servers from one of these providers (you may need to change your DNS servers of your domain to one of the provider in the list)

In this tutorial we will use Cloudflare as our DNS servers for our domain.

Using Pi-hole to route your services internally

Tue, 12 Nov 2019 00:00:00 +0000

Image Source

The Problem

If you have followed our previous guides, chances are that you have a domain, some DNS records pointing to your public IP, port forwarding enabled and a Docker server running some services.

Most likely your domain resolves to your public IP from you internal network as well. This causes a problem: All the traffic between your devices (e.g. your phone) to your server (physically in the same location) gets routed trough the internet, which means you have to utilize your upload and download bandwidth at the same time (e.g. while streaming from Plex), which not only causes a slower connection but also adds an unnecessary high latency.

Traefik 2.0 + Docker: A Simple Step by Step Guide

Tue, 24 Sep 2019 00:00:00 +0000

Image Source

Introduction

In this tutorial we will go trough the following things:

Setup and configure Traefik in a Docker container
Let’s Encrypt setup for automatic HTTPS certificates
Deploy a simple service (Portainer) and expose it to the internet

You will find all the required configuration files in our Git repository.

Prerequisites

In order to follow along, you need these things:

Docker (obviously)
Docker Compose
A domain
Ports 80 and 443 forwarded to your Docker host

Setup and configure Traefik with Let’s Encrypt

Let’s get started by setting up Traefik.

Traefik 2.0 + Docker: An Advanced Guide

Tue, 24 Sep 2019 00:00:00 +0000

Image Source

Introduction

This tutorial is the second part of this article. We will go trough the following configurations:

Add a file provider to traefik.yml
Create a config file for a central configuration for storing middlewares config.yml.
Configure a middleware chain

You will find all the required configuration files in our Git repository.

Prerequisites

In order to follow along, you’ll need to read this post!

Update Traefik configuration

To setup a reusable middleware add an additional provider in the Traefik configuration file traefik.yml (/opt/containers/traefik/traefik.yml) (lines 15 and 16).