-
Notifications
You must be signed in to change notification settings - Fork 104
Error: Too Many Requests #72
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
Comments
Does it happen when you first time enable the local store feature? The app does an initial data load when the local store is enabled the first time for the account. At the moment app does the fetching without any delays and even more, currently the app runs up to 3 requests of this kind If the guess is correct, then there will be a need to enable delay between requests, which will slow the data load process down but will let it be successfully completed. The thing is that Protonmail doesn't expose its rate limiting settings information and that's understandable. So I think I better disable a parallel loading and enable the configurable delay in |
Yes I have around 500 mails archived. |
Can you try the build uploaded here? It enables the 250 requests per 1 minute rate-limiting ( "fetchingRateLimiting": {
"intervalMs": 60000,
"maxInInterval": 250
}, If it still fails with the same error, you can adjust the settings in order to make them more strict by editing Besides, keep in mind that this is The initial/bootstrap fetch will work longer with this rate-limiting thing, but it's one-off case since the consequent syncing occurs in incremental mode, ie app fetches the changes diff only. |
I have tested with you release. I have 4 protonmail accounts. I have disabled the local storage settings for each one except for the main wich contains more than 500 mails. |
Thanks for confirming issue resolving, so I keep the default configuration for the final v2 release. The fix is included in just published v2.0.0-beta.7 release. |
Hi
I get the folowings errors when I use the app:
Too Many Requests
Logs:
app verison: 2.0.0-beta-6
electron: 3.0.9
chrome: 66.0.3359.181
node: 10.2.0
v8: 6.6.346.32
The text was updated successfully, but these errors were encountered: