All Activity

When the guide updates, my recording gets canceled. I don't understand why this one gets canceled and not others that could be considered similar.

@Luke@ebrIf you want some videos, you can ask.

Check out v1.3.10.0 — now with support for multiple languages! https://github.com/Amanade3/Emby-New-Overlay-plugin Découvrez la v1.3.10.0 — prise en charge de plusieurs langues ! Schau dir v1.3.10.0 an — jetzt mit Unterstützung für mehrere Sprachen! Descubre la v1.3.10.0 — ¡ahora con soporte para varios idiomas! Scopri la v1.3.10.0 — ora con supporto per più lingue! Confira a v1.3.10.0 — agora com suporte para vários idiomas! Bekijk v1.3.10.0 — nu met ondersteuning voor meerdere talen! Встречайте v1.3.10.0 — теперь с поддержкой нескольких языков! v1.3.10.0 をチェック — 複数言語対応になりました! 快来看看 v1.3.10.0 —— 现已支持多种语言! v1.3.10.0 확인해보세요 — 이제 다국어를 지원합니다! Sprawdź v1.3.10.0 — teraz z obsługą wielu języków! Kolla in v1.3.10.0 — nu med stöd för flera språk! v1.3.10.0'a göz atın — artık birden fazla dil desteği var! تحقق من الإصدار v1.3.10.0 — أصبح الآن يدعم لغات متعددة!

One of these is the issue. Could the reverse proxy be altering web socket messages that are going from client to server? are you able to monitor that in it's app? how have you configured the network tab in the emby server?

Not the "Allow remote control of shared devices" The screenshot could have been better. Must admit i always thought the "Allow Remote control of other users" was for being able to stop the other streams. But trying it now it doesn't actually remove the controls. Never played around with the setting my self as i never had problems. I would as a first troubleshoot step try something as simple as clearing the cache of the browser. That will at least rule out the browser as being the problem.

What option?

Hi, it does by the artist and album artist values embedded in your audio files. How are they tagged ?

I know this isn't the big issue to fix but wondering if there's any update. Still having the issue and I've been trying every beta update that comes out.

And for Afroman it does list "The Prodigal Son" also for the Artist Joseph Foreman, but when i click on it it reads and links to Afroman. It also shows under Afroman too. But for "The Land of Thule" by Burzum (NEW) it shows Burzum as Artist, Burzum (NEW) as Album artists and only lists it on the Burzum page as featured on.

So, like the title says, for a lot of artists that use an "alias" (different name, same artist), Emby seems to add the alias as a new, separate artist instead of associating it with the original artist. Likewise, instead of showing the complete overview you would expect from the MusicBrainz page, some of the artist's music appears to be missing because it is associated with the alias rather than the correct artist. Here are some examples:

Hahaha, i didn't notice the date. It was late when I wrote it Thanks for reminding me!

This is still happening for me on all my Roku devices (at least) as of 4.10.0.40. I think it might happen elsewhere when transcoding is happening but I'm not sure. I'm a long time plex user trying to migrate the family off to emby but they are not loving this bug (and I don't blame them). I'm a premiere subscriber, if it matters.

Hi, the Emby app is also in the app store.

Server version: 4.10.0.31 Apple TV app version: 2.0.9 (1) iOS app version: 2.2.58 Not sure how best to describe what's happening other than showing a video of it happening, but the video is glitching/ghosting/rubber banding. It happens regularly after watching anytime between 5-30m. I did not see the issue at all on the iOS app. Both were direct playing so no transcoding. image_D5BEB523-6AC2-4D21-83F1-9CA528DA8EE1_1789437607.mov embyserver (2).txt

Adding to the above, I also tested Samsung and LG TVs using the latest app versions available from their respective app stores. Both show the same behavior. As soon as the second user starts playback, there are no remote-control buttons available in the Emby Dashboard for those sessions. That makes this broader than an Android app-version issue. I am seeing the same loss of remote control across Android, Samsung, and LG clients on 4.10, while iOS, Apple TV, and Web remain controllable.

No need to be sorry! I was able to figure this out. It looks like adding this plugin, it disabled the default selections of My Media, Latest Movies, etc. I just had to go to each profile and add them back in. No problem though!

embyserver-redacted-2026-09-15.txt See attached. It took a while to tail the relevant logs because "Anonymize log contents" does not do a very good job, so I had to manually scrub quite a bit of information from the log. However, here is what I found. The capture was taken while the issue was actively occurring, with remote Android clients streaming normally but showing no remote-control options in the Dashboard. The server explicitly identifies the affected Android playback as remote: IsPlayback: true, isInLocalNetwork: False Playback itself continues normally. The Android clients continue reporting playback progress and receiving successful responses from the server. What stands out is that, during the same window, the server repeatedly logs: SessionInfosWebSocketListener failed processing WebSocket message SessionsStart with: System.IndexOutOfRangeException inside: MediaBrowser.Controller.Net.BasePeriodicWebSocketListener.Start There are six occurrences of this during the short capture. At the same times, the server also repeatedly logs: ActivityLogWebSocketListener failed processing WebSocket message ActivityLogEntryStart with a System.FormatException, again inside BasePeriodicWebSocketListener.Start. There are also six occurrences of that error. I also found three 404 responses to: GET /embywebsocket?api_key=...&deviceId=... while the affected Android sessions are active and continuing to report playback normally. I am not claiming that any one of those entries, by itself, proves the root cause. What I am pointing out is that there are repeated server-side WebSocket processing failures occurring at the same time the remote-control problem is present. One other limitation of this log is that Info-level logging does not show the request body for /Sessions/Capabilities/Full, so it does not expose the actual SupportsMediaControl value being declared by the client. The only capability registration that happened during this particular capture window was Apple TV, which completed successfully with a 204. The Android sessions were already active when I started the capture, so I am not interpreting the absence of an Android capability registration in this window as proof that Android never registered one. The important part remains that this is reproducible by changing only the Emby Server version. On 4.10.0.40 these remote Android sessions are immediately treated as non-controllable. Reverting to the previous stable restores the Dashboard controls for the same clients, users, permissions, reverse proxy, and network configuration, until the longstanding WebSocket timeout occurs.

@yocker, "Allow remote control of shared devices" is not what governs this. That policy lets an account send content to shared devices, the DLNA-style ones with nobody signed in. The sessions in question are not shared devices, they are normal user sessions with a user signed in and actively streaming (Emby for Android on the TV boxes, and a Samsung TV). So that toggle does not even apply to them, and either way it is a permission on the controlling account, not something that decides whether a given client platform can be controlled. Here is the proof it is not that setting. The exact same admin account (and other users) keep full remote control on iOS and Apple TV with no problem. That same account logs in on a Samsung TV, which had working controls before this update, and there are none. Same account, controls work on one platform and vanish on another. A user or account permission cannot do that, because it would kill control everywhere, not only on Samsung and Android. To remove all doubt, I turned that setting on for my own admin account and I had it streaming a show, and there were still zero controls for it in the Emby dashboard. So the toggle is not the fix. I have already rolled back to the previous stable, since I rely on these controls to manage my kids' streams. Hopefully the logs cr8iveLosr is supplying help Luke narrow this down.

Gentlemen...... I might have a solution. While, it's not Emby. Astra, is available in the APPstore and it does recognize the Jellyfin server, Emby is coming soon. Jellyfin works right now but they plan to have Emby working soon.

Works both on local, through VPN and through just normal remote and with promote proxy. Works with my users as well. For the admin account that you want to be able to control others.

Why are you necroing a 9 year old thread..

@scottpro You got it - all correct now. Another detail worth noting: For better transparency, we have started versioning the core UI code. These are the 26.0.-ish version numbers like the web app is showing. In the changelogs for apps (like here for example) and the server you can see sections like "Core UI Changes" which tells you the version of the core ui that is included.

Hi there, please attach the Emby server log from when the problem occurred: How to Report a Problem Thanks!

Thanks for chiming in. This question was already answered, not once, but twice.

Interesting, @yocker. On my end this really is not a permissions thing, because nothing changed except updating the server to the latest Emby stable. And like I said above, I rolled back to the previous stable and remote control came right back with no other changes. That is about as clean a before and after as it gets. I would ask you the same thing I would ask about any test here, because the details really do matter. Is your setup a local install on the same network, or are your clients connecting in remotely through a reverse proxy and subdomain? On my side iOS and Apple TV are golden, the controls work and messages go through, while Android and Samsung are the ones that lost control. So if you are testing on the LAN, or you are not on an Android or Samsung client, that would explain why you are not seeing it. To add to this which setting are you referring to specifically? I have toggled every user setting on and it makes no difference. I also tested this with a full admin account, my own, and the issue is exactly the same there. An admin account already has every permission there is, so if remote control fails even for the admin, that rules permissions out entirely. And if you are saying the admin is somehow lacking a permission to remote control, then that is a separate bug on its own. That is really why I keep coming back to the setup. Same server, same account, same permissions: iOS and Apple TV work, Android and Samsung do not. There is no per user permission that disables remote control for only Android and Samsung while leaving iOS working for that same user. That points at the client platform and the 4.10 server, not a toggle. Not trying to be difficult, just trying to pin down the exact conditions so we are actually comparing the same thing.