Update 1: This is an issue with cloudflare, we are having issues with the account that hosts the site, we are contacting cloudflare support about the issue.

Update 2: we have switched s3 providers and images should be working again, older images may be missing, we will have to do a merge with the old s3 storage backup into the new provider, we plan to do this soon, but all new images will work as expected, sorry for the issues and thanks for your patience and kindness while we were working on the fix

  • leftzero@lemmynsfw.comEnglish
    81·
    8 days ago

    That is not the issue

    It’s the underlying cause of the issue. (Well, that and dealing with cloudflare.)

    we are having issues with our cloudflare account

    Yes (that’s what cloudflare appears to be for). Which is causing your stupid proxy to produce this shit instead of an image:

    {“code”:“object-request-error”,“msg”:“Error performing PUT https://eb21b514652257169b552d5ece7ddfd2.r2.cloudflarestorage.com/lemmynsfw/01/98/22/63/d5/9e/74/c2/94/48/97232eff1bb0.jpeg in 45.917481ms - Server returned non-2xx status code: 403 Forbidden: <?xml version="1.0" encoding="UTF-8"?><Error><Code>NotEntitled</Code><Message>Please enable R2 through the Cloudflare Dashboard.</Message></Error>”}

    You’ll notice how the first link, which is what your site produces, craps out (because your cloudflare account isn’t working properly, as tends to happen with cloudflare, no surprise there), while the second link, which is the original URL reconstructed from your mangling, works perfectly. (I grabbed it from some random post in the front page, the content is irrelevant but harmless).

    So keep the fucking original URL instead of hijacking it with some stupid unnecessary proxy and it’ll fucking work!

    Q.E. fucking D., for fuck’s sake! 🤷‍♂️