XF 1.5 Issues with IMG tags displaying

Gazhyde

Well-known member
I have this issue someone has raised where it's displayed the broken image indicator when a post is made with IMG tags. I think this may have started when we upgraded to 1.5.14. Any ideas?

Link to example post - https://zroadster.org/threads/img-tags-not-working-anymore.20223/

1507284681601.png

If I edit the post the image displays fine.

1507284721950.png

Original image link
Code:
[IMG]https://audio.home.xs4all.nl/zooi/z4/div/z4vberg.jpg[/IMG]
 

Chris D

XenForo developer
Staff member
The broken icon is coming from the Image Proxy. It indicates that it wasn't able to retrieve or display the image for some reason.

You can test this under Tools in the Admin CP. That should give you a reason for the failure.
 

Chris D

XenForo developer
Staff member
The error is reporting a connectivity issue between your server and the server where the image is hosted.

Can you tell if it is just happening with this image? What about images hosted on the same site? Or images hosted on another site?
 

Gazhyde

Well-known member
Also have the same on this thread - https://zroadster.org/threads/gookahs-progress-journal.2721/page-2#post-120082 There are some IMG tags pointing to Flickr that do the same.

The first image in that post is
Code:
https://c1.staticflickr.com/2/1681/24335145562_6cede03269_b.jpg
Which gives the same error.
Code:
https://c1.staticflickr.com/2/1681/24335145562_6cede03269_b.jpg could not be fetched or is not a valid image. The specific error message was: Unable to Connect to ssl://c1.staticflickr.com:443. Error #110: Connection timed out
Oddly though the last image loads, but has a slightly different URL to the others.
Code:
https://farm4.staticflickr.com/3921/14376257254_9ce3a3962d.jpg
Could it be anything to do with CloudFlare getting in the way?
 

Chris D

XenForo developer
Staff member
Could it be anything to do with CloudFlare getting in the way?
It could be yeah, or something else on the server side.

It seems somewhat sporadic, but the fact that it is happening on images from multiple sources suggests it is something on the server (or the path to/from the server).
 
Top