Using Request Tracing for Debugging
📖 Usage
·
Updated 2 weeks ago
When to Use Request Tracing
Request Tracing helps when:
- A route returns 502 or other errors
- You suspect a redirect loop
- Requests are not reaching the backend
- You want to check which headers/IPs are arriving
How to Enable Tracing
- Open the affected route (Edit Modal)
- Switch to the Debug tab
- Enable the Request Tracing toggle
- Save the route
Reading Trace Entries
The Debug tab shows a live table with all requests:
- Green (2xx) — Request successful
- Yellow (4xx) — Client error (404 Not Found, 403 Forbidden, etc.)
- Red (5xx) — Server error (502 Bad Gateway, 503 Service Unavailable, etc.)
The table auto-refreshes every 3 seconds.
Common Error Patterns
502 Bad Gateway
The backend is unreachable. Check if the peer is online and the correct port is configured.
Endless 302 Redirects
If you see multiple 302 entries in a row, there is a redirect loop. Check the route authentication settings.
No Entries
If no entries appear despite sending requests, traffic is not reaching the route. Check DNS settings and Caddy configuration.
Important
- Only enable tracing temporarily — it generates additional log entries
- Works only on HTTP routes (not L4/TCP)
- An orange Debug badge appears in the route list when tracing is active