Cloudflared routes tunnel to irrelevant domain: pre-http.cc -> pre-http.cc.be-political.org

This behavior makes absolutely no sense for it to resolve as a subdomain of something not mentioned in the parameters

mατh.rαdOP•8/28/24, 3:19 AM

 cloudflared tunnel route dns main pre-http.cc

2024-08-28T03:10:20Z INF Added CNAME pre-http.cc.be-political.org which will route to this tunnel tunnelID=afa25c50-1ec5-4711-abda-3ab17cb098e5

 cloudflared tunnel route dns main pre-http.cc

2024-08-28T03:10:20Z INF Added CNAME pre-http.cc.be-political.org which will route to this tunnel tunnelID=afa25c50-1ec5-4711-abda-3ab17cb098e5

Erisa•8/28/24, 3:24 AM

When you authorised cloudflared originally it made you select a zone, this one command for whatever reason will only work on that selected zone. I would honestly just create dns records manually rather than use that command since it doesn't make a whole lot of sense

mατh.rαdOP•8/28/24, 3:25 AM

EErisa When you authorised cloudflared originally it made you select a zone, this one c...

mατh.rαdOP•8/28/24, 3:27 AM

I attempted to manually set the DNS record for my domain with a CNAME that lead to the same place, but it failed to reach the origin resource so I suspected this failure to create the correct dns record may have been related

mατh.rαdOP•8/28/24, 3:28 AM

My application was on port 3003 and I was able to successfully get a response from curl on localhost:3003 yet both using the cli and installing a tunnel to interface via the web failed

Erisa•8/28/24, 3:28 AM

It should be a proxied record leading to tunnelid.cfargotunnel.com where tunnelid is that long id

mατh.rαdOP•8/28/24, 3:29 AM

one moment, I deleted the records but I'm pretty sure I followed that procedure to manually set the record

Erisa•8/28/24, 3:29 AM

what's the exact error you get? failed to reach origin resource sounds unrelated to dns

EErisa what's the exact error you get? failed to reach origin resource sounds unrelated...

mατh.rαdOP•8/28/24, 3:32 AM

2024-08-28T02:51:09Z 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 127.0.0.1:3003: connect: connection refused" connIndex=1 event=1 ingressRule=0 originService=http://localhost:3003

2024-08-28T02:51:09Z 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 127.0.0.1:3003: connect: connection refused" connIndex=1 event=1 ingressRule=0 originService=http://localhost:3003

mατh.rαdOP•8/28/24, 3:33 AM

since it's little work to set up, I'm going to recreate the tunnel(as I've done multiple times) would you rather it be via the client or the website interface for the tunnels

mατh.rαdOP•8/28/24, 3:33 AM

Also the only reason for why I posted it under this error is because I belieived these were related as the initial problem made no sense at all

mατh.rαdOP•8/28/24, 3:34 AM

I can confirm the service is accessible via netstat as well as just making a simple curl request

Erisa•8/28/24, 3:34 AM

it doesnt matter which, and recreating likely won't help with that error. that error means that the traffic reaches the tunnel successfully (so dns is fine and the tunnel works) but the cloudflared process can't reach the origin. are you running it in something funky like docker?

mατh.rαdOP•8/28/24, 3:35 AM

it's just a simple express application. I've reduced it to this for debugging purposes and simplicity

const app = require("express")();

app.get("/*", (request, response) => {
    response.send(request.url)
})

app.listen(3003)

const app = require("express")();

app.get("/*", (request, response) => {
    response.send(request.url)
})

app.listen(3003)

mατh.rαdOP•8/28/24, 3:35 AM

I'm not sure why its not picking up anything

Erisa•8/28/24, 3:36 AM

and you didn't use docker, just the regular install commands?

mατh.rαdOP•8/28/24, 3:36 AM

I have little experience with docker, but I will say that I initialized the application with solely npm

mατh.rαdOP•8/28/24, 3:36 AM

I did use docker to install cloudflared

Erisa•8/28/24, 3:36 AM

using docker for any part of this adds a load of extra considerations that complicate things, this is why I'm asking

Erisa•8/28/24, 3:36 AM

that will be it then

Erisa•8/28/24, 3:37 AM

docker has network isolation, so it can't access the same localhost as on your host machine

mατh.rαdOP•8/28/24, 3:37 AM

I see

mατh.rαdOP•8/28/24, 3:37 AM

How can I install it without docker? The only option for both the cli and the individual tunnel set up uses docker - when documented

mατh.rαdOP•8/28/24, 3:38 AM

I am using ubuntu

Erisa•8/28/24, 3:38 AM

the quick and easy fix is to either not use docker, or throw

--network host

--network host

on the docker run command to use the host network
the proper/smarter fix is to properly implement docker networks but thats a whole other thing im not getting into

Mmατh.rαd How can I install it without docker? The only option for both the cli and the in...

Erisa•8/28/24, 3:38 AM

uh where are you seeing that as the only option? there should be manual install options for both

Erisa•8/28/24, 3:39 AM

for web setups there's even a copy and paste command that installs the Ubuntu package

mατh.rαdOP•8/28/24, 3:40 AM

mατh.rαdOP•8/28/24, 3:40 AM

Interesting though

mατh.rαdOP•8/28/24, 3:40 AM

My mistake, I did not use docker for this:

mατh.rαdOP•8/28/24, 3:40 AM

Erisa•8/28/24, 3:40 AM

oh just click debian lol, ubuntu is based on it

Erisa•8/28/24, 3:40 AM

it works just the same, you can also use those commands there if you want. either is fine

mατh.rαdOP•8/28/24, 3:41 AM

is the cli known to be glitchy(referring to the initial problem)? would you recommend using the website or the client

mατh.rαdOP•8/28/24, 3:42 AM

I've noticed it has had strange and misleading behavior before

mατh.rαdOP•8/28/24, 3:42 AM

Unintuitive, at least

Erisa•8/28/24, 3:43 AM

the route dns command is the only thing that stands out as glitchy, the rest of the cli is just difficult to understand but does give you a bit more flexibility once you've worked it out. the web setup is easier, you just run one command and click some buttons

Erisa•8/28/24, 3:44 AM

which one to choose is entirely up to you

mατh.rαdOP•8/28/24, 3:44 AM

I'll try with the client again

mατh.rαdOP•8/28/24, 3:45 AM

if you were refering to the cloudflared repo, which Debian distribution

mατh.rαdOP•8/28/24, 3:45 AM

this: https://pkg.cloudflare.com/index.html#ubuntu-focal

mατh.rαdOP•8/28/24, 3:45 AM

im guessing you were most likely talking about the website though

Erisa•8/28/24, 3:46 AM

the website install is where i said just use the debian link

Erisa•8/28/24, 3:46 AM

for the pkg. site, use the instructions for the Ubuntu version you have

mατh.rαdOP•8/28/24, 3:47 AM

Okay, I might run into the same problem again because I'm pretty sure that never used docker

Erisa•8/28/24, 3:47 AM

i think 24.04 isn't on there but from memory the 22.04 one should work fine

mατh.rαdOP•8/28/24, 3:47 AM

yeah i have .03

mατh.rαdOP•8/28/24, 3:47 AM

or did at least

Erisa•8/28/24, 3:47 AM

i dont think any ubuntu version ends in .03

mατh.rαdOP•8/28/24, 3:48 AM

sorry I meant the client

2024-08-28T02:51:09Z 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 127.0.0.1:3003: connect: connection refused" connIndex=1 event=1 ingressRule=0 originService=http://localhost:3003

Cloudflared routes tunnel to irrelevant domain: pre-http.cc -> pre-http.cc.be-political.org

Similar Threads

Similar Threads

Similar Threads

Cloudflared routes tunnel to irrelevant domain: pre-http.cc -> pre-http.cc.*be-political.org*

Similar Threads

Similar Threads

Similar Threads

Cloudflared routes tunnel to irrelevant domain: pre-http.cc -> pre-http.cc.be-political.org