Invalid response, more details in JavaScript Console (F12)

Most probably because the requests are timing out, you could also check the PHP error log for clues or ask your hosting provider to check that for you.

Thanks, I did check the PHP error log, nothing in there.
Here is the response from my service provider:
The error indicates that the message received from a request was not valid json/javascript. In this case, you will need to isolate specifically which request this is hitting to generate the response….If this is coming from a third party host, your php and server logs won’t have any details to provide.
I don’t think this is an issue on my end.I’m on apache2 ubuntu 14.04

When you’re receiving that error press F12 (Chrome, Firefox or IE) and post the error log you have in Console tab. Will go from there, maybe we’ll spot something.

Here is how the error looks like:

https://drive.google.com/file/d/0B1z-Wlca87CoWWtvQXg0ay12NUU/view?usp=sharing

and screenshot when I press F12

https://drive.google.com/file/d/0B1z-Wlca87CodHZ2TmROUzZIeDg/view?usp=sharing

Thanks for looking into this.

Marek

After pressing F12 there is a Console tab, click it and than make the screenshot.

Here you go:

https://drive.google.com/file/d/0B1z-Wlca87CoeUZjVTRhSHQya1E/view?usp=sharing

Hi, I am getting exactly the same error after the update.

Cheers

It appears that the plugin stopped working, I’m getting “This report is unavailable (-23)” all across the board.

That’s a daily limit exceed it will be automatically reseted at the midnight PST, most probably you’ve reached that limit because of the error you have.

No sure how the daily limit works and what they are but I wasn’t logged in to my website since 8 PM EST last night until 12 PM today EST. No data was pulled from GA for almost 16 hours.

I have switched back to version 4.3.9 Works fine. No errors, no limits.

I’m getting the same error! Will this be fixed?

me too. fwiw all was fine, for me, before mid-january’s update. and now this [as the aboves]

Yep me too. The JSON in the console seems fine.

I’m getting this error as well, despite the recent update.