All Activity

Hi everyone!!!! I'm the creator of Moonfin, a truly cross platform media client. If this is your first time hearing about the Moonfin project, welcome! Moonfin is a little shared ecosystem of third party clients that shares UI, functionality, and features across TV clients, Web, Mobile, and Desktop clients. It has been around since November 2025 and it is now on basically every platform you can think of. Up until now it was a Jellyfin only thing, but that's no longer the case. Moonfin Community Discord: here Moonfin website to test the web client and see more info here ────────────── How it works Everything is tied together by the Moonfin Server Plugin, which now installs on Emby seamlessly. The plugin is what powers the shared Moonfin experience across all of the Moonfin clients. It lets you log directly into Seerr, holds server wide MDBList and TMDB API keys, syncs your settings between Desktop (web gets counted as desktop if accessed through desktop or mobile if accessed via mobile browser. neat right?), Mobile, and TV, and handles the features and integrations that make the whole thing feel consistent no matter where you're using it. Install the plugin on your Emby server, point any Moonfin client at it, and you are good to go. ────────────── What the clients bring to the table NOTE: ALMOST everything here can be toggled on and off. No setting or UI is forced on you. It is YOUR media, YOUR way. Featured media bar slideshow with image preloading and content filtering, 5 different styles to chose from 4 Custom app themes and the ability to create your OWN custom themes as well Fully customizable home rows, including Seerr rows, TMDb rows, IMDb lists, and MDBList lists with proper posters Cross server playback, so multiple servers show up as one unified library Full Seerr integration with a dedicated requests screen, push notifications (as phone notifications and in-app banner for TV and desktop), download progress, and issue reporting MDBList ratings from IMDb, Rotten Tomatoes, Letterboxd, Metacritic, Trakt, AniList, and MyAnimeList Two different media detail screens with different styles and layouts to best suit your liking Live TV and DVR with an EPG refresh and lazy loaded programs In app YouTube trailer previews with SponsorBlock, theme music, and audio and subtitle delay adjustment Full playlist control with no item limit PIN protection per user and parental controls with content rating filtering Ebook, comic, and audiobook readers, plus a retro games library if you're into that (I know you are, dont lie) Offline mode with local first playback and original or transcoded downloads ────────────── All Moonfin Clients Platform Download Development Repository Android Mobile Google Play Store GitHub/Moonfin-Core Android TV Google Play Store GitHub/Moonfin-Core Fire TV Amazon Appstore GitHub/Moonfin-Core iOS Apple App Store GitHub/Moonfin-Core Linux Latest GitHub Release GitHub/Moonfin-Core macOS Apple App Store GitHub/Moonfin-Core Roku Roku Channel GitHub/Roku Tizen (Samsung TVs) Latest GitHub Release GitHub/Smart-TV tvOS (Apple TV) Apple App Store GitHub/tvOS webOS (LG TVs) Latest GitHub Release GitHub/Smart-TV Windows Latest GitHub Release GitHub/Moonfin-Core ────────────── Why so many clients? A lot of people ask how Moonfin ended up with separate clients across so many platforms. It honestly started pretty simply. The original goal was just to add the featured media bar to the Jellyfin Android TV client. Once that existed, people started saying it would be cool to have something similar on their platform. Then feature requests started coming in and it kind of took off from there. At the same time, platforms like webOS, Tizen, and Roku didn't really have alternative clients available like Android TV, Android mobile, iOS, and Apple TV have, so it felt like a good opportunity to create some. I enjoy building things and helping where I can, so I started working on ports. Having LLMs around for quick experiments, refactors, and figuring out unfamiliar platform quirks definitely helped along the way too. Why open source and why not charge for it? Honestly, I just enjoy building things and helping people. Open source lets others learn from the project, contribute if they want to, or adapt things for their own setups. I have no plans now, or in the future, to make any of these paid. : Screenshots shown in this documentation feature media content, artwork, and actor likenesses for demonstration purposes only. None of the media, studios, actors, or other content depicted are affiliated with, sponsored by, or endorsing the Moonfin client or the Jellyfin project. All rights to the portrayed content belong to their respective copyright holders. These screenshots are used solely to demonstrate the functionality and interface of the application.

Thank you to everyone who took the time to review and discuss the proxy architecture design I shared here. As some of you know, I originally built this project to work entirely through the Emby API. As development progressed, I discovered that the available APIs couldn't reliably determine when files were actively being updated. Without that level of visibility, it wasn't possible to guarantee safe file updates or consistently protect against corruption during provider failures. That realization led me to redesign the architecture from the ground up. Rather than relying solely on application-level APIs, the new engine works directly with the operating system to determine the true state of files before making changes. The result is greater stability, improved performance, and significantly stronger reliability. I'm also excited to announce that I'm officially partnering with @Fyb3roptikwhere my proxy code will be integrated directly into his Kernel Media Server, giving us a foundation that goes well beyond the limitations of existing solutions. Together, we're building a platform that delivers native HLS/DASH streaming, higher availability, and a more resilient architecture designed for long-term reliability and performance. Thank you again to everyone who shared feedback and ideas throughout this journey. Your input helped shape the direction of this project, and I'm excited to share what's coming next.

I gotta figure out how to make it size screenshots (I should google it), but every picture I post is giant! did you actually see the log file hiding under that monster of a picture? (hope you laughed... I sure as heck did).

@Luke , it didn't work. Now canyouseeme.org can't see the open port after setting up port forwarding rules on the new router. I have an escalation case with GFiber. I've seen some posts about cloudflare or wireguard tunnels. Would these help bypass the issues I'm having? If so, is there a post on the forum on how to set these up? I'd like to use something that is low cost for me, and my invited emby users don't have to pay for or download anything.

OK, perhaps try a different public facing router port?

OK if you don't know it, then you probably haven't setup emby connect: Emby Connect But this doesn't matter right now. Not until remote access is working.

You have got to be the only one I've ever heard of who thinks transcoded 384 kbps AC3 sounds better than TrueHD Atmos because that's what you're getting using the Samsung app. Also, the server has nothing to do with it since the sound goes from the Shield to the soundbar. All the server is doing is passing it through unless it's transcoding. You can run Emby server on an old PC and no graphics card as long as it's not transcoding. The Shield passes the audio to the soundbar DSP just fine. As long as you turn off Dolby Audio Processing in settings and check all the supported audio codecs your soundbar supports the audio is sent bitstreamed and untouched. If you don't do that of course it will be modified. What you get is multi channel PCM if you don't set up your Shield correctly.

Should be fixed now, this css file includes a host of changes (ive moved away from using the JS script, felt too unsafe imo) Most noteable change is the tv episode grive view inline with the jellyfin theme Elegantemby.css

Just saw something that I think is worth adding to this conversation. It looks like the dev behind the jellyfin desktop client is breaking off from the main dev team and will continue to develop the client under a different name no longer directly related to the main jellyfin project. From what I saw they plan on coming forward with more information as to why they came to this decision within the next day or so, but it appears to stem from internal conflicts and burnout from what I've read thus far. I've had this opinion for a while now, but Jellyfin's biggest weakness has been their client apps. Their Xbox app went unmaintained for well over a year until fairly recently. Their entire app ecosystem is completely disjointed whether that be first party or third party. There are far too many third party developed client apps that are touted as being the best at this one thing or that other thing. This is less of an issue if you're just hosting a media server solely for yourself, or people only use the web client. When you start inviting friends and family to your server and they want to watch on something other than a browser it becomes a nightmare trying to explain that they should use an app with one name on this platform, a completely different app on that platform, and the actual jellyfin app on this other platform. They've done some interesting things server side (and there are some arguments that can be made that some things might be handled better than emby there), but none of that matters when their app ecosystem is as dysfuntional as it is. I love free/open source software, but sometimes you get what you pay for. I run Jellyfin alongside Emby just to keep up with it. I would pick Jellyfin over Plex any day of the week despite it's issues if for some reason Emby stopped existing or went down too similar of a path as Plex. As long as Emby has an affordable lifetime license you'll never convince me that $0 is better than paying $120 one time (or a couple of times in my case as I have a couple of licenses just because I wanted to) for an overall better and more cohesive experience. IMO most people shouting that Jellyfin is better in every single way than Emby are likely basing their opinion on the price rather than the overall experience or that Jellyfin is open source as the free part is usually the appeal whether they admit it or not. Don't get me wrong, I want to actually see Jellyfin succeed, but it seems like their whole ecosystem takes just as many steps backwards as it does forwards. Emby is just a better overall experience from both the admin and user perspective. Emby on the server-side has progressed fairly well (and not surpisingly still far ahead of Jellyfin on a number of things IMO). Just as importantly the first party app support has been fairly consistently maintained throughout the years. All of my friends/family know to just download the app called "Emby" regardless of what platform they are on. I don't have to go through the explanation as to why they need to switch to this other app or platform because whatever volunteer dev that was working on the project hasn't released an update in over a year and the app is no longer compatible with the new server version. If Emby drops support for a particular app/ecosystem there will at least be a valid argument as to why it's no longer viable from a technical or supportability standpoint. It seems that when you have a dev team that gets paid for the work they do that the project actually has the resources to keep things going fairly smoothly. Who could have ever predicted that?

In case you don't know, in the new(er) app, if you go to fast forward, once its fast forwarding slowly if you click the FF button again and again it gets faster and faster. But I still prefer the old way in the old app where you just hold the button down and it gradually accelerates all by itself.

I don't know my "embyconnect email". I log into emby.media with my standard email address.

8096 per screenshot. Typo

Hello, Tested the next song and it works on single echo device and not the group echo. It seems like it acknowledge the command but doesn't process it. Thanks

Hi, I'm hoping someone can help because I've narrowed this down as much as I can. Environment Emby Server 4.9.5.0 QNAP TS-464 and TS-453D Native QPKG installation (not Docker) Nginx Proxy Manager (latest jc21/nginx-proxy-manager) HTTPS using Let's Encrypt Reverse proxy to Emby on HTTP port 8096 Reverse proxy NPM configuration is very standard: Forward Scheme: HTTP Forward Host: 192.168.x.x Forward Port: 8096 Force SSL: Enabled HTTP/2: Enabled WebSockets: Enabled Cache Assets: Disabled Block Common Exploits: Disabled No custom locations No custom nginx directives Emby Network settings Secure connection mode: Handled by reverse proxy External domain configured Public HTTPS port: 443 Local HTTP port: 8096 Local HTTPS port: 8920 Remote connections enabled UPnP disabled The strange part I have two completely separate Emby servers. Different NAS hardware Different databases Same Emby version Same reverse proxy Both behave identically. Testing results Works Windows browser via reverse proxy Android phone browser via reverse proxy Android phone Emby app via reverse proxy Android TV browser (Edge) via reverse proxy Android TV app via local IP OttoAibox Emby app via local IP Fails Sony Android TV Emby app via reverse proxy OttoAibox Emby app via reverse proxy Both Android TV devices authenticate correctly if I connect directly to: http://192.168.x.x:8096 They fail only when using: https://emby.backup.monitoringcomputers.com.au Emby Connect Emby Connect also fails. The PIN page says: Pin Confirmed. Thank you. but the TV never completes the login. Logs The server receives the authentication request. Immediately afterwards the log shows: GET /emby/Users/authenticatebyname followed by: Access token is invalid or expired. 401 Unauthorized Browser authentication succeeds through the same reverse proxy. Why I think this may be a client issue Everything else works: Browser Android phone app Direct LAN Same reverse proxy Same certificate Only Android TV-style clients fail when connecting through the reverse proxy. Has anyone seen this before? Is there something different about Android TV authentication compared with the Android phone app? Any suggestions would be appreciated.

Not quite sure what you mean pal. The plugin won't be free as you have premium. I'm bound to only allow use of my paid plugins if a user is a premium subscriber but not the other way round. The plugins are $5 each from the catalog or £10 from my website for all 4.

One of the deal breakers for me on the universal android app currently the lack of fast forward/revarse on a remote. I can navigate to the progress bar, but it moves sooo slow and only moves in miliseconds. Also I can't find the option for starting the app with profile selector.

Yes, as shown above, your server has frozen up and quit responding.

With regards to the Referer header, some provides object to Referer abd accept Referrer and vice versa The M3U Tuner plugin has just been updated to allow you to try out the different variants Ensure the m3u tuner plugin is updated to version 1.0.46 or higher and restart the emby server. This version was released today Edit your M3U settings in Live TV setup Try out the different variants by selecting one of the 4 options in the Referer header mode. There are 4 variants: 1. Include both "Referer" and "Referrer" in the header 2. Include "Referer" in the header 3. Include "Referrer" in the header 4,. Do not include any of the two in the header Of course you might also need to specify a different user agent

Yessir it's all working now! Sorry to waste your time, I should have been more thorough.

@AhmedNSane This has now been resolved Ensure the m3u tuner plugin is updated to version 1.0.46 or higher and restart the emby server Edit your M3U settings in Live TV setup There is now an optiin for the "Referer" header giving you 4 variants 1. Include both "Referer" and "Referrer" in the header 2. Include "Referer" in the header 3. Include "Referrer" in the header 4,. Do not include any of the two in the header I believe for your provider, it needs to be set to "Referrer" I will be updating the support article to include screenshots for this

Thanks for the feedback, and I’m glad you like the direction Traxx is taking. Sorting options for albums, especially Date Added and Random, are useful suggestions. DLNA playback is also worth looking into for devices that do not support Google Cast. Tailscale is not supported yet. Traxx currently only accepts the usual private internal IP ranges, while Tailscale uses addresses in the 100.x.x.x range. I will need to adjust that in the app before remote connections through Tailscale can work properly. I’m very busy at the moment, so it may take some time before I have the opportunity to investigate and implement these options. I have added them to the list of things to look into. Thanks again for the suggestions and encouragement.

Did 2 for each of the possibilities i described. First is started on dex screen, second on mobile (but then displayed on dex screen) emby_android_1784322815102.txt emby_android_1784322929512.txt

TYVM! I will test this out on my testing sandbox server today!

I am not sure if you got the right Topic. This is a plugin to create Emby Theme songs and backgrop theme videos that play on each Shows/Movies detail page

More cool ones here https://giphy.com/explore/neon-frame-stickers