← Blog

Location not available? How to fix GPS and browser location errors

· 6 min read

"Location not available." "Permission denied." "Your location could not be determined." These errors appear at the most inconvenient moments — when you actually need to know where you are. The frustrating part is that the cause is rarely obvious from the error message alone. Here's a systematic guide to diagnosing and fixing location errors across every major browser and platform.

The three root causes of location errors

Almost every location error falls into one of three categories:

  1. Permission denied — the browser or operating system has blocked this site from accessing your location, either because you said "Block" at some point, or because a system setting is preventing it.
  2. Hardware unavailable — GPS has no satellite fix, or the device doesn't have GPS at all.
  3. Timeout — the location request started but the device couldn't get a fix within the allowed time window.

Each has a different fix. Knowing which one you're hitting is step one.

Fix: permission denied in Chrome (desktop and Android)

If you previously clicked "Block" for a site, Chrome remembers that decision and won't prompt you again.

  • Desktop: Click the lock icon (or info icon) in the address bar → select Site settings → find Location → change from Block to Allow. Reload the page and try again.
  • Android Chrome: Tap the three-dot menu → Settings → Site settings → Location → find the site in the blocked list → tap it → change to Allow.
  • Alternatively, go to Chrome settings → Privacy and security → Site settings → Location and look for the site under "Not allowed."

Fix: permission denied in Safari (macOS and iOS)

Safari handles location permissions at both the browser and OS level, which is why it can be trickier to fix.

  • macOS: Safari menu → Settings → Websites → Location → find the site and change it to Allow or Ask. Also check: System Settings → Privacy & Security → Location Services → Safari → set to "While Using."
  • iOS: Settings → Privacy & Security → Location Services → Safari Websites → change to While Using the App. Then in Safari, you may also need to: tap the AA button in the address bar → Website Settings → Location → Allow.

Fix: permission denied in Firefox

  • Click the lock icon in the address bar → Connection secure → clear the Location permission (click the × next to it). Reload and you'll be prompted again.
  • Or go to about:permissions in the address bar → find the site → set Location to Allow.

Fix: OS-level location services disabled

Even with browser permissions granted, location won't work if location services are turned off at the operating system level.

  • Windows: Settings → Privacy & security → Location → turn on Location services and also turn on access for your browser app specifically.
  • macOS: System Settings → Privacy & Security → Location Services → enable it and ensure your browser is checked.
  • Android: Pull down the notification shade → tap the Location quick-tile to enable it. Or Settings → Location → turn on.
  • iOS: Settings → Privacy & Security → Location Services → make sure the master toggle is on.

Fix: GPS has no fix (hardware unavailable or timeout)

If you get a "position unavailable" error rather than a "permission denied" error, the device obtained permission but couldn't get a GPS fix.

  • Go outdoors or near a window. GPS satellites require a reasonably clear line of sight. Dense buildings, basements, and parking garages block signals. Even near a window you'll often get a fix within 30–60 seconds.
  • On Android: make sure High accuracy mode is enabled (Settings → Location → Mode → High accuracy). This uses GPS + Wi-Fi + cell for the fastest, most accurate fix.
  • Wait longer. If a device hasn't used GPS recently, it needs a "cold start" to download fresh satellite data — this can take up to 90 seconds on first use or after a long gap.
  • Check airplane mode. GPS itself works without internet, but assisted GPS (A-GPS) uses a network connection to speed up the initial fix. Airplane mode without Wi-Fi can slow down the first fix significantly.

Fix: location is available but inaccurate

Sometimes location works but the position shown is clearly wrong — a few kilometers off, or in the wrong city entirely.

  • IP fallback: If GPS failed silently and the browser fell back to IP geolocation, the position can be the city your ISP routes through, not where you are. Reload and try the location request again.
  • VPN: If you're using a VPN, your IP-derived location will be the VPN server's location. Disable the VPN or use precise GPS mode which bypasses IP entirely.
  • Cached position: Browsers sometimes return a cached position that's hours old. Try a hard reload (Ctrl+Shift+R / Cmd+Shift+R) to force a fresh fix.

Does the site need to be on HTTPS?

Yes — this is a browser security requirement, not something we control. The Geolocation API is only available on secure origins (HTTPS or localhost). If you're visiting a site over plain HTTP, location will be blocked by the browser regardless of your permission settings. My Location is served over HTTPS, so this doesn't affect it — but if you're testing on a local development server, you'll need localhost (not your LAN IP) for location to work.

Still stuck?

If you've worked through the steps above and location still fails, the quickest diagnostic is to check whether any site can access your location: open Google Maps or maps.google.com and tap "find my location." If that also fails, it's almost certainly an OS-level setting. If Google Maps works but another site doesn't, it's a site-specific permission issue. Once your location is working, open My Location to see your coordinates, address, and a live map view.