Recently installed recaptcha v3. Over 1 million calls per day.
Periodically, for some users, it shows the following error:
"grecaptcha.execute('" crashes by timeout. > 10 seconds
The cache update helps. Cannot reproduce the problem locally.
How can I diagnose problem? What events can be logged?
Related
so I am currently working in heroku and I need the task to programmatically restart if certain errors arise, so I used the heroku restart API to do so. The problem is that my program is restarting every 10 seconds or so, and it seems that heroku is letting the other web tasks stay online which leads to them later on crashing. I was wondering if there was anyway to only run one task at a time and skip their 60/30 seconds waiting period for when you restart a task. I read somewhere about One - off tasks, but I wasn't sure. I am sorry for the formatting of my question, it is my first post on StackOverflow. Thank you.
I am using Amazon SES for sending emails from PHP application through Swift Mailer. I am searching on google from 3 4 days but was unable to find any solution. I tried every possible solution available on Internet but still, my issue is not resolved. Can someone please guide me how to resolve this issue?
This happens intermittently but appears to cause all our mails to stop sending once the initial error occurs - restarting the queue worker fixes it but inevitably the problem re-occurs intermittently.
I get 500 Errors when I redirect my users to the OAuth Endpoint from Europe. Has anything changed? It worked for several months
I also don't have the rep yet to comment. But I have been noticing this issue today also.
All of my sites that use Google oauth (different tokens) are returning 500 errors after choosing the google account you want to log in with.
500. That’s an error.
There was an error. Please try again later. That’s all we know.
I checked the status page and I don't see any errors or any other reports of this https://status.cloud.google.com but it seems there is something going on since at least a few of us are seeing this. I have tried from multiple computers on different networks, and I had a friend try on a different google account and had the same issue. I am using the following gem in a rails app:
gem "omniauth-google-oauth2", "~> 0.2.1"
Edit: That page has now been updated with an notice on the bottom.
We are investigating an issue with Authentication services. We will provide more information by 07:30 US/Pacific.
I can't post a comment as a guest but I have been noticing this as well. I have found that several refreshes sometimes bring up the authentication window, but I haven't actually been able to authenticate and connect yet. I am on the Eastern coast of NA trying to access GMAIL api.
This started to happen to me this afternoon , it will occasionally work but most of the time it doesn't.
I have read this may be because you must now past through the oauth_verifier which has only just been changed, although it should not have just yet.
Source GarretMurray - https://twittercommunity.com/t/oauth-access-token-stopped-working-today/1630
He said that after adding the verifier it started to work again !
I also experienced this, but the problem seems to have been resolved by Google. I observed the errors happening on our application from roughly 13:42 - 14:28 UTC.
As per https://status.cloud.google.com/
"We are investigating an issue with Authentication services. We will provide more information by 07:30 US/Pacific."
There is also subsequent post specifically on the Google Cloud App Engine service regarding this outage available at https://status.cloud.google.com/incident/appengine/16003.
Sources: See above.
I am developing a chrome extension to which I was pushing notifications so far successfully from my server. However, the notifications suddenly stopped working. I can see that my POST to https://www.googleapis.com/gcm_for_chrome/v1/messages is answered with a 204 so its not my server code.
I am sure I have not hit the 10k per day limit because I would be seeing a completely different code otherwise.
I have a few questions:
Is there a rate limit that I may be hitting?
Is it possible that I have spammed the google server too much and am being blocked?
UPDATE: This bug appears to be Browser Specific to Chrome. I've clicked the link about 50 times each in Firefox and IE and I can't seem to cause it. Also, once it is occurring, I can switch to FF or IE and it'll work fine on those two.
I have a particular page in my Rails 3 application on heroku that loads fine for awhile. I can click the same page and it loads without a problem. But after a certain number of loads, it suddenly starts to give me a 400 Bad Request Error with nginx/0.7.67 below it.
After it occurs once, everytime I load the page I get the 400 error. But if I leave the application alone for awhile, overnight for example, the page works again in the morning for a short while. But if I click the page a few times, it begins giving me that error again.
It's not something that occurs locally so it seems like it must be a heroku issue.
I also tried restarting heroku but that doesn't help. The only thing that seems to help is giving it some time off.
The heroku logs don't give me any new info as far as errors. Everything appears to be working fine and then I get a line that ends 727 | https | 400 and it just stops.
I'm using https if that helps.
The full error heroku log is:
[33m2011-07-02T15:25:59+00:00 heroku[nginx]: <-[0m GET /matters/show/34 HTTP/1.1 | 10.212.125.194 | 727 | https | 400
Let me know what code from this page would help solve this problem if you have an idea.
So after a long back and forth with the Heroku Support staff we finally found the issue. I was using Datatables in various places around my site and using cookies to store user state settings. That cookie was getting longer and longer and longer as a user navigated around the site until my header surpassed the maximum header size allowed by NGINX (8K).
The solution was to remove/simplify that cookie or switch from nginx Heroku (bamboo) to a Heroku stack that didn't use nginx (cedar).