Great news! I was actually struggling with this just last week when trying to post my Terraform config with a diagram. Kept timing out 😅
Thanks for the quick fix! Does this also apply to past posts, or only new uploads from now on?
The fix only applies to new uploads. Existing posts will keep their current image versions unless you manually re-upload them.
If you do re-upload, I'd suggest breaking that Terraform config into a separate post next time and just linking to it. Embedding large configs plus images is asking for trouble, even with the timeout increased.
Build once, deploy everywhere
Timing out on image uploads was a connection-level issue with the CDN. The fix increases the timeout window, so new uploads in large posts won't fail.
Just be aware it doesn't retroactively fix images already stuck in a failed state in old posts. You'd have to re-upload those.
Data over opinions
> Does this also apply to past posts, or only new uploads from now on?
That's a good question. I ran into the same thing trying to embed an architecture diagram in a long post a while back. Even if the fix is just for new uploads, it's a step forward.
Do we know if there's a way to tell if a past image *is* in that failed state without manually checking each post? Like a user dashboard flag or something?
> a way to tell if a past image *is* in that failed state
Not automatically, no. But if you know which posts had the issue, just edit and look at the image src in the HTML. If it's pointing to the temp blob URL instead of a permanent CDN path, it's broken. That's how I've been spotting them in our internal knowledge base.
You're right that a dashboard flag would be helpful, though. I'll add that to our feature request list for the team.
Automate the boring stuff.
> look at the image src in the HTML
That's the kind of manual fix that shouldn't exist. If the system can store the state, it should surface it.
Adding a dashboard flag is just adding another tool. Fix the root cause: make the upload process idempotent or transactional so a timeout doesn't leave broken state.
Simplicity is the ultimate sophistication
> breaking that Terraform config into a separate post next time and just linking to it
This is good advice, though I'd take it a step further. A permalink to a gist or a dedicated documentation page is often better than a separate forum post, especially for long configs. It keeps the main discussion focused and avoids version drift if you need to update the config later without bumping the entire thread.
On the re-upload point, it's a bit of a band-aid, but the alternative is a much more complex migration script for all historical content. For now, manually fixing the broken ones you actually care about is probably the pragmatic path, annoying as it is.
Oh man, that exact scenario is why I started using image hosting for anything over a quick screenshot. I've got a couple of architecture diagrams I need to re-upload now too.
> Thanks for the quick fix!
Seriously. The team that works on the forum software has been on a roll lately with these quality-of-life fixes. Between this and the recent markdown table improvements, it's getting much nicer to share technical content here.
ship it