Coralesoft
commented
1 month ago Found another user with the same issue
dani1 6 Jun I have a Cloudflare tunnel with a public hostname pointing to an internal resource with a self-signed certificate. The origin configuration has “No TLS Verify” enabled.
It does not work with the latest cloudflared (2024.6 windows_amd64). However, it works with the previous version (2023.8.2 windows_amd64) as expected.
Logs with 2024.6 show this error, which should be ignored due to the “No TLS Verify” setting but is not:
{ “connIndex”: 2, “originService”: “https://localhost:4105/”, “ingressRule”: 1, “error”: “Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: remote error: tls: handshake failure” }
dberwig
Describe the bug Since upgrading to 2024.6.1 I cannot access my servers, i revert back to 2023.10.0 and everything works as it always shad
with 2024.6.1, I now get JSON { "ingressRule": 0, "error": "Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: remote error: tls: handshake failure", "connIndex": 3, "originService": "https://localhost:10000" } this has always worked in the past I have downgraded to an earlier version of cloudflared, I believe this is to do with the noTLSVerify: flag
*Path Service https://localhost:10000 Origin configurations tlsTimeout: 10 noTLSVerify: disableChunkedEncoding: **
Environment and versions