2026-06-18 23:27:21
#Jellyfin for #Roku 3.2.1 is scheduled for release on Friday, Jun 19, 2026 5:00 PM PT
https://github.com/jelly…
#Jellyfin for #Roku 3.2.1 is scheduled for release on Friday, Jun 19, 2026 5:00 PM PT
https://github.com/jelly…
#Jellyfin for #Roku 3.2.3 is scheduled for release on Tuesday, Aug 4, 2026 5:00 PM PT
https://github.com/jelly…
a new #Jellyfin puzzle: on scanning my shows …
mpp[3766883]: mpp_platform: can not found match soc name: raspberrypi,5-model-b brcm,bcm2712
what is an mpp when you get one home?
related to this, my Movies are barred from scans again, and it was going so well:
[ERR] Failed executing DbCommand ("11"ms) [Parameters=["@__date_1='?' (DbType = DateTime), @__p_0='?' (Size = 3004)"], CommandType='Text', CommandTimeout='30']"
[ERR] An exception occurred while executing an 'ExecuteUpdate' operation for context type '"Jellyfin.Database.Implementations.JellyfinDbContext"'."
""Microsoft.Data.Sqlite.SqliteException (0x80004005): SQLite Error 19: 'UNIQUE constraint failed
something sends a null SQL UPDATE, and the scan process aborts 😞
also https://forum.jellyfin.org/t-database-sqlite-error-19 and https://forum.jellyfin.org/t-database-issue-exception-occurred (first suggests it's unrelated to renamed files?)
This pre-release issue reports upgrade creating duplicate users and provides and SQL fix:
https://github.com/jellyfin/jellyfin/issues/14423
which leads to this useful rabbit hole: https://jellywatch.app/blog/jellyfin-database-maintenance-optimization-guide-2026
#Jellyfin Server 12.0 RC3 has been released!
We're inching closer to the next server release!!!!
https://github.com/jellyfin/jellyfin/releases/tag/v12.0-rc3
#Jellyfin does great at finding and playing, but oddly, on Android's app, text copy is forbidden? I had wanted to grab and search the whole description in hopes of finding out who this is.
You can maybe either go get a laptop, or invoke Google Lens? Why would they do this? Protect from scraping info previously scraped from elsewhere?
#Jellyfin for #Roku 3.2.2 is scheduled for release on Monday, Jul 27, 2026 5:00 PM PT
https://github.com/jelly…
apparently the phenomenon is new with 10.11 #Jellyfin
https://github.com/jellyfin/jellyfin/issues/15384
I also cannot delete the phantom old Twilight Zone, and so cannot see the updates of same name, as I apparently do not have permission to delete a file that isn't there. It wasn't there again today; I wish I wish it'd go away! 😊
Having #selfhosted services, like #jellyfin seems extra magic during a major broadband outage!
Ok, major major stupid flaw in #jellyfin and looks like the only solution is wipe clean the entire dB and reinstall … every time you make an outside change?!
And starting from scratch means copious mislabeled items. It will take me weeks to fix television shows. Admittedly I chose Jellyfin because it appeared to work well sharing legacy files and folders with Nextcloud, and I loved the big-screen apps. It was fun, until I noticed …
But I can't spend my life re-entering metadata, and the family just laughs at the brokenness.
How, no, why on earth would a competent programmer throw an uncaught exception and abort because a file to be deleted has already been removed, or simply renamed? What is the business case for such? Why make an archive write-only, no deletes, no renames, no moves?
Is there a less fragile alternative?
a #Jellyfin question, that's actually on the forum but unanswered in months so perhaps it's because the fix is easy?
the scans for directory changes do not appear to remove missing files or folders. as a result, as I learned about 'proper' jellyfin file nameing and fixed things so similar titles were not grouped, I end up with many phantoms. Selecting one to watch gives an error, and the log is full of scans reporting things missing. An example now that blocks me, I'd put my Twilight Zone collection up, but then added the '84 series which JF lists as the '64 series in titles etc. I split these, with {imdb-} flags, but all we see are bad links to files no longer there, which also means Metadata cannot 'delete' them.
Is there a fix?
Important information regarding #jellyfin project leadership changes.
https://forum.jellyfin.org/t-project-leadership-changes
How does this impact the
Stop believing #reddit posts from peeps who act like they have information, but are just speculating trolls. Infact, never believe reddit posts for anything!
Stop believing "news" posts from peeps who act like they have information, but are just speculating trolls.
Read why Joshua stepped down from
Point of clarification regarding the new #JellyfinJune episode 2 video regarding clients.
In the video it's said the official clients are "just the website packaged..."
That's only true for some of the clients, and certainly isn't true for #Jellyfin for…
well …it was a good try but #Jellyfin still gets that UNIQUE constraint error, only the database does not have any duplicates, not if this is correct:
SELECT ItemId, UserId, CustomDataKey, COUNT()
FROM UserData
GROUP BY ItemId, UserId, CustomDataKey
HAVING COUNT() > 1;
to test, I listed =1 through sort | uniq -c just to be sure 😅 so whatever such 3-part not-UNIQUE it is wanting isn't in my jellyfin.db 🤔
This really needs to be common #Jellyfin knowledge:
https://jellywatch.app/blog/jellyfin-fail2ban-setup-guide-block-brute-force-attacks-2026
Update on the #Jellyfin Library Remove trick: it did damage to edge-case metadata, but did nothing to let me add my Doctor Who, or anything else new.
I may try using SQL to edit the db directly, but I'm beginning to fear one must do a COMPLETE purge and re-install after any filesystem changes
Spending the weekend farm-sitting in South Bay with #SamsungTv that has no #jellyfin client and the absolute worst browser you ever tried, but I got in and with practice could watch my movies and, I discovered, could put my entire music channel on random play!
Except, another jellyfin Inexplicable, if it hits an unsupported file, FULL STOP and a dialog box. So it cannot run unattended (unless your collection is Pure) 😔
#Jellyfin cruft-clearance update: I found space to backup "short films" ~70 GB to then test, and doing Dashboard / Libraries / Libraries and on the Hamburger on Short Film clicking Remove did NOT delete any content! 🥳
Testing again, after backing up Television, which is an order of magnitude larger and full of bad or ambiguous filenames, but still backupable … given time.
I clearly will have metadata to fix for a while. The program I wrote for Cage's mesostics, seeking previously unused syllables from biblical names when Hebrew rules are different and OCCASSIONALLY, less and less, requiring human assistance, was also numbingly tedious.
John called it, "knitting with my computer" 😊
RE: #NextCloud files with #Jellyfin
I do like #jellyfin and have come to depend on it, but it's these dumb design decisions, and when the back-trace is littered with references to Microsoft code, well, I don't want to profile anybody, but it's a red flag in my (long) experience. It worries me.
It's just dumb. Deleting a missing file is a warning at best, not a stacktrace abort; a playlist fail shouldn't stop the party and call for a tech.
On My Resignation as #Jellyfin Project Leader | Joshua Boniface, sysadmin
https://www.boniface.me/posts/on-my-jellyfin-resignation/
Another run in with cruft in #jellyfin and a strong recommendation to others to read their manual page on filenames very carefully, at least until this notion of uncaught exceptions on missing files is updated to be a mere shrug and flush of associated metadata,and a priority to fix.
What happened was really stupid on my part: I noticed file shares often include an IMDB tag in the filename. I had THOUGHT I had seen {imdb-tt…} in the wild, but it had no effect (so I thought) so I hunted up the guide, and so I corrected them to be [imdbid-tt…]
I can no longer watch those shows: Jellyfin offers the old {imdb-*} and will not register the 'new' [imdbid-*] files, even in the Folders view.
For a wishlist, I'd hope some enterprising coder can roll a db-cleanup script that recognizes a missing file and purges all references. Would be nice if it recognized a name-change-only case and ported the old metadata, but hey, as it is, the only method left is wipe clean rebuild from scratch, so anything at all is welcome.
Not sure why, but within the LAN I've needed to whitelist all hosts using #Jellyfin clients, otherwise their IP gets blocked by Fail2Ban after about an hour of watching. I fear this would happen to remote viewers too, but not sure I've ever watched more than an hour remotely. No idea if any other remote client services do the same, I've not let them run more than a few minutes.
Is this perhaps a #debian #ufw #Fail2Ban setting I should know about?