• CatoblepasEnglish
    33·
    4 months ago

    It’s for a cat, it’s clearly a smelloscope!

  • KazuyaDarklight@lemmy.worldEnglish
    7·
    4 months ago

    {“code”:“object-request-error”,“msg”:“Invalid status 429 Too Many Requests for Some("01/90/dc/68/af/53/7f/c8/90/b5/cd488bef606f.jpeg") - {\n "message":"Too many requests"\n}”

    Seems we’ve overloaded this Lemmy server.

      • Salamander@mander.xyzMEnglish
        7·
        4 months ago

        This error is a rate limit from the object storage provider. I did not know of this limit when I chose them, and I still have not found a way to change the limit. I will send them an e-mail. If the limit can’t be increased, one option is to pick another object storage provider, but the migration takes days.

        • aeharding@vger.socialEnglish
          1·
          3 months ago

          Any update on this? The rate limiting is affecting users on other instances too unfortunately.

          • Salamander@mander.xyzMEnglish
            4·
            3 months ago

            This is the current status:

            • The instance is serving the images via object storage. Specifically, I am making use of Contabo to save and serve the images.

            • I now know that the default limits are 250 requests / second and 80 Mbit/s: https://help.contabo.com/en/support/solutions/articles/103000275478-what-limits-are-there-on-object-storage-

            • It appears to me like when the requests are exceeded, the “Too many requests” error is triggered and it takes a few seconds before the requests are accepted again. This can happen if few users access the front page at once as this will fetch all of the thumbnails and icons on the page.

            • I have been in touch with Contabo’s customer support via e-mail. But they mis-understood my original e-mails and thought I was speaking about increasing the maximum number of images that can be stored (3 million by default). I have clarified that I want to increase the rate limit and have been waiting for their response for a few days now.

            • The other solution would be to move the images to a different object storage provider. The migration is also limited to the 250 requests/s and 80 Mbit/s, so it will require turning off the images for 4 - 7 days while all the images are moved… Since I am not familiar with the policies of other object storage providers I would also need to do research to avoid falling into the same trap.

            So, I am hoping that Contabo’s support will get back to me soon and allow me to increase the rate limits, as this would be the most straight forward approach.