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

Allow RPC port and HTTP port to be on different IP addresses for servers #301

Closed
mtougeron opened this issue Aug 22, 2014 · 0 comments
Closed

Comments

@mtougeron
Copy link

It would be nice if the RPC port and HTTP port could be run on different addresses. By default, they both run on 127.0.0.1 but that means that the HTTP API access isn't available outside of the server. If the client_addr is changed, them all consul calls, even simple ones like consul members needs to have the RPC port passed in.

We want to be able to run HTTP on a non-local IP address (it would be a private one that is only accessible via security group rules to keep it as internal traffic only) so that we can query it from machines that are not running consul. But if we do this, we are not able to write simple scripts or run commands without first finding the server's IP address because the consul binary assumes 127.0.0.1 for RPC.

@armon armon closed this as completed in e86c5b2 Sep 2, 2014
duckhan pushed a commit to duckhan/consul that referenced this issue Oct 24, 2021
Update PodSecurityPolicy for exposeGossipPorts
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant