Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error: API response: 429 #130

Closed
hanacchi opened this issue Dec 21, 2019 · 9 comments
Closed

Error: API response: 429 #130

hanacchi opened this issue Dec 21, 2019 · 9 comments

Comments

@hanacchi
Copy link

System

  • OS name: Windows
  • OS version: 7
  • Browser name: Firefox
  • Browser version: 71

Extension

  • Extension version: 0.6.0
  • User input simulation: yes
  • Client app version: 0.2.0
  • Client app installed successfully: yes

Bug description

  1. Try to solve captcha with buster
  2. Get a notification saying "Something went wrong. Open the browser console for more details."

This happens every once in a while but when it does it usually happens a few times in a row.

Logs

Browser:

Error: API response: 429, {
  "code": "rate-limit",
  "error": "You have exceeded the limit of 400 requests per minute for your app"
}

Client app:

2019/12/21 04:05:35.516331 Starting client (version: 0.2.0)
2019/12/21 04:05:35.516331 Receiving message
2019/12/21 04:05:35.516331 Processing message
2019/12/21 04:05:35.516331 Command: ping
2019/12/21 04:05:35.516331 Sending response
2019/12/21 04:05:35.516331 Receiving message
2019/12/21 04:05:35.536332 Processing message
2019/12/21 04:05:35.536332 Command: moveMouse
2019/12/21 04:05:35.536332 X: 916, Y: 896
2019/12/21 04:05:35.538332 Sending response
2019/12/21 04:05:35.538332 Receiving message
2019/12/21 04:05:35.640338 Processing message
2019/12/21 04:05:35.640338 Command: clickMouse
2019/12/21 04:05:35.651339 Sending response
2019/12/21 04:05:35.651339 Receiving message
2019/12/21 04:05:37.341436 Processing message
2019/12/21 04:05:37.341436 Command: moveMouse
2019/12/21 04:05:37.341436 X: 1111, Y: 586
2019/12/21 04:05:37.359437 Sending response
2019/12/21 04:05:37.359437 Receiving message
2019/12/21 04:05:37.465443 Processing message
2019/12/21 04:05:37.465443 Command: clickMouse
2019/12/21 04:05:37.476443 Sending response
2019/12/21 04:05:37.476443 Receiving message
2019/12/21 04:05:37.977472 Closing client
@dessant
Copy link
Owner

dessant commented Dec 21, 2019

Try again, it seems to work now. There are too many people using the extension with the default speech recognition service, I'll add a couple more API keys in the next release and rotate them.

You can also use your own API key from https://wit.ai, it is a free service.

@Cyberavater
Copy link

I'm having the exact same problem here.

@dessant
Copy link
Owner

dessant commented Dec 21, 2019

Visit the extension's options if the error comes back, and switch to the Wit Speech API service, then add this API key for English: EQAXGAJVZIMI3YMILN2XQZY7IWGUPKGL

@hanacchi
Copy link
Author

Thanks for the quick reply! That seems to have fixed it for now. If the issue comes up again I'll get my own API key.

@dessant dessant pinned this issue Dec 29, 2019
@coaxial
Copy link

coaxial commented Jan 14, 2020

Could you detail how to get my own API key? When I go to wit.ai all I see is a very minimalistic page with three lines of text describing what the company does and no way to sign up.

Nevermind, it's my Firefox settings not loading their JS... Anyway, glad to see your extension is getting popular, thanks for your hard work!

@Cyberavater
Copy link

Cyberavater commented Apr 29, 2020

I'll add a couple more API keys in the next release and rotate them.

Can you add some more? Cuz, I'm having this issue more often recently.

@coaxial
Copy link

coaxial commented Apr 30, 2020

@Cyberavater you can get your own key and add it yourself then you most likely won't run into that issue ever again.

You can also use your own API key from https://wit.ai, it is a free service.

@dessant
Copy link
Owner

dessant commented Apr 30, 2020

4 keys should be plenty for the current user base. It's also possible that someone is taking the keys to abuse the service, so the quota is sometimes depleted.

@dessant dessant unpinned this issue May 14, 2020
@bncdemo
Copy link

bncdemo commented Nov 30, 2023

"API quota exceeded: Try again later" error. Is this the end of the story? The error is permanent.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants