[media-finish] Moonfin: opt-in enabled — fetching latest release... [media-finish] WARN: Moonfin: no .zip asset found in latest release. from what i can tell, there is a .zip in the latest moonfin release, Moonfin.Server-1.9.1.0.zip
7 replies
tomspark wrote:
Honestly, hats off — filing the issue AND building the fix yourself is above and beyond, and extra respect for being upfront about how it was made. I can't bundle it into SparkBox though: that would ship code onto other people's boxes that neither of us can fully vouch for yet, and a Jellyfin plugin holds the keys to the whole media server. Nothing personal — our own patches are held to the same bar. The right road is exactly the one you're on: once the Moonfin dev reviews and merges it, SparkBox picks up their next release automatically, no action needed on our end. And knowing exactly which cookie step was missing is a big head start for the bridge we've been looking at on our side. For anyone else reading: this is an unreviewed community build, so weigh that before installing.
tomspark wrote:
Hey RyuikuX! Thanks for catching this—looks like our installer's asset detection isn't finding Moonfin's .zip properly. We've flagged this for investigation. Meanwhile, you can try manually downloading the .zip from the release and placing it in your media folder, or let us know if you'd like help with that workaround. Appreciate the detailed report!
RyuikuX wrote:
Ive hit another wall. worked with the AI to my daily limit twice now trying to get through it. I've manually installed Moonfin, which the moonfin client is working, but the seerr integration is not. i get far enough that i have the plugin installed on the jellyfin server, enabled the seerr integration, but when i try to link the seerr integration from moonfin client using credentials, i get an error saying "no session cookie from Seerr." From my research ive been able to confirm that the connection is working technically, because if i try to link with incorrect credentials i get a different error. according to Seerr's logs, when i submit the request to link, it says "Found matching Jellyfin user; updating user with Jellyfin" and jellyfin log reports "[2026-07-06 02:15:22.715 +00:00] [INF] [48] Jellyfin.Server.Implementations.Users.UserManager: Authentication request for "luke" has succeeded. [2026-07-06 02:15:22.715 +00:00] [INF] [48] Emby.Server.Implementations.Session.SessionManager: Current/Max sessions for user "luke": 1/0 [2026-07-06 02:15:22.715 +00:00] [INF] [48] Emby.Server.Implementations.Session.SessionManager: Logging out access token "d49f9782bb65469f93f41b6a9542f557" [2026-07-06 02:15:22.716 +00:00] [INF] [48] Emby.Server.Implementations.Session.SessionManager: Creating new access token for user 77000a84-ad7a-4ed1-91e7-9e8f8a96e911 [2026-07-06 02:15:22.745 +00:00] [WRN] [29] Moonfin.Server.Services.JellyseerrSessionService: No session cookie received from Seerr for user "luke"" I read online that a Session cookie might be getting stripped if the request changes from HTTPS to HTTP, and ive tried using nginx to pass certs and utilize https, but im still hitting the same error. im not sure if there are Seerr / Jellyfin settings im missing to utilize HTTPS and a cert, or any other settings that would make the integration work. i have noticed Seerr has an update from 3.2.0 to 3.3.0 but i doubt that'll fix the issue im having. Seerr is working just fine as a standalone. im just really trying to get the convenience out of Moonfin.
RyuikuX wrote:
I know Seerr works through it’s interface. I’m really trying to get moonfin working for extra convenience. A while ago I saw a demox post about you guys fixing this issue, but It wasn’t uh technical enough for me to know what was done or what needs to change. Is the issue something that even can be fixed on the seerr side, or do we need to raise the flag with moonfin’s dev? I’ve already created an issue in moo fin’s GitHub of the issue
tomspark wrote:
Both, honestly — it could be fixed from either side, so opening the GitHub issue with Moonfin's dev was exactly the right move. The post you remember was us fixing the earlier version of this: our Seerr used to reject Moonfin's login outright, so we shipped a patch on our side that adjusts Seerr's login code as it starts up. That's why you now get as far as a successful login — but our Seerr still never hands back the session cookie Moonfin waits for, because Moonfin was written for the original Seerr and the edition we ship answers that step differently. Cleanest fix is Moonfin supporting our edition, and your issue helps there. We're also looking at whether another patch on our side can bridge it — no promises on timing yet.
RyuikuX wrote:
I got tired of waiting around for the original dev to look into and make a fix, so i did it myself. here is a link to the raw manifest.json if you want to add it as a plugin repo to jellyfin, as well as a direct download to my fix release since i think Sparkbox manually installs moonfin's plugin as it currently stands. https://raw.githubusercontent.com/Ryuiku/Moonbase-CookieFix/master/manifest.json https://github.com/Ryuiku/Moonbase-CookieFix/releases/download/1.9.1-cookiefix/Moonfin.Server-1.9.1-cookiefix.zip This is just temporary until the original dev reviews my work and applies this fix himself. i am not a coder, this is my first time ever modifying a source code, and ive only built something from source a handful of times. i used Claude to do everything, and i read the code but im not experienced so i cant identify anything that would be bad or a security risk. Use this if you want to, but for now im set and anyone who comes looking for a solution can also use this. i have verified, it does work :)
tomspark wrote:
You've done everything right — this isn't a settings problem, and it's not the HTTPS thing either, so don't sink more hours into certs or nginx. The "no session cookie from Seerr" error happens because Moonfin was built for a slightly different edition of Seerr than the one SparkBox ships. When Moonfin asks our Seerr to log you in, it never hands back the login ticket Moonfin is waiting for — nothing on your box is misconfigured, and the 3.3.0 update won't change it. The good news: everything that integration would give you already works in Seerr itself. Open http://YOUR-BOX-IP:5055, sign in with your Jellyfin account, and request stuff there — you only lose the button inside Jellyfin. Getting Moonfin talking to our Seerr needs a change on Moonfin's side; it's on our radar.