Network Errors

Updated June 2025

Network errors occur when your browser or wallet cannot communicate with the BNB Smart Chain (BSC). This guide walks you through every common cause and how to resolve it.

1. Wrong Network Selected in MetaMask

The most frequent cause of network errors is having the wrong network active in MetaMask. OddsForge operates exclusively on BNB Smart Chain Mainnet (Chain ID 56).

How to switch to BSC Mainnet

  1. Open the MetaMask extension in your browser.
  2. Click the network selector dropdown at the top of the MetaMask window.
  3. If BNB Smart Chain (or BSC Mainnet) is listed, select it.
  4. If it is not listed, click Add Network and enter the following details:
    • Network Name: BNB Smart Chain
    • New RPC URL: https://bsc-dataseed.binance.org/
    • Chain ID: 56
    • Currency Symbol: BNB
    • Block Explorer URL: https://bscscan.com
  5. Click Save, then select BNB Smart Chain from the network list.
  6. Refresh OddsForge and try your action again.
Tip: OddsForge will automatically prompt you to switch networks when it detects the wrong chain. Accept the prompt in MetaMask to switch instantly.

2. BSC RPC Endpoint Issues

Sometimes the default RPC endpoint becomes congested or temporarily unavailable. If you see errors like "Could not fetch chain ID" or "RPC request failed", try switching to an alternative endpoint.

How to change your RPC endpoint

  1. Open MetaMask and go to Settings → Networks → BNB Smart Chain.
  2. Replace the current RPC URL with one of these alternatives:
    • https://bsc-dataseed1.defibit.io/
    • https://bsc-dataseed1.ninicoin.io/
    • https://bsc-dataseed2.binance.org/
    • https://bsc.publicnode.com
  3. Click Save.
  4. Reload OddsForge and retry.
Warning: Only use trusted, well-known RPC endpoints. Never enter an RPC URL from an unverified source — malicious endpoints can expose your transaction data.

3. Browser Cache & Stale Data

Outdated cached data can cause OddsForge to send requests to the wrong contract address or use stale configuration.

How to clear your cache

  1. Open your browser settings (e.g., Chrome → Settings → Privacy and Security → Clear Browsing Data).
  2. Select Cached images and files. You can leave cookies and browsing history unchecked.
  3. Set the time range to Last 24 hours (or All time if the issue persists).
  4. Click Clear data.
  5. Close and reopen your browser, then navigate back to oddsforge.org.
Tip: You can also try opening OddsForge in a private/incognito window to quickly rule out cache-related issues.

4. BSC Network Status

Occasionally the BNB Smart Chain itself may experience congestion, degraded performance, or an outage. Before extensive troubleshooting, check whether the network is healthy.

How to check BSC network status

  1. Visit BscScan.com and check whether new blocks are being produced.
  2. Look at the Last Block timestamp — it should be within the last few seconds.
  3. Check the BNB Chain Twitter/X account for any announced maintenance or incidents.

If the network is experiencing issues, wait for it to stabilise before retrying your transaction.

5. Firewall, VPN & DNS Issues

Corporate firewalls, strict VPN configurations, or DNS filtering can block the WebSocket and HTTPS connections that OddsForge and MetaMask require.

Steps to diagnose

  1. Disable your VPN temporarily and reload OddsForge. If the error disappears, your VPN is blocking BSC traffic.
  2. Switch DNS providers — try using 1.1.1.1 (Cloudflare) or 8.8.8.8 (Google) to rule out DNS-level blocking.
  3. Check firewall rules — ensure outbound HTTPS (port 443) traffic to bsc-dataseed.binance.org and oddsforge.org is allowed.
  4. If you are on a corporate or school network, contact your network administrator to whitelist the required domains.
Warning: If you disable your VPN for testing, avoid sharing sensitive personal information until you re-enable it. Wallet interactions on BSC are public by nature, but your browsing activity may not be protected without a VPN.

6. MetaMask or Browser Extension Conflicts

Other browser extensions — especially ad blockers, privacy tools, or competing wallet extensions — can interfere with MetaMask's ability to communicate with BSC.

  1. Temporarily disable all browser extensions except MetaMask.
  2. Reload OddsForge and try again.
  3. If the issue resolves, re-enable extensions one by one to identify the conflict.

Troubleshooting Checklist

Work through the following checklist in order. Most network errors are resolved within the first three steps.

  1. Verify your network: Confirm MetaMask is connected to BNB Smart Chain Mainnet (Chain ID 56).
  2. Refresh the page: Press Ctrl+Shift+R (or Cmd+Shift+R on Mac) for a hard refresh.
  3. Switch RPC endpoint: Use an alternative BSC RPC URL in MetaMask settings.
  4. Clear browser cache: Remove cached files and reload.
  5. Check BSC status: Visit BscScan to confirm the network is operational.
  6. Disable VPN/firewall: Temporarily disable and retry.
  7. Disable other extensions: Rule out extension conflicts.
  8. Try another browser: Test in Chrome, Firefox, or Brave to isolate browser-specific issues.
  9. Update MetaMask: Ensure you are running the latest version of the MetaMask extension.
  10. Contact support: If none of the above resolves the issue, reach out to OddsForge support with details of the error message and the steps you have already tried.

Did this answer your question?