Hello,
I have some issue with route local app via Cloudflare Tunnnel, from cloudflared logs
{"level":"error","error":"Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: EOF","cfRay":"73eae26d694f166d-WAW","ingressRule":"2","originService":"http://192.168.1.38:80","time":"2022-08-22T10:21:56Z"}
{"level":"error","ip":"198.41.200.113","connIndex":0,"error":"Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: EOF","type":"http","dest":"https://myhostname.app.com/favicon.ico","time":"2022-08-22T10:21:56Z","message":"Request failed"}
Error 502 in web browser
config.yaml
- hostname: myhostname.app.com
service: http://192.168.1.38:80
originRequest:
noTLSVerify: true
myhostname.app.com added to DNS via
cloudflared tunnel route dns -f TUNNELID myhostname.app.com
Output from local curl where cloudflared installed
[email protected]:~# curl -I --insecure http://192.168.1.38:80
HTTP/1.1 200 OK
Date: Mon, 22 Aug 2022 12:22:41 GMT
Server: Webs
X-Frame-Options: SAMEORIGIN
ETag: "0-16e-1e0"
Content-Length: 480
Content-Type: text/html
Connection: keep-alive
Keep-Alive: timeout=60, max=99
Last-Modified: Sun, 05 May 2019 05:58:22 GMT
[email protected]:~# cloudflared tunnel ingress validate
Validating rules from /etc/cloudflared/config.yml
OK
any ideas? It is a hkvision web camera dashboard
there is no difference that Cloudflare Access policy exist for this URL or not.
Few apps routed via cloudflared same way (but destination is nginx/apache) already exist on this node so it is very strange…