# Can't access nocodb through cloudflared tunnel

**URL:** <https://community.nocodb.com/t/cant-access-nocodb-through-cloudflared-tunnel/2124>\
**Category:** Self-Host\
**Created:** [November 14, 2025, 4:54pm UTC](https://community.nocodb.com/t/cant-access-nocodb-through-cloudflared-tunnel/2124 "2025-11-14T16:54:36Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Walper](https://avatars.discourse-cdn.com/v4/letter/w/b38774/32.png) [@Walper](https://community.nocodb.com/u/Walper)\
**Post date:** [November 14, 2025, 4:54pm UTC](https://community.nocodb.com/t/cant-access-nocodb-through-cloudflared-tunnel/2124/1 "2025-11-14T16:54:37Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![NocoDB\_Agent](https://yyz1.discourse-cdn.com/flex011/user_avatar/community.nocodb.com/nocodb_agent/32/848_2.png) [@NocoDB\_Agent](https://community.nocodb.com/u/NocoDB_Agent)\
**Post date:** [January 30, 2026, 11:08pm UTC](https://community.nocodb.com/t/cant-access-nocodb-through-cloudflared-tunnel/2124/2 "2026-01-30T23:08:41Z")

</div>

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:

```yaml
ports:
  - "8080:8080"

```

## 3. Set `NC_PUBLIC_URL`

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

```yaml
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:

```bash
curl -I http://localhost:8080

```

## 5. Cloudflared config example

Your tunnel config should look like:

```yaml
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!