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

CLI - login command fails when health-checks enabled #2523

Open
qrkourier opened this issue Nov 6, 2024 · 0 comments
Open

CLI - login command fails when health-checks enabled #2523

qrkourier opened this issue Nov 6, 2024 · 0 comments

Comments

@qrkourier
Copy link
Member

Re: https://openziti.discourse.group/t/ziti-v1-1-15-fails-initial-login/3378/8?u=qrkourier

In this case there are two web listeners. One has client only, the other has mgmt, fabric, and health-checks.

Login fails with error containing health-checks response.

error: no session token returned from login request to https://ebea685ad01d442a8515a4f1329d2b8d.mgmt.zitipoc.com:8444. Received: {"data":{"checks":[{"details":null,"healthy":true,"id":"bolt.read","lastCheckDuration":"15.12µs","lastCheckTime":"2024-11-06T01:02:17Z"}],"healthy":true},"meta":{}}

Login works if:

  • roll back to 1.1.11
  • remove the health-checks binding
  • the URL path /edge/management/v1 is appended to controller address in login command

This points to a problem with routing default protocol handler requests to the correct binding introduced >1.1.11-1.1.15.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
1 participant