Reloading the page via CTRL-F5 makes the images show up, however, since we are having this issue in many topics, this workaround is not really acceptable.
First observed beginning of September 2019 with images from dslreports.com and FF69.0 (on Windows)
Issue is still present today with FF 76.0.1 and Discourse 2.5.0.beta4
Observations of a different user
Confirmation using FF 69.0 on macOS 10.12.6âŚ
The normal page load is missing the images as reported.
Cmd-Shift-R (reload with Shift key down) causes the images to appear
Cmd-R (just normal reload) - no images again.
Chrome Version 77.0.3865.75: Same behavior
Cmd-R-no images
Cmd-Shift-R has images.
Safari Version 12.1.2 (12607.3.10) always displays images
Example topics
Topic for testing: Broken imgur images (for testing only) - Site Feedback and Other Questions - OpenWrt Forum Observation #1: When I created this topic, only the âLinked BBCodeâ wasnât showing up Observation #2: After logging out, closing FF, reopening FF and revisiting this topic again, all imgur images are broken. (The first image is not hosted at imgur and is therefore working)
Freshly opened FF, not logged in, visiting the test-topic: All images in the first posting are working
Freshly opened FF, logged in , visiting the test-topic: Last image in the first posting is not working
Chrome
Freshly opened Chrome, not logged in, visiting the test-topic: Last image in the first posting is not working
Freshly opened Chrome, logged in, visiting the test-topic: Last image in the first posting is not working
This is repeatable.
EDIT: Above results are for internet access via cable. Just to rule out that it is a connection problem, I crosschecked via mobile phone tethering: same result.
As you can see, for FF it makes a difference if Iâm logged in or not; Chrome however doesnât care, it doesnât show the last image in any case.
Enabling download remote images to local and removing imgur from disabled image download domains settings will ensure this never happens by hosting all images locally.
Donât know who hosts this forum, but it definitely is not following our Discourse official Standard Installation guide. Because of that it doesnât have HTTP/2 enable so everyone get a slower site.
Oh so that is the BBCode generated by imgur when looking into your own image, and using their âLinked Formatâ.
Well, that is something imgur controls, and nothing we can do about it. Also, we already have workarounds for HTTP content by downloading and serving media locally. Nothing else for us to do.
I would prefer to not host images locally unless absolutely necessary.
The site is hosted by DigitalOcean. I did the installation in 2016 on Debian 8 with what was available then. And⌠HTTP/2 has AFAIK always been enabled.
That is not really necessary. I believe 99% of the people will just just copy and paste images into composer for most of their needs. ++ select area and + into the composer.
Also copying the image from imgur, or the URL of it works just fine. This report is just a minor corner case.
Discourse is installed in a Docker container, and we ship updates to nginx so you donât need support on the host OS. Unless you did a custom setup with a manual reverse proxy, your should have HTTP2 out of the box just by having an up to date Discourse.
Fixing this issue for imgur seems rather simple, although with some effort involved, and that effort has to be made regularly, as new non-working links come in.
@Falco Since the dropbox link doesnât seem to work in the discourse forum too: Do you host images locally as advised above?
Yes, we download images locally, which is the default Discourse behavior.
Posting links from third parties will eventually devolve into broken images, and that is why Discourse comes with this feature built-in from the early days. Of course there is a trade-off, you have to provide space for the images, either locally or using a Object Storage service.
