-
Notifications
You must be signed in to change notification settings - Fork 14
[Help/Bug?] Getting Bouncer Disabled Error #16
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
Comments
Reinstalling the docker container I'm now getting a bit more info, but not sure how to correct it:
|
I use NPM and Crowdsec together in the same stack, each in a docker container. Initially, I configured against version v24.07.1, and everything worked perfectly. Then I updated to version v24.12.1, the latest, and got exactly the same message / error as you did first.
I then entered the container running NPM
and looked at the config from which the message came.
Okay, apparently "Bouncer Disabled" doesn't necessarily have to be the result of an error, but ... I then looked at the bouncer-config again. In the location the config from just now references exactly to
and looked at the lines carefully. For me, the entire configuration was repeated. First my old one including my API-Key and the Crowdsec URL and so on, then a new one, almost empty with default values - and it looked like this
The file is interpreted from top to bottom and keys / values will be overwritten after occurence, apparently.
Everything is as it should be again. Maybe it's the same for you and that's it :) |
Interesting, thanks for pointing this out ... this was likely the issue. I had removed the image and config files and switched to a vanilla NPM instance. Switching back after your comment it's now working ... I don't have a copy of that old config, but it's working now! Appreciate the response on this. |
How did you get the config to persist? Every time I restart the container it appends that new config. Tried changing to read only, but the startup sequence changes the permissions of the file so that didn't work. |
referenced in the volumes section of the compose file does not work?
for me it persists BUT: while trouble shooting I changed the content of the file while being inside of the running container ... don't know if that makes a difference ... enter the running container and edit |
My volumes were configured differently and that wouldn't work for me. I had to do the following after
And then manually modify the startup script to not append that config. Changed this:
To this:
And then everything worked again after restarting. |
I can also report of encountering this bug. Took me a while to identify it. |
Current Behavior
I'm looking for help getting this error corrected. I believe I have the crowdsec-openresty-bouncer.conf setup correctly.
nginx: [alert] [lua] crowdsec_openresty.conf:5):9: [Crowdsec] Bouncer Disabled
I believe I have the rest of the crowdsec processing NPM logs correctly.
I can ping CROWDSECIP from the NPM container as well.
The crowdsec bouncer hasn't seen NPM trying to connect yet:
Expected Behavior
No response
Steps To Reproduce
No response
Environment
Container creation
Unraid template
Container log
Container inspect
Anything else?
No response
The text was updated successfully, but these errors were encountered: