Can't access nocodb through cloudflared tunnel

Self-Host
1

I’m running nocodb from docker compose from the official nocodb wiki. Cloudflared is ran natively on the machine, which has Ubuntu server on it. Whenever I try to access it through I get this: “Hmm. We’re having trouble finding that site.” from Firefox. I know cloudflared tunnel itself works because other stuff routed through it works. Is there a way I can fix this?

2

This is likely a network bridging issue between your native Cloudflared and the Docker container. Here’s how to fix it:

1. Check your tunnel’s service URL

Make sure your Cloudflare tunnel config points to the correct internal address. Since NocoDB runs in Docker, you need to use:

  • http://localhost:8080 — if Docker publishes the port to host
  • http://host.docker.internal:8080 — won’t work here since cloudflared is outside Docker

2. Verify Docker port binding

In your docker-compose.yml, confirm NocoDB exposes the port to your host:

ports:
  - "8080:8080"

3. Set NC_PUBLIC_URL

NocoDB needs to know its public URL for proper redirects. Add this environment variable:

environment:
  - NC_PUBLIC_URL=https://your-tunnel-domain.com

4. Test locally first

Before the tunnel, confirm NocoDB works at http://localhost:8080 from the Ubuntu server itself:

curl -I http://localhost:8080

5. Cloudflared config example

Your tunnel config should look like:

ingress:
  - hostname: nocodb.yourdomain.com
    service: http://localhost:8080
  - service: http_status:404

If all else fails, try running cloudflared in Docker on the same network as NocoDB — that eliminates host/container networking issues entirely.

Let us know if any of these steps help!