Site Tools


folkzone:troubleshooting:cloudflared_container_name_resolution

Cloudflared Container Name Resolution

DEPRECATED: This troubleshooting guide is no longer relevant for folk.zone. The nitro server uses direct HTTPS via Let's Encrypt instead of Cloudflare tunnels.

Cloudflared cannot resolve Docker container names.

Symptom

Services not accessible via Cloudflare tunnel. cloudflared logs show connection errors.

Cause

Cloudflared is running as a system service on the host instead of in Docker. When running as a system service, it cannot resolve Docker container names like `caddy:80`.

Fix

Run cloudflared in Docker on the same network as other services.

Configuration: ```yaml services:

cloudflared:
  image: cloudflare/cloudflared:latest
  command: tunnel --no-autoupdate run --token YOUR_TOKEN
  networks:
    - folkzone_net

```

Steps:

1. Add cloudflared service to docker-compose.yml
2. Ensure it uses the same network as other services
3. Remove any system service installation of cloudflared
4. Restart: `docker compose up -d cloudflared`

Prevention

Always run tunnel services in Docker alongside other services to enable proper container name resolution.

See Also

folkzone/troubleshooting/cloudflared_container_name_resolution.txt · Last modified: by 127.0.0.1