Chrome navigator.geolocation.getCurrentPosition() error 403

Question

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??

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. — Les McCutcheon, Sep 01 '15 at 10:55
Happens for me too. I suspect that google changed somthing in their geo location policy over non secure http — Ido.Co, Sep 01 '15 at 10:56
Same probleme here...chrome error 403...safari tiemout expired http://jsfiddle.net/mhj82/38/ — Pascal Carmoni, Sep 01 '15 at 16:03
possible duplicate of [In new chrome (44.0.2403.157) geolocations doesnt works](http://stackoverflow.com/questions/32328133/in-new-chrome-44-0-2403-157-geolocations-doesnt-works) — Dan Rabinowitz, Sep 01 '15 at 18:08
The problem occurs again, Chrome Version 56.0.2924.87 (64-bit) — Sebastian, Mar 02 '17 at 07:46

score 14 · Accepted Answer · answered Sep 01 '15 at 18:39

14

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/

answered Sep 01 '15 at 18:39

Amin

371
2
11

1

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. – Dan Doyon Sep 01 '15 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) – CodeBrauer Mar 31 '16 at 15:16

Ido.Co · Answer 2 · 2015-09-01T13:29:21.740

1

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);
  })

edited Sep 01 '15 at 13:29

answered Sep 01 '15 at 11:30

Ido.Co

5,317
6
39
64

localhost is defined as secure here: [Prefer Secure Origins For Powerful New Features](https://sites.google.com/a/chromium.org/dev/Home/chromium-security/prefer-secure-origins-for-powerful-new-features) but still doesn't work too... – hooke Sep 01 '15 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. – Les McCutcheon Sep 01 '15 at 12:48
1

we’re using https and this still happens – mllm Sep 01 '15 at 12:51

score 0 · Answer 3 · answered Apr 04 '17 at 07:11

0

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.

answered Apr 04 '17 at 07:11

Carlos_E.

671
8
14

Chrome navigator.geolocation.getCurrentPosition() error 403

3 Answers3

Linked