18 posts tagged with "Traefik"

I recently worked on a project where we needed to secure our application by requiring users to authenticate against an Identity Provider before accessing it.

Last month, while migrating our Traefik instance to our new Nomad cluster, I also made the switch from Traefik EE to Traefik Proxy. The transition went smoothly, but I had to make a few minor adjustments along the way.

Recently, failures occurred randomly in our GitLab CI pipelines when pushing docker images to our internal Docker registry.

In the GitLab CI output, all I saw was the following error:

error parsing HTTP 499 response body: invalid character 'C' looking for 
beginning of value: "Client Closed Request"

Can we conditionally use Traefik Basic Auth? I don't want to use Basic Auth for requests coming from the same server due to solving an issue with a third-party tool that was not able to deal with URLs containing basic auth credentials.

While extensively testing our Boundary setup, we realized that SSH sessions got terminated after about 60 seconds of inactivity. Of course, this is far from ideal so we had to figure out the problem and then fix it.

HashiCorp Boundary provides access to applications and critical systems with fine-grained authorizations without managing credentials or exposing your network internals.

In the process of migrating our Hashicorp Nomad workload to our new Nomad cluster, I also tried to simplify our CI pipelines and ran into an issue with Nomad.

Following our guide to set up Traefik, Docker, and Compose with multiple networks, I ran into a problem:

a network with name customer_staging_default exists but was not created for project "customer_staging"
Set `external: true` to use an existing network

network customer_staging_default was found but has incorrect label com.docker.compose.network set to "staging_default"

In Traefik providers are infrastructure components (e.g. container engines, cloud providers, or key-value stores) that can be queried in order to find relevant information about the routing configuration.

Recently, we've been running into a weird problem. After restarting 2 nodes in our Nomad cluster, we could not properly access GitLab via SSH anymore. Web access was working fine, also cloning via https:// worked, but not via SSH which is what most of our developers use by default.