How to Manually Add Windows Firewall Rules When Binance Market Data is Blocked

If the chart keeps spinning or the order book fails to refresh after launching the Binance desktop client, it is likely that Windows Firewall is blocking the WebSocket connection. This note provides steps to diagnose the issue and add firewall allow rules. Download the client from the Binance Official Website or the Binance Official APP; for iPhone setup, see the iOS installation tutorial.

Signs of Firewall Blocking

Typical symptoms when Windows Defender Firewall blocks Binance:

• The client can log in (HTTP over port 443 is usually allowed by default).
• Charts are blank, and prices do not update.
• No data appears in the order book.
• The status bar shows "Connecting to market server" for a long time.
• Task Manager shows extremely low network traffic for the Binance process.

If your client works for HTTP parts but fails on persistent connections, it is almost certainly a firewall block on WebSockets.

How to Determine if it's the Firewall

First, rule out other possibilities:

• Open binance.com in a browser to check market data. Does it update? Yes → It's a firewall issue (browser rules and app rules are independent).
• Temporarily disable the firewall. Does the data start flowing? Yes → 100% a firewall issue.
• Still no data after disabling the firewall? → It's not the firewall; it's a network issue.

Proceed to add rules only after confirming it is a firewall issue.

Two Network Locations in Firewall

Windows Firewall categorizes network profiles by strictness:

Network Location	Default Strictness
Public Network	Strict (blocks most inbound traffic)
Private Network (Home/Work)	Relaxed (allows IPs on the same subnet)

Home Wi-Fi is typically "Private," while an office might be "Public." The same app may behave differently depending on the network you are connected to.

Adding Allow Rules

Detailed steps:

1. Open Control Panel → System and Security → Windows Defender Firewall.
2. Click Advanced settings on the left.
3. Enter the Windows Defender Firewall with Advanced Security console.
4. Select Inbound Rules → New Rule.
5. Choose Program for the Rule Type → Next.
6. Browse to the full path of Binance.exe.
7. Select Allow the connection → Next.
8. Check all three network profiles (Domain, Private, Public) → Next.
9. Name the rule "Binance" → Finish.

After adding the inbound rule, repeat the process for Outbound Rules by selecting it in step 4.

Verifying the Rules

After adding the rules:

• Restart the Binance client.
• Wait 3–5 seconds to see if charts start updating.
• Check Task Manager to see if the network traffic for the Binance process has increased.

If it still doesn't work, possible reasons include:

• Incorrect rule path (the path changed after a reinstallation).
• Third-party security software (like Norton, McAfee, or Malwarebytes) is also blocking it.
• Blocking at the router level.

Third-Party Security Software Collaboration

Common security software may also block the connection:

Software	Path to Settings
Norton	Settings → Firewall → Program Control
McAfee	Web and Email Protection → Firewall → Internet Connections for Programs
Kaspersky	Settings → Protection → Firewall
Bitdefender	Protection → Firewall → Rules

You must add Binance to the whitelist for each software individually.

Batch Adding Rules via Command Line

For IT administrators:

• Use the netsh advfirewall firewall add rule command for batch processing.
• Alternatively, use the New-NetFirewallRule cmdlet in PowerShell.
• Ideal for remote batch deployment.

Regular users should stick to the graphical interface.

Handling Rules After Uninstallation

Firewall rules are not automatically deleted when you uninstall Binance:

• Leaving them does not affect other apps.
• However, it makes the rule list longer and cluttered.
• To clean up: Find the Binance rules in the Advanced Security console → Right-click → Delete.

Blocking at the Router Level

Home or office routers might block certain IP ranges:

• Router features like "Parental Controls" or "Access Control" might be active.
• Corporate IT might block the entire IP range for binance.com.

Diagnosis: Check if you can connect using your phone's 4G/5G data. If yes → It's a router issue; if no → It's a firewall or something else.

Handling router issues often requires IT assistance as it is beyond the scope of a typical user.

Risks of Disabling the Firewall

Some users disable the firewall entirely for convenience. This is not recommended:

• Disabling it removes perimeter protection for all apps.
• Malicious traffic from the same network can enter your computer directly.
• The risk of malware infection increases.
• Windows will constantly flash "Your device is not secure" warnings.

Adding a single allow rule is much safer than disabling the entire firewall.

Special Cases in Domain-Controlled Environments

Firewall rules on company AD domain computers might be enforced by Group Policy:

• Rules added by the user might be overridden by Group Policy.
• IT departments must configure "Allow Binance" at the Domain Controller level.
• Some companies strictly forbid access to exchanges on employee computers.

In such environments, it is recommended to use a personal computer for trading rather than a corporate machine.

FAQ

Q: Is it enough to turn off the firewall for a while? A: Temporarily turning it off helps verify the issue, but for long-term use, you should add a rule rather than leaving it off.

Q: Can I name the rule something else? A: Yes, Windows supports any name. However, using "Binance" makes it easier to troubleshoot later.

Q: Do I need to add rules for all Binance processes? A: Adding the rule for the main process Binance.exe is usually sufficient. Sub-processes typically inherit permissions.

Q: Will Windows updates wipe out my rules? A: No. Rules added by the user are generally preserved across updates.

Further Reading

• Defender Warning
• Windows Uninstall Residual Cleanup
• CDN Domain List