Nicola Urbinati

Hi I have the same problem in a microk8s deploy on Ubuntu 24.04, node mk8s1, kured 1.16.0 deployed with manifests, the file was clearly present at the time of the...

Hi, anyone has the same problem and resolved?

Hi, I stumbled upon the same problem watching for events through a docker proxy. I'm just restarting a container: ``` 10:09:50.107 INFO whats-up-docker/watcher.docker.docker3: Listening to docker events 10:09:50.119 INFO whats-up-docker/watcher.docker.docker2:...

Hi, I had to delete and re-deploy the chart, probably due to persistent volumes? Is there a proper guide to upgrade and persistence volumes? Thank you.

Hi, thank you very much, I'm the one behind the askubuntu incarnation of the request. Another thing that's probably more technical but useful in pre-sale/documentation/FAQ: if I say, have a...

I tryed to add the trustedIPs: ``` forwardedHeadersTrustedIPs: - 10.0.0.0/8 - 172.16.0.0/12 - 192.168.0.0/16 ``` And find these errors with DEBUG enabled: ``` DEBUG: CrowdsecBouncerTraefikPlugin: 2025/09/10 17:40:23 handleRemediationServeHTTP ip:172.19.0.1 remediation:t...

Last debug: I also changed the LAPI url for a second bouncer (crowdsec-firewall-bouncer) on another host: ``` mode: iptables update_frequency: 10s log_mode: file log_dir: /var/log/ log_level: info log_compression: true log_max_size:...