Chrome navigator.geolocation.getCurrentPosition() error 403

Asked 1/9, 2015 at 10:36 Answered 4/4, 2017 at 7:11

Solved google-maps google-chrome navigator google-geolocation

For some reason suddenly when calling navigator.geolocation.getCurrentPosition() I get this error:

Network location provider at 'https://www.googleapis.com/' : Returned error code 403.

It used to work perfectly yesterday! Could there be anything with their servers??

Serdab answered 1/9, 2015 at 10:36 Comment(8)

I am experiencing the same problems in Chrome and Firefox but seems to work find in IE. Tried it on a colleague machine and getting the same results. – Nunley 1/9, 2015 at 10:55

Happens for me too. I suspect that google changed somthing in their geo location policy over non secure http – Initial 1/9, 2015 at 10:56

Same problem here. Everything ok yesterday Aug 31 2015. – Kanara 1/9, 2015 at 12:7

thank god it is not just me – Banff 1/9, 2015 at 14:34

Same probleme here...chrome error 403...safari tiemout expired jsfiddle.net/mhj82/38 – Customable 1/9, 2015 at 16:3

possible duplicate of In new chrome (44.0.2403.157) geolocations doesnt works – Lebna 1/9, 2015 at 18:8

Looks like it was solved at googleapis.com – Customable 2/9, 2015 at 0:13

The problem occurs again, Chrome Version 56.0.2924.87 (64-bit) – Comment 2/3, 2017 at 7:46

It appears it is back up now. But before I realized it was working, I used another way to get location data as recommended by another user on reddit.com

var latLong;
$.getJSON("http://ipinfo.io", function(ipinfo){
    console.log("Found location ["+ipinfo.loc+"] by ipinfo.io");
    latLong = ipinfo.loc.split(",");
});

Source: https://www.reddit.com/r/webdev/comments/3j8ipj/anyone_else_had_issues_with_the_html5_geolocation/

Actable answered 1/9, 2015 at 18:39 Comment(2)

This appears to be unreliable, I'm showing up in richardson texas, which is news to me, since I'm in SF. Sorry for being snarky. – Beckham 1/9, 2015 at 19:42

This just looks up the current IP in big geoIP tables - specially on mobile devices this is not the best way (GSM IP's are Pool-IPs, and GPS is much more accurate) – Holdback 31/3, 2016 at 15:16

This happens for me too on idoco.github.io/map-chat

I suspect that this is related the the changes google planed for Deprecating Powerful Features on Insecure Origins it seems that some changes were done in the last few days in this chromium Issue 520765: Deprecation and removal of powerful features on insecure origins

Can you test your site over https to confirm that?

In the meanwhile I found this api usage as a workaround on this repo:

  $.getJSON("http://ipinfo.io", function(doc){
    var latlong = doc.loc.split(",")
    setUserLocation(parseFloat(latlong[0]), parseFloat(latlong[1]));
    getLocation(parseFloat(latlong[0]), parseFloat(latlong[1])).then(function(res){
      userLocationName = res
    })
    initialiseEventBus();
    map.panTo(userLocation);

  }, function(err) {
    setUserLocation(Math.random()*50, Math.random()*60);
    userLocationName = "unknown.na"
    initialiseEventBus();
    map.panTo(userLocation);
  })

Initial answered 1/9, 2015 at 11:30 Comment(3)

localhost is defined as secure here: Prefer Secure Origins For Powerful New Features but still doesn't work too... – Director 1/9, 2015 at 12:22

Tried both Http:// and Https:// on internal and external sites with no change in results (Fails in Chrome/FF works in IE. Tried it in fiddler with a standard http:// head and it worked. – Nunley 1/9, 2015 at 12:48

we’re using https and this still happens – Serdab 1/9, 2015 at 12:51

I had the same issue, you have to check your developer dashboard and make sure that your API key has no usage restrictions or warnings.

Symmetrize answered 4/4, 2017 at 7:11 Comment(0)

Recommended topics

Hot tags