Clean reinstall beats endless retry — and the phone app skips the plugin entirely.
FanDuel Geolocation Plugin Not Working: Reinstall, Permissions and Browser Fixes

The short answer
When FanDuel's geolocation plugin won't verify you, do a clean reinstall: uninstall the Player Location Check plugin from your OS, restart the browser, and let FanDuel prompt a fresh install. Then check three things — Wi-Fi enabled (even on Ethernet desktops), browser location permission granted to fanduel.com, and no VPN/proxy running. If the plugin still fails, the FanDuel mobile app does its own geolocation without any plugin and is the fastest workaround.
In this article
On desktop browsers, FanDuel verifies you through GeoComply's Player Location Check — a small plugin that runs alongside the browser. It fails in recognizable patterns: endless "verifying" spinner, "plugin not detected" after you installed it, or an outright "location could not be confirmed." Most of those trace to a corrupted install or a permission that never got granted.
Clean reinstall first
- Uninstall the plugin properly: Windows — Settings > Apps > find "Player Location Check" or "GeoComply" > Uninstall. Mac — Applications folder > drag it to Trash.
- Restart the browser completely (all windows, not just the tab).
- Return to FanDuel in a normal window, place any wager, and let the site prompt the download again — install only through that prompt.
- When your OS asks for location permission for the plugin, allow it — declining once can leave a permanent denial in system settings.
Then the three environment checks
- Wi-Fi adapter on. The plugin triangulates from visible Wi-Fi networks because desktops have no GPS — an Ethernet-only desktop with Wi-Fi disabled can never pass.
- Browser location permission for fanduel.com set to Allow (address-bar lock icon > Site settings > Location).
- No VPN, proxy, or filtered connection — including antivirus "secure web" features and remote-desktop tools running in the background.
Still failing after a clean reinstall plus all three? The remaining causes are usually outside your control: a managed/corporate OS that blocks the plugin's system hooks, or a genuinely borderline location where Wi-Fi triangulation can't place you confidently inside the state.


