[Issue]: Keeps caching station logos forever, even if they change in M3U and XML #5166

Closed
opened 2026-02-07 01:31:16 +03:00 by OVERLORD · 5 comments
Owner

Originally created by @Moonbase59 on GitHub (Oct 17, 2023).

Please describe your bug

Seems https://github.com/jellyfin/jellyfin/issues/8903 is still an issue: Station logos are somehow kept forever, even after a Jellyfin restart.

I have some stations that changed their logo (as can be seen in the m3u and xml files, but Jellyfin never updates these. Clearing the browser cache doesn’t help, and it also shows the old logos in the Desktop Media Player (Win & Linux), the AndroidTV clients.

Even deleting all M3U tuners and TV Guide Data Providers (XMLTV) and then recreating them doesn’t help!

Jellyfin Version

10.8.z

if other:

No response

Environment

- OS: Ubuntu 22.04.3 LTS
- Linux Kernel:
- Virtualization: Proxmox LXC
- Clients: Misc
- Browser: Firefox 118.0.2, MS Edge, Chromium
- FFmpeg Version:
- Playback Method:
- Hardware Acceleration: VAAPI
- GPU Model:
- Plugins:
- Reverse Proxy:
- Base URL:
- Networking:
- Storage:

Jellyfin logs

No response

FFmpeg logs

No response

Please attach any browser or client logs here

No response

Please attach any screenshots here

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
Originally created by @Moonbase59 on GitHub (Oct 17, 2023). ### Please describe your bug Seems https://github.com/jellyfin/jellyfin/issues/8903 is still an issue: Station logos are somehow kept forever, even after a Jellyfin restart. I have some stations that changed their logo (as can be seen in the `m3u` and `xml` files, but Jellyfin never updates these. Clearing the browser cache doesn’t help, and it also shows the old logos in the Desktop Media Player (Win & Linux), the AndroidTV clients. Even deleting all M3U tuners and TV Guide Data Providers (XMLTV) and then recreating them doesn’t help! ### Jellyfin Version 10.8.z ### if other: _No response_ ### Environment ```markdown - OS: Ubuntu 22.04.3 LTS - Linux Kernel: - Virtualization: Proxmox LXC - Clients: Misc - Browser: Firefox 118.0.2, MS Edge, Chromium - FFmpeg Version: - Playback Method: - Hardware Acceleration: VAAPI - GPU Model: - Plugins: - Reverse Proxy: - Base URL: - Networking: - Storage: ``` ### Jellyfin logs _No response_ ### FFmpeg logs _No response_ ### Please attach any browser or client logs here _No response_ ### Please attach any screenshots here _No response_ ### Code of Conduct - [X] I agree to follow this project's Code of Conduct
OVERLORD added the bugstale labels 2026-02-07 01:31:16 +03:00
Author
Owner

@GodBleak commented on GitHub (Nov 25, 2023):

As a workaround, you can delete the contents of livetv in your metadata folder.

@GodBleak commented on GitHub (Nov 25, 2023): As a workaround, you can delete the contents of `livetv` in your `metadata` folder.
Author
Owner

@nikolas-sturm commented on GitHub (Feb 12, 2024):

As a workaround, you can delete the contents of livetv in your metadata folder.

this doesn't seem to work for me at all. i deleted the m3u tuner and xmltv inside the app and turned off the container. then i deleted the livetv metadata; deleted xmltv and image cache fully; cleared browser cache; start jellyfin again; readd m3u and xmltv; images are still completely different than in the m3u file.

@nikolas-sturm commented on GitHub (Feb 12, 2024): > As a workaround, you can delete the contents of `livetv` in your `metadata` folder. this doesn't seem to work for me at all. i deleted the m3u tuner and xmltv inside the app and turned off the container. then i deleted the livetv metadata; deleted xmltv and image cache fully; cleared browser cache; start jellyfin again; readd m3u and xmltv; images are still completely different than in the m3u file.
Author
Owner

@nikolas-sturm commented on GitHub (Feb 12, 2024):

ok, i dug a bit deeper using debug logs and found that specifically all images hosted on imgur had problems. i then found that imgur for some reason has rate limited my server ip and i was getting 429 errors on those images. changing the images to a different host fixed the problem again after deleting livetv in metadata.

@nikolas-sturm commented on GitHub (Feb 12, 2024): ok, i dug a bit deeper using debug logs and found that specifically all images hosted on imgur had problems. i then found that imgur for some reason has rate limited my server ip and i was getting 429 errors on those images. changing the images to a different host fixed the problem again after deleting livetv in metadata.
Author
Owner

@jellyfin-bot commented on GitHub (Jun 12, 2024):

This issue has gone 120 days without an update and will be closed within 21 days if there is no new activity. To prevent this issue from being closed, please confirm the issue has not already been fixed by providing updated examples or logs.

If you have any questions you can use one of several ways to contact us.

@jellyfin-bot commented on GitHub (Jun 12, 2024): This issue has gone 120 days without an update and will be closed within 21 days if there is no new activity. To prevent this issue from being closed, please confirm the issue has not already been fixed by providing updated examples or logs. If you have any questions you can use one of several ways to [contact us](https://jellyfin.org/contact).
Author
Owner

@jellyfin-bot commented on GitHub (Jul 3, 2024):

This issue was closed due to inactivity.

@jellyfin-bot commented on GitHub (Jul 3, 2024): This issue was closed due to inactivity.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/jellyfin#5166