-
Notifications
You must be signed in to change notification settings - Fork 292
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
Boundary tries to connect to 127.0.0.1:9201 even when -cluster-listen-address is set #727
Comments
Thanks @tcassaert - I was able to repro this and will work on getting a fix in soon! |
@tcassaert We fixed this on #705 and I've added a changelog update to reflect it: #730 Feel free to build and test from |
Thanks!
I don't know if this is a known issue? |
This looks like a (hopefully temporary) issue with a downstream dep of a dep. I just ran |
Works fine, thanks! |
Describe the bug
When trying to run
boundary
in dev mode, with a differentcluster-listen-address
, boundary tries to reach127.0.0.1:9201
instead of the providedcluster-listen-address
.To Reproduce
Steps to reproduce the behavior:
boundary dev -cluster-listen-address=10.69.0.24
Expected behavior
Boundary should try to connect to the provided
cluster-listen-address
.I realize there's not much reason to change the cluster-listen-address in dev mode, but when trying the options, it was confusing to see it fail.
The text was updated successfully, but these errors were encountered: