I am getting an error from Google PageSpeed Insights API. Its just returns Internal Error with Code 500.
Here is the detailed response:
"error": {
"errors": [
{
"domain": "global",
"reason": "internalError",
"message": "An error occurred while fetching or analyzing the page."
}
],
"code": 500,
"message": "An error occurred while fetching or analyzing the page."
}
}
I also Tried with Google API key from within Google Cloud Console (Enabled
PageInsights APi for my account). No Luck still the same message.
Here is a result screenshot of the same page tested on tools.pingdom.com
It would be helpful if Google Provided detailed error messages which can help us identify where the issue is. Any help or pointers on this would be great.
The issue was with an SVG image. Once it was removed Page Speed starting working. Still not sure what was wrong with the image.
You have too many resources loading on page load. The Render limit is 200.
You can also try to test your site with think with Google
Related
When I do an GET to the test google site in the docs the blogger documentation the request works fine.
When I do a GET to my personal site I get this error:
{
"error": {
"errors": [
{
"domain": "global",
"reason": "notFound",
"message": "Not Found"
}
],
"code": 404,
"message": "Not Found"
}
}
Working:
https://www.googleapis.com/blogger/v3/blogs/2399953?key=AIzaSyA-6DkaL7Ff_U5Xwm4c_0XoCA_I4G1E24U
Non working:
https://www.googleapis.com/blogger/v3/blogs/657661307303?key=AIzaSyA-6DkaL7Ff_U5Xwm4c_0XoCA_I4G1E24U
I DO have the blogger v3 API enabled. My key is working as shown above. My blog is set to public and can be viewed here:
http://mutant1098.blogspot.com/
Also I see the failed requests coming into my bloggers dashboard.
I don't understand what the issue is. Why is it working on google bloggers main site but not my personal site.
I scoured the API dashboard for any permissions issues but couldn't find any that looked like the problem.
Thanks in advance for any guidance. This looks like a great platform just wish it was either easier or better documented.
Your blog ID must be incorrect, because the call to getByUrl works:
https://www.googleapis.com/blogger/v3/blogs/byurl?url=http%3A%2F%2Fmutant1098.blogspot.ca%2F&key=AIzaSyA-6DkaL7Ff_U5Xwm4c_0XoCA_I4G1E24U
after following the step-by-step instructions (https://developers.google.com/beacons/proximity/guides) I can successfully enable the Google Proximity Beacon API and create both API key and OAuth 2.0 client IDs for the App I created in the Google Developers Console.
Everything appears to be set up fine: the Google Proximity Beacon API shows to be active and "Credentials" tabs shows both API Key and OAuth 2.0 client ID.
The problem occurs when I try calling my Beacon: the Response gives me a "401" error:
...
"code": 401,
"message": "The request does not have valid authentication credentials.",
"status": "UNAUTHENTICATED"
...
The strange thing is that if I try the oauthplayground, again following google's proximity docs, I get a 403 error:
{
"error": {
"status": "PERMISSION_DENIED",
"message": "Project has not enabled the API. Please use Google Developers Console to activate the 'proximitybeacon' API for your project.",
"code": 403,
"details": [
...
I'm kind of lost here...anyone?
Thank you in advance.
Flik
We are calling API by url:
https://www.googleapis.com/customsearch/v1?key=MY_KEY&cx=CUSTOM_SEARCH_ID&q=flower
getting error in reponse:
"error": {
"errors": [
{
"domain": "usageLimits",
"reason": "accessNotConfigured",
"message": "Access Not Configured. Please use Google Developers Console to activate the API for your project."
}
],
"code": 403,
"message": "Access Not Configured. Please use Google Developers Console to activate the API for your project."
}
WE have enabled Custom Search API and Google + API. Still getting above error. Should we needto enable some other API too?
Please help.
(I'm repeating here the answer I gave you here).
No, I believe that custom search API is the only API that you need to enable.
So, I would consider whether you have the right key and CSE ID.
To verify your CSE ID, do a test query from here (fill in ):
https://console.developers.google.com/project/PROJECT_ID/apiui/api/customsearch/method/search.cse.list
If your query works there, but still doesn't work in your code, then perhaps the issue is your key. If you are just doing a simple URL request (as you show in your Q), then I would expect you are using a server key. And, of course, the key you are using must be from the same project where you have enabled the CSE API.
So the problem I'm facing is uploading large video files trough Youtube API v3.0.
I'm folowing the steps specified here.
So I thought that the issue lies in access token, becouse it's valid only for 3600 seconds. So I got the refresh token from OAuth Playground. And I get the fresh token when user starts the upload on my Youtube channel. After 50 minutes i abort the PUT request, get the fresh token and resume upload like specified in documentation. The problem is that after one hour I get response:
{
"error": {
"errors": [
{
"domain": "global",
"reason": "authError",
"message": "Invalid Credentials",
"locationType": "header",
"location": "Authorization"
}
],
"code": 401,
"message": "Invalid Credentials"
}
}
Everything works fine when upload lasts less than one hour. But when uploading big files on slow broadband the upload fails. What am I doing wrong?
I'm making the requests in JavaScript with jQuery. I double checked the steps in documentation, and if it works with smaller video i think the script is ok.
Even this script fails to upload after one hour, the progress bar comes to 100% but then it gets 401 response.
Thank you for your time, and sorry for my bad english.
I'm trying to fetch twitter feeds of a certain user into my IOS app. First I got it working with this link.
https://twitter.com/status/user_timeline/wwwkrcgenkbe.json?count=25&from=wwwkrcgenkbe
But when I tested it I got the following error:
{
"errors": [
{
"message": "Sorry, that page does not exist",
"code": 34
}
]
}
Twitter recently switched off that API endpoint. (https://dev.twitter.com/docs/faq#11716)
You need to be using URLs with the format api.twitter.com/v1.1/.
I suggest reading the latest API documentation, this will probably be a good place to start: https://dev.twitter.com/docs/api/1.1/get/statuses/user_timeline