Chrome navigator.geolocation.getCurrentPosition() error 403 Chrome navigator.geolocation.getCurrentPosition() error 403 google-chrome google-chrome

Chrome navigator.geolocation.getCurrentPosition() error 403


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/


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


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.