CrowdSec integrated with LAPI brain -- no decisions listed in the GUI

[mokaz]

Hi all,

I'm using CrowdSec locally and integrated it with a local "Brain" node, over the LAPI.
It works fine however, my only concern is that for some reasons, under GUI > Services > CrowdSec > Decisions -- I'm provided with a waiting wheel forever.

Though, running the given "cscli decisions list -a" through an SSH session would effectively list me all the decisions although it takes a while to display. Most probably because there are loads of data pulled somehow.. And my guess is that these entries are parsed as well "14291 duplicated entries skipped"..

It is a cosmetic issue altogether / I just perhaps wanted to poll if there are any central cleanings to be conducted to light this up? Or adjust any timeout values around the CrowdSec OPNsense plugin itself perhaps ?

Thanks,
m.

[mokaz]

Oki did a quick experiment on the CS API node:

Code Select Expand

systemctl stop crowdsec
cp /var/lib/crowdsec/data/crowdsec.db /root/crowdsec.db.bak
systemctl start crowdsec

Followed by a total prune of both alerts and decisions and I did add a manual decision to test:

Code Select Expand

cscli alerts delete -a
cscli decisions delete --all
cscli decisions add --ip x.x.x.x --duration 90d --reason manual-restore --type ban

And the unique and new decision has been instantly displayed within the OPNsense GUI.

Timeout issue somewhat?

Thanks,
m.

[Amodin]

I've seen the same timeout issue with just the regular Crowdsec setup, and with my Zoraxy plug-in (bouncer) on my reverse proxy.  The decisions didn't show and I just got the spinning wheel of death.  I think I only had to refresh the view by clicking on something else, then going back to it in the GUI.

Now if I can just get it to stop punching itself in the face....
(Meaning, it tells me to update to 1.8.2, identifies itself as being at 1.8.1_2, and telling me everything is fine, even after reinstalling it all).