After migrating several websites to HestiaCP, I was seeing plenty of unnecessary traffic: requests for exposed credentials, nonexistent PHP files, aggressive crawlers and repeated WordPress login attempts.
So I put together the De-Noise to manage this centrally through the Hestia panel, filtering requests in Nginx before they reach Varnish, Apache or PHP.
Some of its features:
Separate, editable scanner-tool and crawler blocklists.
Protection against known private file and credential probes.
Optional login, xml-rpc and filtered URL rate limits.
Optional automatic IP bans through Hestia’s firewall, plus domain only bans.
Ban explanations showing the requests that triggered them.
WordPress user enumeration protection and Fail2ban login controls.
Extra HTTP password for WordPress administration
Country filtering using a local GeoLite2 database.
Central access defaults with account and domain overrides.
Log analysis and Activity reports with site filters and full User agent details.
Existing proxy templates remain. Each domain supports Off, Observe and Enforce modes.
This is an independent, open-source project, currently preview version 0.16.0, targeting Ubuntu with Hestia’s Nginx proxy setup. It is a request-filtering addon, not a full WAF.
Feedback would be especially useful around false positives, custom templates and legitimate WordPress/WooCommerce workflows. If you try it and you have an issue, please include your setup and the specific rule involved when reporting an issue.
Suggestions are also more than welcome.
The current release has been tested on Ubuntu 26, and the installer currently only accepts Ubuntu.
Deleting from /usr/local/src/hestia-de-noise/tools/install.py these lines:
os_release = Path(‘/etc/os-release’).read_text()
if not any(line in os_release.splitlines() for line in (‘ID=ubuntu’, ‘ID=“ubuntu”’)):
raise ValueError(‘This release targets Ubuntu with HestiaCP’)
you should be able to install it on debian but I cannot know if it will work or even if it will break your sytem or not
The general features work at the Nginx level and can protect PHP applications, static HTML sites and other websites: bot filtering, private file protection, rate limits, optional IP bans, country filtering and log analysis.
The Wordpress specific features such as user enumeration protection, failed login integration and WordPress cron management are optional. You don’t need Wordpress to use the general filtering features.
Like User-Agent lists to block, it will be useful if we have custom (regex enabled)list of endpoints to block.
For example, i often see bad scan bots looking for bak.sql.gz, bak.sql.zip, bak.sql.zst etc. If have the above feature, we can block and eliminate much noise using a regex.
nice, thank you for the list. Now denoise suggest these into their category. Added a list for major and various search engine bots since its not easy to distinguish what some may want or not.