2026-11-18 · 4 min · Mark Bacsko
BitNinja Linux Agent 3.17.14: WAF Pro HTTP 502 Hotfix
BitNinja Linux Agent 3.17.14 is a hotfix that stops WAF Pro from returning HTTP 502 errors on all sites after the transparent proxy fell back to DNAT mode.

BitNinja Linux Agent 3.17.14 is a hotfix release, now available on the frequent (beta) release channel. It fixes an issue in WAF Pro that could cause HTTP 502 errors on all sites of a server after the transparent proxy fell back to DNAT mode. If you run WAF Pro on the frequent channel, this update restores reliable web traffic handling and keeps your Linux server protection working without interrupting your visitors.
This post explains what was fixed, who is affected and how to get the update.
What's fixed in BitNinja Linux Agent 3.17.14
WAF Pro: no more HTTP 502 errors after a DNAT fallback
WAF Pro normally works as a transparent proxy in front of your web server, so it can inspect and filter HTTP traffic without changes to your site configuration. In some situations the transparent proxy falls back to DNAT mode instead.
In the previous version, an outdated (stale) Transparent WAF Pro configuration could be exported again after the HTTP/3 probe ran. When the proxy had fallen back to DNAT mode, this stale configuration did not match the active mode, and every site on the server could answer with HTTP 502 Bad Gateway.
Version 3.17.14 fixes this. The stale configuration is no longer re-exported after the HTTP/3 probe, so sites keep loading normally when the proxy runs in DNAT mode.
What this means for server owners and hosting providers
- No site-wide outages from this issue: visitors no longer get 502 errors on every site of the server after a DNAT fallback.
- Your web application firewall keeps protecting traffic: WAF Pro stays in front of your sites and keeps filtering malicious requests.
- Fewer support tickets: hosting providers no longer need to troubleshoot sudden, server-wide 502 errors caused by this issue.
Background: the HTTP/3 probe
In BitNinja Linux Agent 3.17.13, the WAF started enabling and advertising HTTP/3 only after a successful HTTP/3 probe, falling back to HTTP/1.1 and HTTP/2 if the probe fails. Version 3.17.14 makes sure the steps that run after this probe can no longer bring back an outdated Transparent WAF Pro configuration.
Who should update and how
BitNinja Linux Agent 3.17.14 is a hotfix on the frequent (beta) channel. We recommend it for every server on the frequent/beta channel, especially servers that use WAF Pro. If you run the stable channel, the fix will reach you once the version is promoted to stable.
For update instructions, release channels and configuration details, see the official documentation at doc.bitninja.io.
Summary of changes
| Area | Change |
|---|---|
| WAF Pro | Fixed HTTP 502 on all sites after the transparent proxy fell back to DNAT mode (stale Transparent WAF Pro config was re-exported after the HTTP/3 probe) |
FAQ
What does BitNinja Linux Agent 3.17.14 fix?
It fixes HTTP 502 errors on all sites that could happen after the WAF Pro transparent proxy fell back to DNAT mode, because a stale Transparent WAF Pro configuration was exported again after the HTTP/3 probe.
Do I need this update if I don't use WAF Pro?
This hotfix only changes WAF Pro behavior. It is most important for servers with WAF Pro enabled.
Is BitNinja Linux Agent 3.17.14 a stable release?
Not yet. It is a hotfix on the frequent (beta) channel.
Where can I read about the previous release?
See the BitNinja Linux Agent 3.17.13 release notes for the port filter, WAF3 and malware detection changes that came before this hotfix.
Keep your Linux servers protected
BitNinja combines a WAF, IP reputation filtering, brute-force and login protection, and malware detection in one agent to keep your Linux servers secure with minimal maintenance. Learn more about BitNinja server security at bitninja.com, compare plans on our pricing page, and follow the BitNinja blog for future release notes. The documentation helps you get the most out of version 3.17.14.