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: Too many requests #5

Open
Acidham opened this issue Mar 27, 2019 · 15 comments
Open

Error: Too many requests #5

Acidham opened this issue Mar 27, 2019 · 15 comments

Comments

@Acidham
Copy link

Acidham commented Mar 27, 2019

After first successful translation I am receiving Error:Too many requests.

AlexanderWillner added a commit that referenced this issue Mar 28, 2019
AlexanderWillner added a commit that referenced this issue Mar 28, 2019
AlexanderWillner added a commit that referenced this issue Mar 29, 2019
@lucaschultz
Copy link

Same here unfortunately.

@AlexanderWillner
Copy link
Owner

Was working on this - not that easy...

@lucaschultz
Copy link

I didn't mean to be critical, thank you for your work on this 👍

@AlexanderWillner
Copy link
Owner

Seems to work now. Please test.

@Acidham
Copy link
Author

Acidham commented May 6, 2019

@AlexanderWillner better now. I am receiving less "too many requests" errors but sporatically I am receiving some errors. Not a critical issue because I got more successes than errors.

@AlexanderWillner
Copy link
Owner

@Acidham Is it somehow reproducible, e.g. based on some kind of input? Btw: The DeepL API is designed to translate up to 600 characters per minute and per customer.

@Acidham
Copy link
Author

Acidham commented May 7, 2019

@AlexanderWillner it happens just a few times and sporadically. I tried several combinations but the point in time when the error is thrown is different.

I assume the query is fired once the dot was entered, correct? If yes I did not reach request limits of 600.

I will run additional tests and narrow down the use case.

@AlexanderWillner
Copy link
Owner

Basically working.

@AlexanderWillner
Copy link
Owner

Reopening. Not easy. Also see:

Already looked into the DeepL App HTTPS requests. It's also using the jsonrpc - very similar to this code here. For now, I'm using the official app. But will include a solution if someone finds one.

@MiTereKun
Copy link

Too many requests - solved by manually clearing cookies in the browser, even without changing the IP.

I asked a good friend to write (well, to be honest, to re-write) a browser plugin for instant insertion of text from the clipboard to the website of (any) translator. Maybe anyone is interested, because this is better than the official application

@MiTereKun
Copy link

And the most interesting thing is that the original plugin worked even without this super original 12 line code:

image
The original works only with DeepL and sticks the text in the page link after the last slash https://www.deepl.com/translator#ja/en/
For example, Google reloads the page from such an insert, which leads to the loss of the plugin's right to work and it must be reactivated manually.

@scrapix
Copy link

scrapix commented Aug 3, 2022

I experience the same problem...
[15:36:12.816] Deepl-Translate[Script Filter] Queuing argument 'ich habe hunger.' [15:36:13.342] Deepl-Translate[Script Filter] Script with argv '(null)' finished [15:36:13.371] Deepl-Translate[Script Filter] {"items": [{"uid": null,"arg": "Error: Too many requests","valid": "yes","autocomplete": "autocomplete","title": "Error: Too many requests"}]}

@AlexanderWillner
Copy link
Owner

Best workaround: just get your own (free) API key and configure it in the workflow. See #20

@Tenskin
Copy link

Tenskin commented Jun 29, 2024

Hello, I have the same issue (Error: Too many requests), but I don't understand what is the fix proposed on this page. Can someone give me instructions?

@AlexanderWillner
Copy link
Owner

  • Invoke Alfred
  • Press ⌘ + ,
  • Go to Workflows
  • Right click on DeepL-Translate > Configure...
  • Enter the API Key you got from DeepL for free

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

6 participants