Troubleshooting (v2)
Troubleshooting (v2)
Docker provider
- Verify
tsdproxy.enable=true - Check port labels: Port config
- For HTTPS targets:
tsdproxy.port.1: "443/https:443/https" - Self-signed certs: add
no_tlsvalidateoption - Check firewall
- Same Docker network as TSDProxy
- Network issues: use
tsdproxy.autodetect: "false"label and specify port explicitly
Lists provider
- Config is case-sensitive: Verify files
- Check file path in
lists:config
Common Errors
TLS certificate errors (self-signed)
Docker: tsdproxy.port.1: "443/https:443/https, no_tlsvalidate"
Lists: Set tlsValidate: false on the port
Network timeout
Firewall fix: sudo ufw allow in from 172.17.0.0/16
Funnel doesn’t work
Enable in ACL, add tailscale_funnel port option. See
Funnel Security for details.
Proxy stuck “Authenticating”
Verify OAuth credentials or AuthKey. Check logs. See Authentication Methods for setup.
Enabling debug logging
log:
level: tracepprof debug profiling
Set the TSDPROXY_PPROF environment variable to "true" before starting
TSDProxy to enable Go profiling endpoints:
services:
tsdproxy:
image: almeidapaulopt/tsdproxy:2
environment:
TSDPROXY_PPROF: "true"This exposes the following endpoints:
| Endpoint | Purpose |
|---|---|
/debug/pprof/ | Profile index |
/debug/pprof/cmdline | Command line |
/debug/pprof/profile | CPU profile |
/debug/pprof/symbol | Symbol table |
/debug/pprof/trace | Execution trace |
Warning
pprof endpoints expose internal runtime data. Never enable in production.
Last updated on