Can someone try accessing my server?
For some reason cloudfare seems to be blocking my connection, but when at work it seemed to work just fine.
port.fadriqueserver.com
48 Replies
I am currently sharing data from my phone to my laptop
What's the error do you get?
oh, that's after CF Access
Are you using a tunnel? If so, it's likely your tunnel cannot reach your backend service. You can check logs (
journalctl -u cloudflared -f --lines=100)I am yes
Sep 25 15:26:42 raspberrypi cloudflared[2192]: 2023-09-25T13:26:42Z 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 192.168.1.129:7878: connect: connection refused" connIndex=0 dest=https://radarr.fadriqueserver.com/ event=0 ip=198.41.192.27 type=http
but docker container ls marks portainer as up for 8 hours
from your command line of the same server, can you reach your service?
curl http://192.168.1.129:7878 -vvv
if it's supposed to be a container, Idon't see any container bound to that port unless I'm blind. Is cloudflared running on the host or in a container as well?
in the host
means it's not cloudflared's fault, your web server is actually unreachable
there are no other containers running
well where is 7878 supposed to come from? None of the docker containers are bound to that
It looks like portainer uses 9443 by default which is exposed there, did you mean to use that?
i am using 8000 for portainer
So, why is your public hostname set to use
192.168.1.129:7878?is it?
That's what it looks like, double check your config
i have it at 9000
ahh sorry I see what we got confused by:
the cloudflared log you captured wasn't for port subdomain, it was for radarr
:
dial tcp 192.168.1.129:7878: connect: connection refused" connIndex=0 dest=**https://radarr.fadriqueserver.com/** event=0 ip=198.41.192.27 type=http
Although you may want to fix that as well lol
Using that journalctl command, try to find a log about a failure for dest=port.fadriqueserver.comAh sorry, ill check
Once you run the command, send a few requests/refresh your page
should i be using this same command? journalctl -u cloudflared -f --lines=100
Because last register is a few hours ago
Yea, should be. Just to double check: you are executing this on the same machine as the tunnel, right?
If it helps: You can get this same information from the Zero Trust GUI. If you navigate to Access -> Tunnels, click on your tunnel name, click on your connector uuid in the side panel, click "Begin Log Stream", and then send a request. It's possible portainer itself is 502ing, using this log stream would also expose non-errored requests
I am yes, i have another tunnel open for ssh, which i access from the browser
that seems to work just fine
you have two tunnels, same machine?
hostname, sorry
i have a different public hostname pointing at a different port for various containers
ah ok, makes sense.
Yea, I would use the log stream option within the dash, and send a request. You can expand the event for details, it should give more info eitherway
Making new requests doesnt seem to add anything
Sep 25 15:26:42 raspberrypi cloudflared[2192]: 2023-09-25T13:26:42Z 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 192.168.1.129:7878: connect: connection refused" connIndex=0 dest=https://radarr.fadriqueserver.com/ event=0 ip=198.41.192.27 type=http
Are you using the log stream function within the dash or journalctl?
journalctl
Only the log stream in the dash would show normal requests
(unless you changed the log level of cloudflared, I believe)
ill look it up
If you navigate to Access -> Tunnels, click on your tunnel name, click on your connector uuid in the side panel, click "Begin Log Stream", and then send a request
as soon as i use the log stream it works
stays empty though
Do you have two connectors/the same tunnel installed on two servers, by chance?
There shouldnt be, i only have 1 server, how might i see if i do?
When you clicked on your tunnel, how many connectors did you see in the right hand side panel?
hm, 2
I dont see where i could have installed it twice
Could this be on the same server?
I haven't messed around with how the dashboard shows connectors too much before, it's possible. You can click on each one, and see in the top bar "Connector Details" the origin IP and hostname it is running on, should give you enough info to tell
Yes indeed, i have one installed on my laptop, ive probably messed that up somehow, uninstalling could fix it?
yep, just remove the unnecessary/laptop connector
the problem is its randomly picking to route connections between each connector, and you just were getting unlucky/lucky with its failures
each connector/cloudflared instance should be able to serve all public hostnames of that tunnel
but yea,
cloudflared service uninstallIve been having this issue for a few days now, thank you
sure no problem 
, the giveaway there was that the requests were going through but you weren't seeing them in the connector logstream, because another connector was taking them
, the giveaway there was that the requests were going through but you weren't seeing them in the connector logstream, because another connector was taking them