Configure additional rabbitmq listeners
#676
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The rabbit server will listen for in-cluster communication and
local administration on a port calculated as:
`${cfg.port} + 20000`
This configures that port to use the same listener address as the
configuration option.
`epmd` is a companion process that is used to look up domain names
by `rabbitmq-server` and this also configures that process to listen
on the same listener address.
thenonameguy
approved these changes
Jun 21, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The rabbit server will listen for in-cluster communication and local administration on a port calculated as:
${cfg.port} + 20000This configures that port to use the same listener address as the configuration option.
epmdis a companion process that is used to look up domain names byrabbitmq-serverand this also configures that process to listen on the same listener address.Without this change, the
rabbitmq-serveris available on all possible interfaces with default credentials. This will expose the server to security risks and compromise unless further configuration is made. To test this, I have configured a rabbitmq to only listen on127.0.0.1and I can verify that it is not listening on only a single interface withrabbitmqctl cluster_statusandlsof -nP -i | grep beam(on a mac).