Trailers to requests mod in the JMP

[NicolaSmaniotto]

Is it possible to apply the trailers to requests mod to Jellyfin Media Player?

I have tried patching the files in /usr/share/jellyfinmediaplayer/web-client/desktop/. The tab is renamed and the page shows the Jellyseerr login, but after entering the password nothing happens even though no error is logged.

[BobHasNoSoul]

Honestly I have never been big on the jellyfin media player, most of the clients I use are either web client based or Kodi based systems.. I can look into it however I think it may be totally different in the way this is made (however could be simple I guess)

The main issue you are describing sounds like it isn't passing the user and password from the website to the iframe

Can you try the following
Access from the http Lan IP and see if a http Lan IP iframe to jellyseer will work if it does we know it's because HTTPS and http issues

If you are using HTTPS for jellyfin but http for jellyseerr this will cause issues and similar for the other way around.

Note I will dive into this when I'm free because it sounds odd.. but if the frame exists and loads but doesn't log in.. that's either cross site scripting issues (server.com to notserver.com) or another issue.

I know long ago there was an error with ombi integration and it was because it didn't originate from the same domain to get around it I made ombi load from a base URL on the same domain as jellyfin.

[NicolaSmaniotto]

The server has no HTTPS at all, we access through plain HTTP with Tailscale.

The same happens if I connect with the internal IP or the MagicDNS name server. Connecting to the Jellyfin container logs, it prints:

[09:50:17] [INF] [24] Jellyfin.Server.Implementations.Users.UserManager: Authentication request for nicola has succeeded.
[09:50:17] [INF] [24] Emby.Server.Implementations.Session.SessionManager: Current/Max sessions for user nicola: 1/0
[09:50:17] [INF] [24] Emby.Server.Implementations.Session.SessionManager: Reissuing access token: 2f32c4b2fdc649f69b404f68a75be0b7

So it seems that Jellyseerr is correctly sending the request to Jellyfin, which responds with a correct login.