The Page didnt load Google Maps correctly

[screechyboy79]

Sorry! Something went wrong. This page didn't load Google Maps correctly. See the Javascript console for technical details.

It seems to load briefly then get this error, any ideas?

[vicmora]

not sure but will take a look

[MarcelVuijst]

Hi. Same problem here.

[TylerLaBounty]

Hello, same issue as well. I really like the idea of this module compared to other traffic ones. Has anyone found a solution yet? EDIT: I messed up my API key. I'm dumb. Just as a note to others, make sure your API key is correct

[swizzlest]

Hey there -- I am having the same issue, but I double-checked my Google Maps API key, I even created a new one. Could you expand on how you "messed up" the key?

[dc331903]

I'm with Swizz... I see the map come up on restart for about 5 seconds followed by "Sorry! Something went wrong" Looks great for those 5 sec though - looking forward to getting it running.

[Keniki5]

I'm having the same issue, the map comes up but goes to JavaScript error within a second. npm start dev has a line: "You have included the Google Maps JavaScript API multiple times on this page. This may cause unexpected errors." It then shows the Key. I don't know code enough to deal with this. Any help would be appreciated.

[ghost]

Same problem here. It worked, however, when I first started it. After restarting MM this error will show up. Edit: when clicking "OK", it shows up correctly, but with a black color overlay and a watermark "for development purposes only"

[TylerLaBounty]

@chsamuelHU Same thing happened to me. I started using this module back in February and it worked fine, then I tried using it again a few days ago and I get the watermark as well. It looks like Google changed they way how they hand out API Keys which you can see here. I'm assuming this is causing the errors, but I haven't done any testing with it to verify. I think you need to set up a billing account with them now.

[ghost]

@PhenomAnimal Yea. I have done testing and I can confirm that google limits API usage to one request a day if billing is not enabled. If you open up MM in a browser and check the JS console you'll see something like: "You have exceeded your request quota for this API."

To everyone else having the same issue: Google doesn't allow more than 1 API request / key a day when using a "free" key. In order to increase this limit, one has to enable billing as described here: link. Looks like it is not going to be very free ... (unless you restart your mirror only max. once a day) Question: does the module refresh the traffic data every x minutes? If so, I wonder whether this also counts as an API request..

P.S if you click "OK" on that small dialog that pops up, remember that it will pop up again in x seconds.

[mathiaswscott]

I had the same problem. To fix it I went into my API console and enabled billing and then enabled Maps JavaScript API.

[Brando27615]

@PhenomAnimal Yea. I have done testing and I can confirm that google limits API usage to one request a day if billing is not enabled. If you open up MM in a browser and check the JS console you'll see something like: "You have exceeded your request quota for this API."

To everyone else having the same issue: Google doesn't allow more than 1 API request / key a day when using a "free" key. In order to increase this limit, one has to enable billing as described here: link. Looks like it is not going to be very free ... (unless you restart your mirror only max. once a day) Question: does the module refresh the traffic data every x minutes? If so, I wonder whether this also counts as an API request..

P.S if you click "OK" on that small dialog that pops up, remember that it will pop up again in x seconds.

That was my issue always. I linked my payment to this account and got a free 365 day trial with $300 for free. Thanks for this thread. I was beating my head against the wall.