Skip to content
Troubleshooting (v2)

Troubleshooting (v2)

Docker provider

  1. Verify tsdproxy.enable=true
  2. Check port labels: Port config
  3. For HTTPS targets: tsdproxy.port.1: "443/https:443/https"
  4. Self-signed certs: add no_tlsvalidate option
  5. Check firewall
  6. Same Docker network as TSDProxy
  7. Network issues: use tsdproxy.autodetect: "false" label and specify port explicitly

Lists provider

  1. Config is case-sensitive: Verify files
  2. 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: trace

pprof 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:

EndpointPurpose
/debug/pprof/Profile index
/debug/pprof/cmdlineCommand line
/debug/pprof/profileCPU profile
/debug/pprof/symbolSymbol table
/debug/pprof/traceExecution trace

Warning

pprof endpoints expose internal runtime data. Never enable in production.

Last updated on