1

Are you using stock Docker compose setup?
Yes

If not, either reproduce this issue on the official demo or switch to Docker and see if the issue is resolved.
The issue can be reproduced on demo server too

Describe the problem you’re having:
One specific feed (Reviews (all) - Progarchives.com) is loaded and parsed correctly, however article images are never displayed when using tt-rss via browser (firefox, chrome, or edge).
Images are correctly displayed when using the Android app.

Include steps to reproduce the problem:

  1. install tt-rss on server and android app
  2. add Reviews (all) - Progarchives.com and refresh feed
  3. confirm no images are seen on browser but are seen in Anrdoid app

tt-rss version (including git commit id):
Tiny Tiny RSS v21.06-9669bb94d (but this problem has been happening already for a few months)

Platform (i.e. Linux distro, PHP, PostgreSQL, etc) versions:
Debian 10.1
Linux 4.19.0-14-amd64
Docker-compose setup

Please provide any additional information below:
feed debugger comes back clean and I can’t seem to find any error in it
tested with multiple browsers (Chrome, Edge, FF) disabling browser extensions and in private/incognito mode
I only use 3 plugins in tt-rss which I don’t believe interfere (af_comics, af_youtube_embed, and note) as disabling all 3 of them does not fix the problem

2

i’ll make a note to take a look at your feed some time next week, unless someone else does it first.

3

update - images (album covers) seem to show up just fine here.

image

even managed to find something i like

4

Had this issue too once: I accidentaly checked “use less traffic” at the login. Logout, make sure this is not checked and log in again.

5

@madmap thanks for the hint but the option has never been checked

@fox I confirm the fix works on FF, but for some reason both Chrome and Edge still don’t show images
missing

more info:
Microsoft Edge Version 92.0.902.62 (Official build) (64-bit)
Google Chrome Version 92.0.4515.107 (Official Build) (64-bit)

on Chrome I cleaned all cache/cookies and tried in incognito mode as well.

I have opened developers tools in both FF and Chrome and notice one difference: FF image requests receive the image as reply, but Chrome/Edge image requests seem to receive a 301 redirect.

edge
edge534×540 10.8 KB

If you want the full HAR traces from FF and Chrome I can provide them to you once sanitized.

6

going by your post, to me this doesn’t look a tt-rss issue.

try using different a network connection (i.e. VPN) or a different PC.

7

Thanks for the suggestion, I have tried that from Chrome on my phone while connected to 4G (thus bypassing my home network used in the previous attempts).
Unfortunately I experience the same behavior, ruling out a problem with my device/connection.

_20210804_125440
_20210804_1254402520×1080 263 KB

Sorry if this is quite a melon scratcher but if there’s anything else you think I could do to help troubleshooting please let me know.

8

What happens when you put the url of the image directly in an address bar? Of it serves an image at all, how different is the resulting url from the one in the feed?

9

good point @ddowdle.
problem

http://www.progarchives.com/progressive_rock_discography_covers/11839/cover_133232862021_r.jpg
10

I have a similar situation. The cause is mixed-content. My ttrss is served via https, but the site (Dork Tower) is still only available via http. The app doesn’t bother with that.

Maybe it’s the same with your feed.

11

image2

(had to resize image, sorry)

12

I re-read your reply and I stand corrected:

@MasinAD seems you’ve hit the nail in the coffin as the image comes from HTTP (as probably visible in my last screenshot).
It does however not explain why FF now displays them while Chrome/Edge still don’t…
Do you have any workaround for this?

13

You can use the ttrss-proxy-http plugin to get insecure images securely via your server.

14

@JustAMacUser thanks, will try and report back

15

ahh, mixed content. completely slipped my mind.