Cloudflare quick tunnel works but named tunnel doesn't

Zero Trust Cloudflare Tunnel
1

Hi I’ve service running on localhost:8080 which is live.
I’ve a quick tunnel https://closely-colour-banned-farms.trycloudflare.com which is also working fine.
./cloudflared --url http://localhost:8080. It shows Bad request, this is expected behavior.

But named tunnel doesn’t work
and I get ERR_CONNECTION_TIMED_OUT.

My named tunnel is managed via Cloudflare UI and not via config file. I run it with
./cloudflared tunnel run --token xyz

I’m not currently running it as a service, as it’s from a termux (android) process. My binary is custom built for android as suggested by kai here https://community.cloudflare.com/t/cloudflared-on-android/271072/7

The settings in the Public Hostname page reads
Public Hostname
Subdomain : amz
domain: phoenixhq.space

Service
Type: HTTP
URL: localhost:8080

DNS is configured via CNAME and the tunnel is marked healthy but times out if we try to access http://619fedbc-c07b-4c76-b264-28a1c6460def.cfargotunnel.com. or http://amz.phoenixhq.space

My DNS resolution looks fine
~ ❯ nslookup amz.phoenixhq.space
Server: 2409:40e0:103c:b4d::38
Address: 2409:40e0:103c:b4d::38#53
Non-authoritative answer:
amz.phoenixhq.space canonical name = 619fedbc-c07b-4c76-b264-28a1c6460def.cfargotunnel.com.

Both processes are currently running so you can browse over to

  1. Named tunnel at https://amz.phoenixhq.space
  2. Quick tunnel at https://closely-colour-banned-farms.trycloudflare.com
    to see the difference
4

The CNAME DNS record pointing at the tunnel has to be proxied. Proxy it, wait for DNS Propagation, and try again.

5

I created the record with the command ./cloudflared tunnel route dns cobalt amz.phoenixhq.space, here cobalt is the tunnel name.
It is orange-clouded (proxied)

This issue (quick tunnel working but not named tunnel) is persistent across my mac as well as the android device which is the focus of this thread.

It has been quite some time, I’m trying this on and off for three days, and it still isn’t resolving.

6

If you navigate to your cloudflare website/zone phoenixhq.space , go to DNS Records, find amz, click “Edit”, and turn on proxy. It’s either not proxied, or something has gone horribly wrong. A screenshot would help.
If it was proxied, you would see Cloudflare IPs returned in A/AAAA records, and not the cfargotunnel.com CNAME returned. The cfargotunnel.com subdomains are virtual, only Cloudflare internally can resolve them via proxy, hence why you get an error connecting.

If it is proxied, perhaps you have the zone in two accounts or something? The overview page should tell you if it’s active or not, and at the bottom of the DNS Records page, it tells you which nameservers to use.

8

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.