Further investigation found that the problem was restricted to our 3 networks (our offices in Brisbane & Sydney and the clients network) - although the problem was first reported by a member of the public.
We were able to successfully connect via a 3G connection with a roaming IP address and not have any problems on a MacBook Pro or iPad - this lead me to removing the default domains listed in the restrictions on the Simple API Access keys. Now we can apparently access the maps from anywhere without the "not a valid Google API Key" turn up. Craig On Tuesday, 8 May 2012 10:41:34 UTC+10, Craig Phillips wrote: > > We setup a Google Maps page on a client website back in March and it's > been running happily up until recently, now the account is constantly > giving the message described at the start of this thread. It's an extremely > low volume page about 200 map loads a month. Based on the API access report > Google started rejecting the app on 26 April 2012 - ie. thats when the > traffic drops to zero... > > To test it out we created the simple maps "Hello World" > example<https://developers.google.com/maps/documentation/javascript/tutorial#HelloWorld>using > the current API key (which we regenerated yesterday when the client > first reported the problem to us). That > page<http://www.bathurst.nsw.gov.au/mapshelloworld.html>exhibits exactly the > same problem all the time, so clearly theres a problem > when even the simple "Hello World" example doesn't work. > > We've been through and tried all of the "solutions" discussed here to no > avail, to get it up and running for the client we've had to revert to v2, > so help would be appreciated. > > If there's any information we can provide/do to help track down this issue > please let us know. > > Cheers > > Craig > > On Monday, 23 January 2012 10:54:26 UTC+10, Luke (Google Employee) wrote: >> >> Hi Barbs, >> >> I suggest making sure that the referrals are set correctly and that your >> expressions cover all your domains. >> >> Keys were introduced in 3.7 so that is why you do not get any warnings if >> you set your version to 3.6. >> >> -- Luke >> >> >> On Fri, Jan 20, 2012 at 2:56 PM, Barbs <[email protected]> wrote: >> >>> Hi Luke, >>> >>> Do you have any suggestions for those who have checked the API Console >>> and confirmed that it is correct however still displays this error? >>> >>> ATM the v=3.6 suggestion is the only one that works for me. If the key >>> was incorrectly setup in the console why would this fix work? I would >>> hazard a guess that the v=3.6 would have little effect if the console setup >>> was incorrect. >>> >>> >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Google Maps JavaScript API v3" group. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msg/google-maps-js-api-v3/-/UjN5Wl0FP5AJ. >>> >>> To post to this group, send email to >>> [email protected]. >>> To unsubscribe from this group, send email to >>> [email protected]. >>> For more options, visit this group at >>> http://groups.google.com/group/google-maps-js-api-v3?hl=en. >>> >> >> On Tuesday, 8 May 2012 10:41:34 UTC+10, Craig Phillips wrote: > > We setup a Google Maps page on a client website back in March and it's > been running happily up until recently, now the account is constantly > giving the message described at the start of this thread. It's an extremely > low volume page about 200 map loads a month. Based on the API access report > Google started rejecting the app on 26 April 2012 - ie. thats when the > traffic drops to zero... > > To test it out we created the simple maps "Hello World" > example<https://developers.google.com/maps/documentation/javascript/tutorial#HelloWorld>using > the current API key (which we regenerated yesterday when the client > first reported the problem to us). That > page<http://www.bathurst.nsw.gov.au/mapshelloworld.html>exhibits exactly the > same problem all the time, so clearly theres a problem > when even the simple "Hello World" example doesn't work. > > We've been through and tried all of the "solutions" discussed here to no > avail, to get it up and running for the client we've had to revert to v2, > so help would be appreciated. > > If there's any information we can provide/do to help track down this issue > please let us know. > > Cheers > > Craig > > On Monday, 23 January 2012 10:54:26 UTC+10, Luke (Google Employee) wrote: >> >> Hi Barbs, >> >> I suggest making sure that the referrals are set correctly and that your >> expressions cover all your domains. >> >> Keys were introduced in 3.7 so that is why you do not get any warnings if >> you set your version to 3.6. >> >> -- Luke >> >> >> On Fri, Jan 20, 2012 at 2:56 PM, Barbs <[email protected]> wrote: >> >>> Hi Luke, >>> >>> Do you have any suggestions for those who have checked the API Console >>> and confirmed that it is correct however still displays this error? >>> >>> ATM the v=3.6 suggestion is the only one that works for me. If the key >>> was incorrectly setup in the console why would this fix work? I would >>> hazard a guess that the v=3.6 would have little effect if the console setup >>> was incorrect. >>> >>> >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Google Maps JavaScript API v3" group. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msg/google-maps-js-api-v3/-/UjN5Wl0FP5AJ. >>> >>> To post to this group, send email to >>> [email protected]. >>> To unsubscribe from this group, send email to >>> [email protected]. >>> For more options, visit this group at >>> http://groups.google.com/group/google-maps-js-api-v3?hl=en. >>> >> >> -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-maps-js-api-v3/-/f5mdsCx5gpgJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
