Open klapvogn opened 1 year ago
It seems that @klapvogn may have removed the critical part of the error message, but I'm seeing the same problem. I've deleted and recreated the tunnel without any change in behavior.
Requests generate this error:
2023-04-11T04:01:54Z 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: remote error: tls: unrecognized name" connIndex=0 dest=https://REDACTED ip=REDACTED type=http
My configuration file has these ingress rules:
ingress:
- hostname: "*.REDACTED.com"
service: https://192.168.0.4:443
originRequest:
noTLSVerify: true
- service: http_status:404
Version 2023.4.0
Sorry about the missing info, I have the same error message as @biggator
I've tried regressing to 2023.3.1
and 2023.3.0
without any change in behavior.
I've resolved my issue and it seems that cloudflared is not at fault.
The remote error:
message seems to refer to the routed service, not cloudflared as I had assumed. In my case that is Nginx Proxy Manager (192.168.0.4). I reverted from the Nginx Proxy Manager docker image tagged latest
, which is also v23.04.1
, to v23.03.2
and this issue was resolved.
Unfortunately, regressing causes some other issues with Nginx Proxy Manager: although my existing proxy hosts are functioning, I can't login to the dashboard and the application logs are filling up with certbot errors, but that's a problem for another application.
When I woke up this morning I noticed my websites was not working. And looked in the cloudflare log and found this: