Fixed API deployment issue for wazuh-single.yml default config #1377
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
This was referenced Aug 9, 2024
davidcr01
approved these changes
Aug 13, 2024
teddytpc1
approved these changes
Aug 13, 2024
MaartendeKruijf
force-pushed
the
bug/1350-fix-api-configuration
branch
4 times, most recently
from
a391bd7 to
2ea13ca
Compare
MaartendeKruijf
force-pushed
the
bug/1350-fix-api-configuration
branch
from
2ea13ca to
0eed28d
Compare
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.
This pull request will resolve a deployment issue for wazuh single that would prevent the api being reachable. The fix is to use the localhost ip
127.0.0.1instead of thelocalhostalias.