Skip to main content
Meta Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

12
  • 10
    Can replicate the issue on my end Commented Jun 7 at 0:33
  • 11
    Able to reproduce on the sites, but it works on chat. On chat, image uploads are quite slow but work fine. Most likely it's taking too long, resulting in a timeout on the sites, but chat sites have a larger or nonexistent timeout period. Commented Jun 7 at 0:34
  • 7
    Also able to reproduce -- main & meta site image uploads fail while chat uploads work. Commented Jun 7 at 0:45
  • 2
    @SonictheAnonymousHedgehog Yes, chat upload takes a very long time, but does work. On the main sites image upload fails with an unknown error after only about 21 seconds or so. That seems somewhat for a timeout, at least taken at face value. Chat uploads seem to take longer than that. Perhaps there could be component protocol failures at a finer granularity than is easily obvious to a casual observer. Commented Jun 7 at 2:37
  • 1
    This is probably also causing not being able to change profile pictures (or maybe it’s just a me problem?) Commented Jun 7 at 4:04
  • 3
    One of the profile picture sources supported is SE image hosting so that might track Commented Jun 7 at 4:12
  • 20
    Can confirm - we appear to be having a (possibly intermittent) issue with a third-party service we use for the security scanning of the uploads. I'm not familiar with this part of our system, so I unfortunately can't offer much more, but I've escalated this internally and we'll get folks on it tomorrow (or, fingers crossed, the issue will resolve itself by then). Thanks for the report! Commented Jun 7 at 5:12
  • 2
    It looks like the issue has been fixed, or has resolved itself. Commented Jun 7 at 16:50
  • 2
    @PM2Ring The latter, although I was just about to deploy a mitigation. I'm choosing to believe that intimidated everything into getting back to work. Said mitigation is deployed anyway, so if this happens again, we should be in a better state. Commented Jun 7 at 17:44
  • 2
    @PM2Ring - Hi, Thanks - as you said, image upload seems to be working again which is good news. However, until we get a statement from SE staff that something has actually been fixed, then we don't know if whatever-caused-it could fail again. From here: "If you didn't fix it, then it ain't fixed" :) || Let's hope for an update from SE staff when they are confident of a fix, along with an explanation of the cause for the records :) Commented Jun 7 at 17:44
  • @AdamLear - Hi, Our comments crossed :) If you're confident of the fix, will you be posting an answer, or are you waiting to test the mitigation, or ...? Thanks for your help with this. Commented Jun 7 at 17:45
  • 5
    @SamGibson I posted an answer. I'm going to keep an eye on things over the weekend, but I don't really expect new problems here. Commented Jun 7 at 17:53