docs(admin): explain relationship between bruteforcesettings and fail2ban#14909
Merged
Conversation
Admins frequently ask whether to use Nextcloud's built-in brute force protection or fail2ban, and whether both are needed. Added a new section to bruteforce_configuration.rst that explains the layer each operates on (application vs OS/network) and why they are complementary rather than mutually exclusive. Also added a missing RST reference label to the fail2ban section in harden_server.rst so it can be cross-referenced. Fixes #11425 Signed-off-by: skjnldsv <skjnldsv@protonmail.com>
Contributor
📖 Documentation Preview📄 2 changed documentation pagesLast updated: Tue, 19 May 2026 19:54:56 GMT |
provokateurin
previously requested changes
May 19, 2026
The bruteforcesettings app only provides the admin UI and exclusion settings. The actual brute force protection is implemented in Nextcloud Server core and runs regardless of whether the app is enabled. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> Signed-off-by: skjnldsv <skjnldsv@protonmail.com>
Member
Author
|
Added screenshot |
… BFP The protection is built into Nextcloud Server core and is always active. Disabling the app only removes the ability to manage brute force settings from the Web interface. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> Signed-off-by: skjnldsv <skjnldsv@protonmail.com>
skjnldsv
force-pushed
the
fix/bruteforce-vs-fail2ban-comparison
branch
from
618b442 to
6c16092
Compare
Member
Author
|
/backport to stable34 |
Member
Author
|
/backport to stable33 |
miaulalala
approved these changes
May 19, 2026
This was referenced May 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
☑️ Resolves
Summary
The documentation for Nextcloud's built-in brute force protection and for fail2ban
existed in separate pages with no cross-reference or explanation of how they relate.
Admins frequently wonder whether to use one or both.
Added a Brute force protection vs fail2ban section to
bruteforce_configuration.rstexplaining:
transparently, no OS configuration required
web server, reducing resource consumption
Also added a missing
.. _setup_fail2ban:reference label to the fail2ban section inharden_server.rstso the new cross-reference link resolves correctly.cc @FernandoMarques-Santos @paolosg
🖼️ Screenshots
✅ Checklist
codespellor similar and addressed any spelling issues