You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I've changed the internal ip and now I have a problem with the tls certificate
To Reproduce
Steps to reproduce the behavior:
change the ip of a server
try to use cloudflared
I have the following error
Feb 20 10:22:43 pmx-mi cloudflared[850856]: 2024-02-20T09:22:43Z ERR error="Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: tls: failed to verify certificate: x509: certificate is valid for 127.0.0.1, ::1, 192.168.1.200, not 192.168.2.200" cfRay=8585afcd4f910d55-MXP event=1 ingressRule=0 originService=https://192.168.2.200:8006 Feb 20 10:22:43 pmx-mi cloudflared[850856]: 2024-02-20T09:22:43Z 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: tls: failed to verify certificate: x509: certificate is valid for 127.0.0.1, ::1, 192.168.1.200, not 192.168.2.200" connIndex=2 dest=https://pmxmilano.leomutti.casa/ event=0 ip=198.41.200.193 type=http
If it's an issue with Cloudflare Tunnel:
5. Tunnel ID : pmx-mi-01
6. cloudflared config: where to find it?
Expected behavior
the internal server accessible from internet
Version: cloudflared version 2024.2.0 (built 2024-02-08-1205 UTC)
Logs and errors
Feb 20 10:22:43 hostname cloudflared[850856]: 2024-02-20T09:22:43Z ERR error="Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: tls: failed to verify certificate: x509: certificate is valid for 127.0.0.1, ::1, 192.168.1.200, not 192.168.2.200" cfRay=8585afcd4f910d55-MXP event=1 ingressRule=0 originService=https://192.168.2.200:8006
Feb 20 10:22:43 hostname cloudflared[850856]: 2024-02-20T09:22:43Z 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: tls: failed to verify certificate: x509: certificate is valid for 127.0.0.1, ::1, 192.168.1.200, not 192.168.2.200" connIndex=2 dest=https://pmxmilano.domain.tld/ event=0 ip=198.41.200.193 type=http
Additional context
Add any other context about the problem here.
I have moved the ip of the server from 192.168.1.200 to 192.168.2.200
the problems seems related to the certificate, but I cannot understand how to change the cert
The text was updated successfully, but these errors were encountered:
Describe the bug
I've changed the internal ip and now I have a problem with the tls certificate
To Reproduce
Steps to reproduce the behavior:
Feb 20 10:22:43 pmx-mi cloudflared[850856]: 2024-02-20T09:22:43Z ERR error="Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: tls: failed to verify certificate: x509: certificate is valid for 127.0.0.1, ::1, 192.168.1.200, not 192.168.2.200" cfRay=8585afcd4f910d55-MXP event=1 ingressRule=0 originService=https://192.168.2.200:8006 Feb 20 10:22:43 pmx-mi cloudflared[850856]: 2024-02-20T09:22:43Z 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: tls: failed to verify certificate: x509: certificate is valid for 127.0.0.1, ::1, 192.168.1.200, not 192.168.2.200" connIndex=2 dest=https://pmxmilano.leomutti.casa/ event=0 ip=198.41.200.193 type=http
If it's an issue with Cloudflare Tunnel:
5. Tunnel ID : pmx-mi-01
6. cloudflared config: where to find it?
Expected behavior
the internal server accessible from internet
Environment and versions
# cat /etc/os-release PRETTY_NAME="Debian GNU/Linux 12 (bookworm)" NAME="Debian GNU/Linux" VERSION_ID="12" VERSION="12 (bookworm)" VERSION_CODENAME=bookworm ID=debian HOME_URL="https://www.debian.org/" SUPPORT_URL="https://www.debian.org/support" BUG_REPORT_URL="https://bugs.debian.org/"
Logs and errors
Additional context
Add any other context about the problem here.
I have moved the ip of the server from 192.168.1.200 to 192.168.2.200
the problems seems related to the certificate, but I cannot understand how to change the cert
The text was updated successfully, but these errors were encountered: