I am unable to trace what the problem is with the certificate & connection. I have trawled the forum without find what my problem is.
I have created new PEM/ Key Certificates but still receiving many of these message i the logs.
Any guidance would be appreciated.
Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: x509: certificate is not valid for any names, but wanted to match mtamo.co.uk" cfRay=787XXXXXXXXX-PRG originService=https://192.168.0.18:19443
You need to check your certificate. It doesn’t appear to be correctly configured to supply names.
Thanks i created a new certificate and results are now,
023-01-11T22:52:54Z INF Generated Connector ID: 51d1eaf3-462e-49d7-98bb-b0c33ca9aab3 2023-01-11T22:52:54Z INF Initial protocol quic 2023-01-11T22:52:54Z INF ICMP proxy will use 172.19.0.6 as source for IPv4 2023-01-11T22:52:54Z INF ICMP proxy will use :: as source for IPv6 2023-01-11T22:52:54Z INF Starting metrics server on 127.0.0.1:40931/metrics 2023-01-11T22:52:55Z INF Connection a2a24077-47a3-4edb-8e75-def2db1b1262 registered with protocol: quic connIndex=0 ip=188.8.131.52 location=LHR 2023-01-11T22:52:55Z INF Connection 3d5601ff-24d6-424c-a87c-251704cd04c6 registered with protocol: quic connIndex=1 ip=184.108.40.206 location=MAN 2023-01-11T22:52:57Z INF Connection 0bc4a634-f628-467b-9795-48f4fab6d6c1 registered with protocol: quic connIndex=2 ip=220.127.116.11 location=LHR 2023-01-11T22:52:58Z INF Connection a37e1300-df7e-41a3-a4dc-65e93fbcae52 registered with protocol: quic connIndex=3 ip=18.104.22.168 location=MAN 2023-01-12T00:39:34Z 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=7881XXXXXXX-LHR originService=https://192.XXX.X.X:19443 2023-01-12T00:39:34Z 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: EOF" connIndex=0 dest=https://mtamo.co.uk/auth/token ip=22.214.171.124 type=http text
It seems to be a NGINX problem now… My A/CName records NGINX seem OK one at point in the past it worked ??. Question : Could i create a tunnel for NGNIX ?
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.