-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
馃悰 Bug Report: 429 Too Many Requests at high upload speeds #7879
Comments
@WuGGu, thanks for creating this issue! 馃檹馃徏 Would you please share the exact full error? Request and response headers would also be helpful. |
I'll be back in the office on Tuesday due to the Easter vacation and will reproduce it. 馃槉 |
@stnguyen90 {
"message": "Rate limit for the current endpoint has been exceeded. Please try again after some time.",
"code": 429,
"type": "general_rate_limit_exceeded",
"version": "1.5.4"
} payload:
|
@WuGGu, thanks for this! Also, what are you using to create the file? If you're using one of our SDKs, would you please provide the version? |
Ahh wait I think I found the problem. Looks like we made a fix in #7154, but there was a regression and abuse key is missing the chunkId: appwrite/app/controllers/api/storage.php Line 342 in 2993537
Compared to 1.4.x: appwrite/app/controllers/api/storage.php Line 342 in 5cfaee4
|
A previous PR added chunkId as an abuse key param to fix a problem where uploading multiple chunks of a file would trigger the `general_rate_limit_exceeded` error. For some reason, the parameter disappeared from the abuse key causing a regression. This PR adds the param back to fix the regression. Reference: * #7879 * #7154
馃憻 Reproduction steps
Upload big file like 1GB. Use a Internet connection with 200Mbit Upload.
馃憤 Expected behavior
Should just upload quicker to the storage.
馃憥 Actual Behavior
Returns 429 after a view seconds because of Too Many Requests in under 60 seconds.
馃幉 Appwrite version
Version 1.5.x
馃捇 Operating system
Linux
馃П Your Environment
Hetzner Machine with Rocky Linux and Docker.
馃憖 Have you spent some time to check if this issue has been raised before?
馃彚 Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: