NOD32 blocking WampServer

WampServer 2 had been working fine on Vista, then it suddenly stopped: the browser just hung and no local page would load. The culprit turned out to be NOD32 — its HTTP traffic scanner was intercepting requests to localhost and quietly swallowing them.

The original fix (NOD32 v3 era, 2008)

In the 2008 version of NOD32 the fix was to exclude the local server from the web filter:

• Open the NOD32 window
• Go to Advanced setup
• Navigate to Antivirus and AntiSpyware → Web Access Protection → HTTP → Web Browsers
• Uncheck the browser that WampServer was launching

Where the equivalent setting lives today

The menu layout above is long gone, but the concept persists in every current ESET product: the setting is now called Web access protection → URL address management, and the modern way to exclude a local server is to add localhost and 127.0.0.1 to the allowed address list (Setup → Computer protection → Web access protection → URL address management → Allowed addresses). Excluding the whole browser process, as the old fix did, left you browsing with no web filtering at all — the narrower exclusion is the better approach.

The same pattern applies to nearly every endpoint suite (Kaspersky, Avast, Bitdefender, Windows Firewall rules): anything that inspects HTTP will trip over local development servers, and the fix is a loopback exclusion, not disabling protection.

Worth knowing

WampServer itself is still maintained, though the official site has become unreliable to reach; the community add-on and documentation mirror keeps the project usable. But in 2026 the more common stack is Docker or native PHP + a real database, where the “antivirus eats my localhost” problem mostly disappears — the server no longer runs under a GUI installer that a web filter hooks into.

And one 2008 habit worth keeping: when a local dev server suddenly dies, check what changed — new security software first, configuration second. The answer was sitting in the system tray the whole time.