Home / Load Balancer / Fix Traefik Reverse Proxy Routing Failed

Load Balancer

Fix Traefik Reverse Proxy Routing Failed

Resolve Traefik reverse proxy routing failures by checking router configuration, service discovery, and ingress settings.

Published: Apr 7, 20268 min readBy FixWikiHub Editorial Team

Abstract illustration for load balancer troubleshooting guides.

Introduction

Traefik reverse proxy fails to route requests to backend services. Requests receive 404, 502, or timeout errors instead of reaching target services.

Symptoms

```bash $ curl http://traefik-server/app

404 page not found ```

Traefik logs:

bash

time="2024-01-01T10:00:00Z" level=error msg="service \"app\" not found"
time="2024-01-01T10:00:00Z" level=error msg="no routers matching request"

Backend unreachable:

```bash $ curl http://traefik-server/app

502 Bad Gateway ```

Dashboard empty:

bash

Traefik dashboard shows:
- Routers: 0
- Services: 0
- Middlewares: 0

Common Causes

1.Router not configured - Missing routing rules
2.Service not discovered - Backend not registered
3.Docker provider issues - Container labels missing
4.Kubernetes Ingress issues - Ingress resource wrong
5.Health check failing - Backend marked unhealthy
6.TLS certificate issues - HTTPS routing blocked

Step-by-Step Fix

1.Check logs for specific error messages
2.Verify configuration settings
3.Test network connectivity
4.Review recent changes
5.Apply corrective action
6.Verify the fix

Step 1: Check Traefik Status

```bash # Check Traefik process: docker ps | grep traefik

# Or systemd: systemctl status traefik

# Check Traefik logs: docker logs traefik

# Or: journalctl -u traefik -f

# Check Traefik version: docker exec traefik traefik version

# Check Traefik dashboard: curl http://localhost:8080/api/overview

# Check routers: curl http://localhost:8080/api/http/routers

# Check services: curl http://localhost:8080/api/http/services

# Check providers: curl http://localhost:8080/api/providers ```

Step 2: Check Traefik Configuration

```bash # Check static configuration: docker exec traefik cat /etc/traefik/traefik.yml

# Or: cat /etc/traefik/traefik.yml

# Check providers config: # Docker provider: providers: docker: endpoint: "unix:///var/run/docker.sock" exposedByDefault: false

# Kubernetes provider: providers: kubernetesIngress: endpoint: "https://kubernetes.api"

# File provider: providers: file: filename: /etc/traefik/dynamic.yml

# Check dynamic configuration: cat /etc/traefik/dynamic.yml

# Check entrypoints: curl http://localhost:8080/api/entrypoints ```

Step 3: Check Router Configuration

```bash # Check routers via API: curl http://localhost:8080/api/http/routers | jq .

# Check specific router: curl http://localhost:8080/api/http/routers/app@docker | jq .

# Expected router config: { "service": "app", "rule": "Host(app.example.com)", "entryPoints": ["web"], "status": "enabled" }

# Docker labels for router: docker inspect app-container | grep -A10 Labels

# Required labels: traefik.enable=true traefik.http.routers.app.rule=Host(app.example.com) traefik.http.routers.app.entrypoints=web

# Check rule syntax: # Common rules: # Host(example.com) # PathPrefix(/app) # Host(example.com) && PathPrefix(/api)

# Check rule matching: curl -H "Host: app.example.com" http://traefik-server/ ```

Step 4: Check Service Discovery

```bash # Check services via API: curl http://localhost:8080/api/http/services | jq .

# Check specific service: curl http://localhost:8080/api/http/services/app@docker | jq .

# Docker labels for service: traefik.http.services.app.loadbalancer.server.port=8080

# Check backend servers: curl http://localhost:8080/api/http/services/app@docker | jq .loadBalancer.servers

# Should show backend IPs/ports

# Kubernetes service discovery: kubectl get svc -n traefik

# Check service endpoints: kubectl get endpoints app-service -n myapp

# Check Ingress: kubectl get ingress -n myapp

# Check Ingress annotations: kubectl get ingress app-ingress -n myapp -o yaml | grep annotations ```

Step 5: Check Docker Provider

```bash # Check Docker provider status: curl http://localhost:8080/api/providers/docker

# Check Docker connectivity: docker exec traefik ls -la /var/run/docker.sock

# Test Docker API from Traefik: docker exec traefik curl http://localhost:2375/containers/json

# Check Docker network: docker network ls

# Ensure containers on same network: docker network inspect traefik-net

# Check container labels: docker inspect app | jq .[0].Config.Labels

# Required labels: { "traefik.enable": "true", "traefik.http.routers.app.rule": "Host(app.example.com)", "traefik.http.services.app.loadbalancer.server.port": "8080" }

# Add missing labels: docker update --label-add traefik.enable=true app ```

Step 6: Check Kubernetes Ingress

```bash # Check Ingress resource: kubectl get ingress -A

# Check Ingress details: kubectl describe ingress app-ingress -n myapp

# Check Ingress class: kubectl get ingressclass

# Traefik IngressClass: cat << 'EOF' | kubectl apply -f - apiVersion: networking.k8s.io/v1 kind: IngressClass metadata: name: traefik spec: controller: traefik.io/ingress-controller EOF

# Check Ingress annotations: annotations: kubernetes.io/ingress.class: traefik traefik.ingress.kubernetes.io/router.entrypoints: web

# Check service backend: kubectl get svc app-service -n myapp

# Check endpoints: kubectl get endpoints app-service -n myapp

# Test service: kubectl exec -it test-pod -- curl http://app-service:8080 ```

Step 7: Check Health Checks

```bash # Traefik health check config: # Docker labels: traefik.http.services.app.loadbalancer.healthcheck.path=/health traefik.http.services.app.loadbalancer.healthcheck.interval=10s traefik.http.services.app.loadbalancer.healthcheck.timeout=5s

# Check service health: curl http://localhost:8080/api/http/services/app@docker | jq .loadBalancer.healthCheck

# Check backend health: curl http://localhost:8080/api/http/services/app@docker | jq .serverStatus

# Output: # {"http://10.0.0.1:8080": "UP", "http://10.0.0.2:8080": "DOWN"}

# Test backend health endpoint: curl http://backend:8080/health

# If health check failing: # Disable health check temporarily: traefik.http.services.app.loadbalancer.healthcheck.path=

# Or fix health endpoint on backend ```

Step 8: Check TLS Configuration

```bash # Check TLS routers: curl http://localhost:8080/api/http/routers | jq '.[] | select(.tls != null)'

# TLS router labels: traefik.http.routers.app.tls=true traefik.http.routers.app.tls.certresolver=myresolver

# Check certificate resolver: curl http://localhost:8080/api/tls/certificates

# Let's Encrypt config: certificatesResolvers: myresolver: acme: email: admin@example.com storage: acme.json httpChallenge: entryPoint: web

# Check ACME certificates: cat /etc/traefik/acme.json | jq .

# Test HTTPS: curl https://app.example.com

# Check TLS entrypoint: curl http://localhost:8080/api/entrypoints/websecure | jq . ```

Step 9: Check Middlewares

```bash # Check middlewares: curl http://localhost:8080/api/http/middlewares | jq .

# Check middleware attached to router: curl http://localhost:8080/api/http/routers/app@docker | jq .middlewares

# Middleware labels: traefik.http.routers.app.middlewares=auth,ratelimit

# Common middlewares: # auth - Basic auth # ratelimit - Rate limiting # stripPrefix - Path prefix removal # redirectScheme - HTTP to HTTPS redirect

# Check middleware config: traefik.http.middlewares.auth.basicauth.users=admin:$apr1$...

# Test middleware: curl -H "Host: app.example.com" -u admin:password http://traefik-server/

# Check middleware errors: docker logs traefik | grep middleware ```

Step 10: Traefik Verification Script

```bash # Create verification script: cat << 'EOF' > /usr/local/bin/check-traefik.sh #!/bin/bash

API="http://localhost:8080/api"

echo "=== Traefik Overview ===" curl -s $API/overview | jq .

echo "" echo "=== Entrypoints ===" curl -s $API/entrypoints | jq '.[] | {name, address}'

echo "" echo "=== HTTP Routers ===" curl -s $API/http/routers | jq '.[] | {name, rule, service, status}'

echo "" echo "=== HTTP Services ===" curl -s $API/http/services | jq '.[] | {name, loadBalancer.servers, serverStatus}'

echo "" echo "=== Providers ===" curl -s $API/providers | jq .

echo "" echo "=== Docker Containers ===" docker ps --filter label=traefik.enable=true --format "table {{.Names}}\t{{.Status}}"

echo "" echo "=== Test Routing ===" curl -s -H "Host: app.example.com" http://localhost/ | head -20

echo "" echo "=== Traefik Logs (last 20) ===" docker logs traefik --tail 20 2>&1 | grep -E "error|warn|router|service" EOF

chmod +x /usr/local/bin/check-traefik.sh

# Run: /usr/local/bin/check-traefik.sh

# Watch dashboard: watch -n 5 'curl -s http://localhost:8080/api/http/routers | jq length' ```

Traefik Routing Checklist

Check	Command	Expected
Traefik running	docker ps	Container up
Routers configured	API routers	Routers listed
Services discovered	API services	Backends listed
Docker labels	docker inspect	Labels present
Rule matching	curl with Host	Routes correctly
Health status	API serverStatus	Backends UP

Verification

```bash # After fixing routing

# 1. Check routers curl http://localhost:8080/api/http/routers // Routers listed with status enabled

# 2. Check services curl http://localhost:8080/api/http/services // Services with backends

# 3. Test routing curl -H "Host: app.example.com" http://traefik-server/ // Response from backend

# 4. Check dashboard # Open http://traefik:8080 // Shows routers and services

# 5. Check logs docker logs traefik --tail 50 // No errors

# 6. Test all routes curl http://app.example.com/api curl http://app.example.com/health // All working ```

[Fix HAProxy Backend Health Check Failed](/articles/fix-haproxy-backend-health-check-failed)
[Fix Nginx Upstream Timed Out](/articles/fix-nginx-upstream-timed-out)
[Fix Load Balancer Backend Unhealthy](/articles/fix-load-balancer-backend-unhealthy)

[Fix Fix Haproxy Backend 503 Issue in Load Balancer](fix-haproxy-backend-503)
[How to Fix HAProxy Backend Connection Errors and 503 Failures](fix-haproxy-backend-connection-503-error-deep)
[HAProxy All Backends Down: Complete Recovery Guide](fix-haproxy-backend-down-all)
[Fix Fix Haproxy Backend Down Issue in Load Balancer](fix-haproxy-backend-down)
[Fix HAProxy Backend Health Check Failed](fix-haproxy-backend-health-check-failed)

Was this guide helpful?

Related search paths

People also search for

If the symptom is close but not identical, these search paths usually surface the right neighboring fixes faster than scrolling the full archive.

Traefik Reverse Proxy Routing Failed Traefik Reverse Proxy Routing Failed Load Balancer Traefik Reverse Proxy Routing Failed troubleshooting Traefik Reverse Proxy Routing Failed fix Resolve Traefik reverse proxy routing failures by checking router configuration, service discovery, and ingress settings Load Balancer Resolve Traefik reverse proxy routing failures by checking router configuration, service discovery, and ingress settings

Explore Related Topics

Browse Guides from Other Categories

Discover troubleshooting guides from related categories to expand your knowledge.

FAQ

Load Balancer Troubleshooting FAQs

Common questions about troubleshooting and preventing similar issues

How do I know if this load-balancer-issues troubleshooting guide applies to my situation?

This guide is designed for load-balancer-issues issues. If you're experiencing similar symptoms described in the article, follow the step-by-step instructions. Start with the most common causes and work through the diagnostic process.

Is it safe to follow these load-balancer-issues troubleshooting steps?

Yes, all steps are designed to be safe and non-destructive. We recommend creating backups before making significant changes and testing each step before proceeding to the next.

How long does it typically take to resolve this type of load-balancer-issues issue?

Most load-balancer-issues issues can be resolved within 30 minutes to 2 hours, depending on the complexity and root cause. Follow the troubleshooting flow to identify and fix the problem efficiently.

How can I prevent this load-balancer-issues issue from happening again?

Regular maintenance, monitoring, and following best practices for load-balancer-issues configuration can help prevent recurrence. Consider implementing automated checks and alerts for early detection.

Written by

FixWikiHub Editorial Team

Our editorial team consists of experienced DevOps engineers, systems administrators, and cloud architects with hands-on experience in production environments across AWS, Azure, GCP, and on-premises infrastructure.

Every guide undergoes technical review for accuracy and is updated when software versions, commands, or best practices change.

Last updated: Apr 7, 2026

About our team

Important Notice

Disclaimer & Safety Guidelines

The troubleshooting steps in this guide are provided for educational and informational purposes. Before applying any changes to production systems:

Test in a staging environment first — Always verify commands and configurations in a non-production environment before deploying to live systems.
Create backups — Ensure you have current backups of databases, configurations, and critical files before making changes.
Understand the impact — Review how each step may affect your specific environment, dependencies, and users.
Consult official documentation — This guide supplements, but does not replace, official vendor documentation and best practices.

FixWikiHub is not responsible for any damages arising from the use of this content. See our Terms of Use for more information.

Resources

Official Documentation & Further Reading

For authoritative information, consult the official documentation for the technologies discussed in this guide. Our troubleshooting content supplements, but does not replace, vendor documentation.

AWS Documentation — Official Amazon Web Services guides and API references
Kubernetes Documentation — Official Kubernetes documentation
Nginx Documentation — Official Nginx web server documentation
Apache Documentation — Official Apache HTTP Server documentation
Docker Documentation — Official Docker container documentation

Fix Traefik Reverse Proxy Routing Failed

Introduction

Symptoms

Common Causes

Step-by-Step Fix

Step 1: Check Traefik Status

Step 2: Check Traefik Configuration

Step 3: Check Router Configuration

Step 4: Check Service Discovery

Step 5: Check Docker Provider

Step 6: Check Kubernetes Ingress

Step 7: Check Health Checks

Step 8: Check TLS Configuration

Step 9: Check Middlewares

Step 10: Traefik Verification Script

Traefik Routing Checklist

Verification

People also search for

Browse Guides from Other Categories

WordPress

SSL

DNS

Load Balancer Troubleshooting FAQs

FixWikiHub Editorial Team

Disclaimer & Safety Guidelines

Official Documentation & Further Reading

Fix Traefik Reverse Proxy Routing Failed

Introduction

Symptoms

Common Causes

Step-by-Step Fix

Step 1: Check Traefik Status

Step 2: Check Traefik Configuration

Step 3: Check Router Configuration

Step 4: Check Service Discovery

Step 5: Check Docker Provider

Step 6: Check Kubernetes Ingress

Step 7: Check Health Checks

Step 8: Check TLS Configuration

Step 9: Check Middlewares

Step 10: Traefik Verification Script

Traefik Routing Checklist

Verification

Related Issues

Related Articles

People also search for

Share this guide

More Load Balancer Troubleshooting Guides

Browse Guides from Other Categories

Load Balancer Troubleshooting FAQs

FixWikiHub Editorial Team

Disclaimer & Safety Guidelines

Official Documentation & Further Reading