Open Hani-K opened 6 months ago
Is the imgur or local hosting serving the broken image?
Not entirely sure, if both functionalities are broken and return a string that cannot be parsed as an image, which leads to 403. Or if the {ImageURL} var itself is broken and is not processing the links properly and resulting in 403.
But if you match the EntryData Html to the Result, line by line; You could see that the {ImageURL} variable itself returns 403, so I would start fom there.
one thing to note here: if a series get's scanned in, all subsequent episodes will use the same image hosting method as the original (so long as there exists a url for the series prior). This is a task I have in my backlog to fix (database refreshing).
So for now, could you try to follow these steps just to see if it's something with the DB as is?
the newsletters.db file lives in your jellyfin's data directory.
/PATH/TO/JELLYFIN/config/data/newsletters.db
Try with imgur first I, then repeat and try with local hosting. See if you get different results and let me know.
--- Also, you can compare the newsletter in the email with the physical copy saved into Jellyfin's cache directory:
/PATH/TO/JELLYFIN/cache/temp/Newsletters
Issue
For some reason, when sending newsletter, all images return 403. This happens with both Local JF Hosting and Imgur.
How to replicate?
Jellyfin dashboard > scheduled tasks > scan media library
.Jellyfin dashboard > scheduled tasks > Filesystem scraper
.Jellyfin dashboard > scheduled tasks > Email Newsletter
Proof of concept
My config:
I modified the EntryData to troubleshoot. My EntryData Html:
Log when using local JF hosting
Log when using imgur
Result
Setup
Jellyfin 10.8.13 Installed on a standalone Debian GNU/Linux 12 (bookworm) LXC container