Crowdsec-haproxy-bouncer
Hello, the haproxy bouncer package is not available in the repos, I installed it manually but I can't connect to my remote LAPI, and there is no systemd to start it, is that normal?
10 Replies
Important Information
This post has been marked as resolved. If this is a mistake please press the red button below or type
/unresolve© Created By WhyAydan for CrowdSec ❤️
Yes as its Lua its a runtime inside haproxy itself not a seperate service.
and did you define the crowdsec backend as the remote LAPI?
Hmmm ok and can I use the same api_key of the bouncer for several agents?
Hmmm, did you mean can I use the same api key to point a bouncer to the central LAPI? as the agents dont use API keys
if so yes, but you may find the bouncer inside the database gets renamed to <name>@<ip> for the child instances
ah that's good my test server had the right haproxy version but my demo server had an unsupported haproxy version, I use a token key to register my machines because tls is too complex for the moment to industrialize, do I have to create a cscli bouncer per machine?
You can if you want to be able to see different names and who they belong too, otherwise you can use the same key but they will be displayed with different ip addresses
ok but if I have 2 agents connected to a lapi server I must create 2 bouncers on the lapi because if I have only one when I do cscli bouncer list I only see 1 agent (the last one that is connected)
as long as your running the latest version it should create aliases, make sure you havent install an old version like the debain repository one
cscli version should be at least 1.6.9Oh Nice upgrade 🙂 its good because a hundred servers
Resolving Crowdsec-haproxy-bouncer
This has now been resolved. If you think this is a mistake please run
/unresolve