Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🐛I have changed the internal ip and the cert does not match #1185

Open
pippo73 opened this issue Feb 20, 2024 · 1 comment
Open

🐛I have changed the internal ip and the cert does not match #1185

pippo73 opened this issue Feb 20, 2024 · 1 comment
Labels
Priority: Normal Minor issue impacting one or more users Type: Bug Something isn't working

Comments

@pippo73
Copy link

pippo73 commented Feb 20, 2024

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:

  1. change the ip of a server
  2. try to use cloudflared
  3. 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

Environment and versions

  • OS: Linux
    # 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/"
  • Architecture: Intel(R) Celeron(R) N5095A @ 2.00GHz
  • 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

@pippo73 pippo73 added Priority: Normal Minor issue impacting one or more users Type: Bug Something isn't working labels Feb 20, 2024
@wslf1995
Copy link

me too! 我也是,谁有解决办法?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority: Normal Minor issue impacting one or more users Type: Bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants