Changing nodename on cluster root causes failed auth #6021
-
After changing the nodename on our cluster root, all leafs and users can no longer connect to the cluster. The web interface works but that's about it. We renamed it from "001.xyz.eu" to "001.lndn.eu" and it no longer appears to function. We've restarted the service, attempted to re-authenticate and restarted leaves, nothing.
Running 6.0.1, didn't modify the config at all apart from the nodename but I can publish it. No errors or warnings when someone tries to login, only ones on the client side. Client debug:
Server debug:
Only error on the server is related to Kubernetes, this environment does not use nor have kubernetes configured on Teleport. Edit: leafs are authenticating with our root cluster, although cli (tsh) still wont work- tried clearing out ~/.tsh |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
public_addr was commented out and I didn't notice, my bad |
Beta Was this translation helpful? Give feedback.
public_addr was commented out and I didn't notice, my bad