Can you please provide the hostnames that you put into the API Console, and 
also the full URL of the page that's accessing the API?

On Wednesday, March 6, 2013 6:14:48 AM UTC+11, Brandon Chambers wrote:
>
> Is there any official word on this?
>
> It seems people are having trouble all over the map with this thing.
>
> I tried entering a whole set of hostnames with and without wildcards. None 
> worked. I still get the "access not configured" error even with a basic 
> curl -i call.
>
> What's with this??? I'd be happy to share more specific details if Google 
> is willing to support their API.
>
> On Tuesday, November 6, 2012 1:30:37 AM UTC-8, Guillaume Chata-Simoni 
> wrote:
>>
>> Hi all,
>>
>> Also got this issue, 3-4 times in two weeks...
>>
>> I've entered referrers with *, without *...
>>
>> tag-all.com/* *.tag-all.com/* m.tag-all.com/ 
>>> dev.tag-all.com:28880/build/TagAll/production/* 
>>> *.tag-all.com:28880/build/TagAll/production/* 
>>> dev.tag-all.com:28880/TagAll/tagall/applications/mobile/* 
>>> *.tag-all.com:28880/TagAll/tagall/applications/mobile/*<http://tag-all.com/**.tag-all.com/*m.tag-all.com/dev.tag-all.com:28880/build/TagAll/production/**.tag-all.com:28880/build/TagAll/production/*dev.tag-all.com:28880/TagAll/tagall/applications/mobile/**.tag-all.com:28880/TagAll/tagall/applications/mobile/*>
>>>
>>
>> Thing is : 
>>
>> - application is working fine one my Desktop iMac (using Chrome), but 
>> doesn't on my colleague iMac (same network).
>> - application doesn't works since yesterday (at night - France) when 
>> connected from devices (iPhone and Android), even at home and even at 
>> office (not the same Wifi).
>>
>> This issue seems to be "chaotic", and, *i ask help, since we got an 
>> official opening of our application today !*
>>
>> Thanks for response
>>
>>
>> Le vendredi 29 juin 2012 17:51:44 UTC+2, Danny Pryor a écrit :
>>>
>>> We just made a modification on our permitted sites, in the API console, 
>>> to include domains with the starting asterisk AND without. The prefix 
>>> asterisk would work with the "www" appended at the beginning of a domain, 
>>> but not without the "www"; the moment we added the second condition, the 
>>> API worked just fine. So for each site, we are now setting up the permitted 
>>> referrers as follows:
>>>
>>> *.example.com/* and example.com/*
>>>
>>> This is the arrangement that seems to cover the most bases, for now.
>>>
>>> :)
>>>
>>> On Wednesday, June 13, 2012 7:09:49 AM UTC-4, sw45859 wrote:
>>>>
>>>> Figured i would let you know what worked just now for me.
>>>>
>>>> i had my referrer set up for a client as:
>>>> *.clientDomain.com/*
>>>>
>>>> and i was getting the errors, now that i just reset it to:
>>>> clientDomain.com/*  - without the beginning *.
>>>>
>>>> i guess googles rule parser is having an issue with the documented *. 
>>>> for the subdomain wildcard
>>>> it just loaded fine, hope this helps.
>>>>
>>>>
>>>> On Monday, January 9, 2012 3:43:24 AM UTC-6, Jack W-H wrote:
>>>>>
>>>>> Hi Googlers, 
>>>>>
>>>>> This morning I noticed on my site the following message in the Chrome 
>>>>> Javascript Console: 
>>>>>
>>>>> "The key provided is not a valid Google API Key or it is not 
>>>>> authorised for the Google Maps JavaScript API v3 on this site. If you 
>>>>> are the owner of this application, you can learn about obtaining a 
>>>>> valid key here: 
>>>>> http://code.google.com/apis/maps/documentation/javascript/tutorial.html#Obtaining_Key";
>>>>>  
>>>>>
>>>>>
>>>>> Here is a screenshot of my API Access console to confirm this is 
>>>>> correct: http://i.imgur.com/sVq69.png (I have blurred out the 
>>>>> personal 
>>>>> details). I would provide a link to test and debug - but I can't. This 
>>>>> is for a private client who would rather I did not share it at the 
>>>>> moment whilst the site is still in development. 
>>>>>
>>>>> I can show you that this is how I'm loading the snippet, blanking out 
>>>>> the last part of my key: 
>>>>>
>>>>> <script src="https://maps.googleapis.com/maps/api/js? 
>>>>> key=AIzaSyD_On9NiqOTjMdRZvgWXXXXXXXXXXXXXXX&sensor=false<https://maps.googleapis.com/maps/api/js?key=AIzaSyD_On9NiqOTjMdRZvgWXXXXXXXXXXXXXXX&sensor=false>"></script>
>>>>>  
>>>>>
>>>>>
>>>>> I'm using the V3 API. I was not noticing this the other day, but maps 
>>>>> still seem to be being displayed. Also, I am seeing all the requests 
>>>>> count up in the API Console, implying it does seem to be able to 
>>>>> connect. Any advice? 
>>>>>
>>>>> Thanks! 
>>>>>
>>>>> Jack
>>>>
>>>>

-- 
You received this message because you are subscribed to the Google Groups 
"Google Maps JavaScript API v3" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-maps-js-api-v3+unsubscr...@googlegroups.com.
To post to this group, send email to google-maps-js-api-v3@googlegroups.com.
Visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to