aeleos / cloudflared

Cloudflare Tunnel Instructions and Template for Unraid
173 stars 21 forks source link

ERR error="Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: EOF #14

Closed fishermanG closed 3 years ago

fishermanG commented 3 years ago

Heyo

Thanks for the amazing guide. Now I can close off all the exposed 80 and 443 ports. Everything works fine e.g. multiple domains

But.. the docker log is flooded with this

2021-09-01T14:33:19Z INF Starting metrics server on 127.0.0.1:34395/metrics 2021-09-01T14:33:20Z INF Connection c0a8d328-a652-461d-bfc8-535d9c91e56d registered connIndex=0 location=SEA 2021-09-01T14:33:21Z INF Connection 6b41f4fa-d0c0-48bb-83e8-23d81a31d4fa registered connIndex=1 location=HKG 2021-09-01T14:33:22Z INF Connection 62a34012-8ed3-4325-a261-a19811f29a9c registered connIndex=2 location=SEA 2021-09-01T14:33:23Z INF Connection acdd26d8-0047-4a1e-97bc-151c4fee13b9 registered connIndex=3 location=HKG 2021-09-01T14:34:09Z ERR error="Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: EOF" cfRay=687f37bd84af59ce-IAD originService=https://192.168.1.11:18443

2021-09-01T14:34:10Z ERR error="Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: EOF" cfRay=687f37c6a4be212d-SJC originService=https://192.168.1.11:18443

2021-09-01T14:37:03Z ERR error="Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: EOF" cfRay=687f3bff16f52f55-DFW originService=https://192.168.1.11:18443

Any idea?

martinkeat commented 3 years ago

Just setup cloudflareds myself - same issue.

aeleos commented 3 years ago

@fishermanG @martinkeat I also see these logs in general, and my understanding is that it isn't a problem. I haven't figured out what causes it but I haven't found anything that is broken so my assumption is that it is fine.

aeleos commented 3 years ago

Closing this for now, if someone knows the root cause or a fix for this just make another issue

martinkeat commented 3 years ago

Figured it out. It was to do with the origin cert. Fixed it by changing the config.yaml config to noTLSVerify. Job done.

bolavefasfas commented 2 years ago

thanks buddy it is working for me also now i was pissed coudnt make it work for weeks and what does notlsverify actually means ? does it means that the traffic is unencrited from my server to cloudflares server ?? so someting else

GeoSnipes commented 2 years ago

Found another workaround that can work. The following assumes you are using the Nginx Package Manager container to accomplish reverse proxying: https://docs.ibracorp.io/cloudflare-tunnel/#certificate-not-valid-for-any-names

This allow you to maintain security when using origin certificate validation

darshanv237 commented 1 year ago

Even I am facing the issue, i also notlsverify and set it true but still facing the issue

darshanv237 commented 1 year ago

2023-06-28T05:39:41Z 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.29.254:443: connect: connection refused" connIndex=0 dest=https://ssh.titancloud.cloud/ event=0 ip=198.41.200.23 type=ws

I am geeting this error