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
The settings in the Public Hostname page reads
Subdomain : amz
DNS is configured via CNAME and the tunnel is marked healthy but times out if we try to access
My DNS resolution looks fine
~ ❯ nslookup amz.phoenixhq.space
amz.phoenixhq.space canonical name = 619fedbc-c07b-4c76-b264-28a1c6460def.cfargotunnel.com.
Both processes are currently running so you can browse over to
- Named tunnel at
- Quick tunnel at
to see the difference