Zero Trust Tunnel - Unable to reach the origin service

Zero Trust Cloudflare Tunnel
1

Hello together, I’m getting the following error, when I try to access my subdomain through Cloudflare zero trust tunnel.

Error:

ERR  error="Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: tls: first record does not look like a TLS handshake" cfRay=793f3310ceea9a24-FRA ingressRule=0 originService=https://192.168.178.54:3000

But I’m able to access the same http://192.168.178.54:3000 page locally without any issues.

When I check the status on the Cloudflare dashboard for that tunnel, it gives me a “healthy” status and for the connector the status “connected”.

Any help is really appreciated

2

It looks like you specified an HTTPS type service when it is HTTP,

originService=https://192.168.178.54:3000

“The service may be down or it may not be responding to traffic from cloudflared: tls: first record does not look like a TLS handshake”
Try changing the service type to HTTP in the Zero Trust Dashboard. You can find that setting in your Public Hostname settings.

1 Like
3

thank you for your reply.
I already did this. If I then try to access the url it only outputs a “Invalid Host header” in the browser.

4

Most likely that is from your origin, the server at 192.168.178.54:3000. What web server are you using?
It looks like Webpack gives this exact error message, javascript - I am getting an "Invalid Host header" message when connecting to webpack-dev-server remotely - Stack Overflow
Check that post if that is what you are using.

Another potential thing that might fix it is in your Public Hostname Settings, under Additional Application Settings → HTTP Settings, you could try setting the HTTP Host Header to “192.168.178.54:3000”

(Just a side note, if you are using Webpack Dev Server, it looks like it’s not really recommended to be exposed publicly. If it’s meant to be private, after you get it working, you may want to configure Cloudflare Access on it)

5

thanks, for pointing that out. I was using the dev server instead of the the prod server

6

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.