It sounds like you're having trouble capturing traffic from Bloons TD 1 with Fiddler Everywhere. Here are a few things you might want to check:
Proxy Settings: Ensure that Fiddler is set as your system's proxy. Sometimes, games may bypass the default proxy settings.
HTTPS Decryption: Ensure that HTTPS decryption is enabled in Fiddler, as many games utilize HTTPS for communication.
Game Launching: Try launching the game after starting Fiddler. Some applications may not send traffic until they are opened while the proxy is active.
Firewall/Antivirus: Verify that your firewall or antivirus is not blocking Fiddler from capturing traffic.
Hopefully, one of these solutions helps you capture the traffic successfully!
2 Answers, 1 is accepted
0
Nick Iliev
Telerik team
answered on 27 Feb 2024, 07:55 AM
Hello Radajsa,
From what I can gather, the game seems to be using a Flash player in many of the locations where it is published. The Flash player should comply with the system proxy settings, but it is unclear how or what HTTPS requests are managed behind the scenes, as the source code is not available, and no information has been provided regarding the capturing endpoint.
answered on 18 Dec 2025, 05:19 PM
| edited on 12 Jan 2026, 06:31 PM
looks like with bloons td 1 you’re running into the issue that the flash runtime or the wrapper itself doesn’t send requests through the system proxy, so there’s just nothing for fiddler to catch. I’ve seen something similar myself: when launching an old flash game, there’s zero traffic in fiddler, but in the browser I’d get a popup ad redirect to https://cricketbettingapps.org/ , which just made things more confusing. try checking network activity at the socket level in parallel (wireshark/etw) to see if there’s any http/https at all. if it’s empty there too, then it’s not a fiddler problem, it’s just that the game doesn’t have any proxyable web traffic.
It sounds like you're having trouble capturing traffic from Bloons TD 1 with Fiddler Everywhere. Here are a few things you might want to check:
Proxy Settings: Ensure that Fiddler is set as your system's proxy. Sometimes, games may bypass the default proxy settings.
HTTPS Decryption: Ensure that HTTPS decryption is enabled in Fiddler, as many games utilize HTTPS for communication.
Game Launching: Try launching the game after starting Fiddler. Some applications may not send traffic until they are opened while the proxy is active.
Firewall/Antivirus: Verify that your firewall or antivirus is not blocking Fiddler from capturing traffic.
Hopefully, one of these solutions helps you capture the traffic successfully!