CrowdSec: report email link points to the wrong node and page #8252

Activity

1. stephdl

   added the

   Bug

   issue type on Oct 21, 2026
2. stephdl

   added this to the NethServer 8.11 milestone on Oct 21, 2026
3. stephdl

   added this to NethServeron Oct 21, 2026
4. github-project-automation

   moved this to ToDo in NethServeron Oct 21, 2026
5. stephdl

   moved this from ToDo to In Progress in NethServeron Oct 21, 2026
6. stephdl

   self-assigned this

   on Oct 21, 2026
7. stephdl

   added a commit that references this issue on Nov 3, 2026

   fix(notifications): point email link to leader blocklists page (#229)

   ...

   ea287ce
8. stephdl commented on Nov 3, 2026

   

   stephdl

   on Nov 3, 2026

   Author

   More actions

   QA for ghcr.io/nethserver/crowdsec:1.4.3-dev.1

   This release fixes the "View Active Decisions" link in the CrowdSec report email (#229). The link used the local node FQDN and the removed unban page. It now uses the leader hostname and the blocklists page. The rest of the release is UI dependency updates and translations.

   Setup

   Configure a cluster smarthost and set at least one receiver email in CrowdSec Settings. Update an existing instance:

   update-module crowdsec1 ghcr.io/nethserver/crowdsec:1.4.3-dev.1
   

   Test both a fresh install and an update from 1.4.2.

   Test 1: CrowdSec on the leader node

   1. Send a test notification: podman exec crowdsec1 cscli notifications test email_default
   2. Check the email. The subject and title show the local node FQDN.
   3. The "View Active Decisions" link is https://<leader FQDN>/cluster-admin/#/apps/crowdsec1?page=blocklists.
   4. Click it. The Blocklists page opens on the "Local blocklist" tab.

   Test 2: CrowdSec on a worker node

   1. Install CrowdSec on a worker node and send a test notification as above.
   2. The subject and title show the worker FQDN. This tells which node banned the IP.
   3. The link points to the leader, not to the worker. The hostname comes from the leader VPN endpoint (node/<leader_id>/vpn), so it can differ from the leader FQDN. Please report what you get and whether it opens cluster-admin.
   4. Click it. The Blocklists page opens.

   Test 3: real ban email

   Trigger a real ban, for example with a brute force on a protected service. Check that the report email arrives and that the link works.

   Regression

   Open every CrowdSec page (Status, Settings, Detections, Collections, Blocklists, Threat Shield, About). Check that they load without console errors and that icons render. Axios, Carbon icons, sass and core-js were updated.

   Known limitation

   The link is computed at service start. After a leader switch, it points to the old leader until the module restarts (systemctl restart crowdsec1). This is intended and documented in the README (#240).
9. stephdl

   moved this from In Progress to Testing in NethServeron Nov 3, 2026
10. stephdl

    added

    testingPackages are available from testing repositoriesPackages are available from testing repositories

    on Nov 3, 2026
11. stephdl

    removed their assignment

    on Nov 3, 2026