Re: git: 646715298a8e - main - security/crowdsec-firewall-bouncer: Update 0.0.34 => 0.0.36

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=298580

On Tue, Sep 15, 2026, 20:32 Jordan Ostrev <jordan@ostreff.info> wrote:

> Dear All,
>
> I’ve missed to include all participants in this thread, so i’m repeating
> my answer to Matthias, extending it.
>
>
> The update to 0.0.36 was tested prior to commit and is working as expected
> on my setup. Here is cscli bouncers list showing v0.0.36 actively
> connected and pulling updates from LAPI:
>
> Name              IP Address  Valid  Last API pull              Type                       Version
> firewall-bouncer  127.0.0.1   ✔️      2026-09-15T20:13:24+03:00  crowdsec-firewall-bouncer  v0.0.36-freebsd-41445554
>
>
> When the bouncer service dies or exits silently, it is almost always due
> to an API authentication failure with CrowdSec LAPI.
> Here is how you can verify and fix it step-by-step:
> 1. Check the logs
> Check /var/log/crowdsec-firewall-bouncer.log. You will likely see entries
> like this:
> level=error msg="failed to connect to LAPI, retrying in 10s: API error:
> access forbidden"
> 2. Regenerate the API Key
> Force-generate a new API key for the bouncer:
>
> cscli bouncers add firewall-bouncer
>
>
> 3. Update the configuration
> Copy the newly generated key and set it in
> /usr/local/etc/crowdsec/bouncers/crowdsec-firewall-bouncer.yaml:
>
> api_key: <NEW_GENERATED_API_KEY>
>
>
> 4. Restart the service
>
> service crowdsec_firewall restart
>
>
> Once the key is updated, the service should start normally and resume
> communication with LAPI.
> Regarding the PORT-INSTALL / DEINSTALL logic and manual service restarts
> during upgrades, I agree that should be addressed separately—let's handle
> that in a distinct issue/thread.
>
> Since it fails silently on your end, could you help check a few things to
> narrow down the issue?
>
>    1. Log files: Is there anything recorded in
>    /var/log/crowdsec-firewall-bouncer.log or messages at the moment of
>    start?
>    2. Manual run: Does running the binary directly with log_level: debug in
>    the configuration file output any panic or error before exiting?
>    3. Backend: Which firewall mode are you using in
>    crowdsec-firewall-bouncer.yaml (e.g., pf or ipfw)?
>
> Let me know what you find so we can figure out what is breaking on
> 15.0-p13.
>
> Best regards,
> Jordan
>
>
> On 15 Sep 2026, at 18:39, Matthias Fechner <idefix@fechner.net> wrote:
>
> Am 15.09.26 um 01:15 schrieb Yusuf Yaman:
>
> The branch main has been updated by nxjoseph:
>
> URL:
> https://cgit.FreeBSD.org/ports/commit/?id=646715298a8ed3a7833569f9dcccd941f4fcf90f
>
> commit 646715298a8ed3a7833569f9dcccd941f4fcf90f
> Author:     Jordan Ostreff <jordan@ostreff.info>
> AuthorDate: 2026-09-14 23:08:21 +0000
> Commit:     Yusuf Yaman <nxjoseph@FreeBSD.org>
> CommitDate: 2026-09-14 23:15:33 +0000
>
>     security/crowdsec-firewall-bouncer: Update 0.0.34 => 0.0.36
>          Changelog:
>
> https://github.com/crowdsecurity/cs-firewall-bouncer/releases/tag/v0.0.36
>          PR:             298102
>     Approved by:    Manuel Sabban <manuel@crowdsec.net> (maintainer
> timeout, 2 weeks)
>     Approved by:    osa, vvd (Mentors, implicit)
>
> it seems that this update does not work.
>
> The firewall-bouncer is not started and does not report any error message.
>
> I guess that update was never tested?
>
>
> Thanks for feedback ;)
> Matthias
>
>
>