You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
CrowdSec: a rejected console enroll key stays saved #8221
Open CrowdSec > Blocklists > Community blocklist, with "Central API and signal sharing" enabled.
Type a wrong value in "Enroll key" and save. The page shows an invalid key error, as expected.
Reload the page.
Save again without changing anything.
Expected behavior
A rejected key is not saved. Saving again shows the same error.
Actual behavior
The rejected key is saved anyway. After the reload it shows in the field as if it were valid. Saving again passes without any error, because the key did not change, so it is never checked again.
The phonehome data then reports the instance as enrolled in the CrowdSec console (console_enrolled: true). It also says true when the Central API is turned off after a key was saved, although nothing can reach the console then.
Activity
stephdl commentedon Oct 9, 2026
Fix: NethServer/ns8-crowdsec#223
DavidePrincipi commentedon Oct 13, 2026
@stephdl moved to In Progress since NethServer/ns8-crowdsec#223 is open. Feel free to move it back if that's not right.
fix(enroll): never save an unchecked enroll key (#223)
stephdl commentedon Oct 13, 2026
QA for crowdsec:1.4.1-dev.1
Install or update to
ghcr.io/nethserver/crowdsec:1.4.1-dev.1.In the UI, go to CrowdSec > Blocklists > Community blocklist.
1. Wrong enroll key is not saved
2. Valid enroll key is saved
3. Other settings are kept after a rejected key
4. Phonehome facts
Run on the node (replace
crowdsec1with the module id):false.true.false.gsanchietti commentedon Oct 13, 2026
All test cases have been verified.
stephdl commentedon Oct 14, 2026
released by https://github.com/NethServer/ns8-crowdsec/releases/tag/1.4.1