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

Cluster redirecting to admin port #4764

Closed
andydunstall opened this issue Mar 14, 2025 · 0 comments · Fixed by #4776
Closed

Cluster redirecting to admin port #4764

andydunstall opened this issue Mar 14, 2025 · 0 comments · Fixed by #4776
Labels
bug Something isn't working

Comments

@andydunstall
Copy link
Contributor

Once a migration is finished in Dragonfly, but not yet finalized by the control plane (with cluster config), Dragonfly redirects to the internal IP and admin port, not the configured public domain and port

Such as we should redirect to eq0e9hvo2-qoixobx8a.dragonflydb.cloud:6379, but instead redirect to 10.5.34.191:9999

This means clients can't follow the redirect, both because it needs the domain not the IP (for TLS verification), and it needs the public port not the admin port

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant