I recently “upgraded” the storage (a week ago) from a Google Compute Engine attached drive to a Google Cloud Storage bucket. In theory, it is supposed to be highly scalable, but obviously there must be some subtle misconfiguration that is causing intermittent failures, as I see uploads working for some users… I’ll have to investigate more
I’ve fixed it again, thus solving the problem once and for all
All previously uploaded images are still available on a storage bucket (but with a corrupted index file), so if anyone wants to try to reconstruct things at their own peril, they can reach out to me for access…
deleted by creator
What are CSAM attacks?
It’s definitely possible we’re hitting up against some kind of size limit and need to expand our cloud storage solution. This is the first post I saw today about the issue - thanks for bringing it to my attention!
Running into same error uploading an image:
{“data”:{“msg”:“Error in store”,“files”:null},“state”:“success”}
Appreciate that feedback! We are looking into it now. I have been hearing through the grapevine that Cloudflare in general has been having some service issues today which might be contributing to our services as well.
It’s now throwing a different error when uploading an image:
POST https://lemmy.whynotdrs.org/pictrs/image
Status Code: 400 Bad Request
Response: Request error: error sending request for url (http://pictrs:8080/image): error trying to connect: dns error: failed to lookup address information: Name does not resolve
