Is it some kind of a web application or?
Are you using proxy for the port 3000 on the origin host/server?
Are you running HTTP only, how about HTTPS and a valid SSL certificate?
Anything in the log files for the tunnel connection and particular hostname?
If you run the cloudflared tunnel command with -loglevel debug.
Are you running HTTP only, how about HTTPS and a valid SSL certificate?
i tried access my companion. with both HTTPS/HTTP, both doesn’t work. I never purchase any SSL cert as i followed those YT setup video and understand cloudflare by default secured the whole channel while external user access to my app which installed locally.
i try to use my window machine (without admin right currently), and able to run cloudflare within docker, ain’t sure how to pull out log. But i try the UI and pump in my ray ID in the error page. No error generated. A bit lost here
i tried CGPT to help me pull the log from docker, also trim the content as i am allowed only to post 4 links in post
PS C:\Users\it’s me> docker logs funny_lalande --tail 10PS C:\Users\it’s me> docker logs funny_lalande --tail 10
2025-02-10T01:17:13Z ERR Request failed error=“Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: dial tcp [::1]:8055: connect: connection refused” connIndex=2 dest=https://ttrack.nextnovas.com/ event=0 ip=<masked-ip…> type=http
2025-02-10T01:17:13Z ERR error=“Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: dial tcp [::1]:8055: connect: connection refused” connIndex=2 event=1 ingressRule=0 originService=https://localhost:8055
2025-02-10T01:17:13Z ERR Request failed error=“Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: dial tcp [::1]:8055: connect: connection refused” connIndex=2 dest=https://ttrack.nextnovas.com/favicon.ico event=0 ip=<masked-ip…> type=http
PS C:\Users\it’s me>
Is your Nginx serving this app over an IPv6 in the vhost config file, which might be misconfigured, or rather “by default” and you’ve got both IPv4 and IPv6 on the origin enabled and configured correctly?
If so, then noTLSVerify option should be enabled from the Zero Trust dashboard for your tunnel public hostname.
sorry for the confusion, in my top post, coz i was using my mac mini, it’s accessing localhost:3000 (open webui)
this morning i am with my win laptop to continue troubleshoot, which is accessing localhost:8055 (directus CMS), (that’s why the recent error log u saw are pointing to 8055), it’s correct. I didn’t mess up with the ports, no worry. i couldn’t use my mac mini now but i wanna continue troubleshoot with my win laptop now to troubleshoot lol
if it confused u, let’s jz say i am troubleshooting for localhost:8055, to be map to ttrack.nextnovas.com/