Stuck on "Congrats! You created a tunnel!

Getting started with Argo Tunnel creation. I’m able to get the tunnel created, but then all I see is the

Congrats! You created a tunnel!

Argo Tunnel exposes locally running applications to the internet by running an encrypted, virtual tunnel from your laptop or server to Cloudflare’s edge network.

Ready for the next step?

I’ve confirmed that I can access the specified site on the local network, and when I open the actual firewall I can get access to the site using the direct IP. The tunnel appears to be established, but I’m not able to access the local resources.

Hey @technology7
I feel that you need to add a bit more context here, so we can check what is going on.
I feel that something is missing from the puzzle.

Would you mind setting your loglevel to debug, and re-check your cloudflared.log file for errors?
if you will share it with us make sure to remove any sensitive info like IPs, domains etc.

you can also set transport-loglevel to debug too, so you can get more information.
if you will share it with us, make sure to remove any sensitive info like IPs, domains etc.

Running on Windows, local firewall is off. Just updated to the most recent version (2021.8.7)

tunnel: 2572a463-8a6e-458f-badb-f9aa6f8bac7f
credentials-file: C:\Windows\System32\config\systemprofile.cloudflared\2572a463-8a6e-458f-badb-f9aa6f8bac7f.json
logfile: C:\Windows\System32\config\systemprofile.cloudflared\cloudflared.log
loglevel value: debug

ingress:
#ingress rules. The first is a test using the built in cloudflared webservice to display Hello World
service: hello_world

#ingress rule to publish the local XYZ site into Cloudflare
-hostname: XYZ.DOMAIN.COM
service: https://localhost:9251

#final ingress rule to generate 404 error if the page is not found
-service: http_status:404

The tunnel comes up, but then I get the error message from the default port http://localhost:8080

2021-08-30T20:21:56Z 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]:8080: connectex: No connection could be made because the target machine actively refused it.” cfRay=6870ba6c1d08182d-EWR originService=http://localhost:8080
2021-08-30T20:21:58Z 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]:8080: connectex: No connection could be made because the target machine actively refused it.” cfRay=6870ba79bd69175c-ORD originService=http://localhost:8080

localhost:8080 is the default ingress rule

Given that your logs show cloudflared trying to access that, it looks as if your config is not being picked up as you expect/hope.

You can pass it explicitly with --config <PATH> to cloudflared command.

1 Like

Yes, that’s what’s so strange. That’s what I get when specifying the path:
cloudflared tunnel --config C:\Windows\System32\config\systemprofile.cloudflared\config.yaml run

I’ve also copied the config and JSON to the %userprofile%.cloudflared folder and get the same behavior