Leaderboard

Apologies. At some point I allocated my emby server with only one vCPU. I'm not sure how this happened. I've provisioned the server with eight vCPUs and searching is no longer a problem.

That's it working mate, thanks a lot much appreciated.

Here we go, an idea that sounded simple caused a lot of headaches along the way, but we eventually got there. Updates: More color variable options, a few variables to fine tune colors in specific areas. (See Section 1 updates for more details) Table grid header colors moved from h1-color to h5-color Video titles, music now playing in the OSD us now using h3-color instead of h1-color Changed custom CSS box to use 500 lines instead of 1000 Fixed icon hover shadows in the sidebar and dialogs popups. Fixed table view play buttons. Fixed the (3 dots ...) in table views to have a hover color. Removed the media bade effect from dialog popups Fixed the halo effect that happened with watched/favorite indicators in media cards. Fixed audio full screen image hover bugs Updated seasons to not use background images if they are set. (There's already enough animation going on, and it looked awful) (Some seasonal fixes still need to be done.) Updated seasons to reflect various changes. More image backdrop animation options (See section 1 updates for more details) Fixed various areas in the music suggestions page Submit/Action buttons will no longer be in all uppercase. Any many more fixes. Section 1 Changes: If you customized your CSS, you could keep your section 1 and just update section 2 on down. but here are the important things that were added or changed so you can modify accordingly. A lot of areas were re-organized; colors options were placed more closely together. And some moved into more appropriate areas. (No real change needs to happen here if you wish to keep your section 1) New header icon color variables (This affects the main pages, not the headers inside the OSD): --header-icon-color: var(--my-gold); /* Header icon color */ --header-icon-hover-color: var(--my-gold-light); /* Header icon color in a hover state */ New sidebar icon color variables: --sidebar-icon-color: var(--my-gold); /* Sidebar icon colors */ --sidebar-icon-hover-color: var(--my-gold-light); /* Sidebar icon colors in a hover state */ New OSD icon color variables: --osd-icon-color: var(--pure-white); /* Icon colors for the OSD display */ --osd-icon-hover-color: var(--my-gold-light); /* OSD Icon colors in a hover state */ (Pay attention to the OSD one @MediaEmby1968, if you loved those orange buttons in the OSD, you would want to change that, as white will be the default.) New Dialog icon color variables: --dialog-icon-color: var(--my-gold); /* Dialog popup icon color */ --dialog-icon-hover-color: var(--my-gold-light); /* Dialog popup icon color in a hovered state */ Various comments were updated but I did not really keep track of those. This comment is to note though as more options were created --backdrop-anim-toggle: imgZoomFadeIn; /* Options are: 'imgZoomFadeIn', 'imgPanRight', 'imgCinematicDrift', 'imgFadeOnly' to ENABLE the backdrop animation, or 'none' to DISABLE it */ Some of these default colors may change in time, I'm still experimenting with them to see what I actually prefer. I Think that's It, hope I did not miss anything on my notes here. Emby Navy and Gold v5.0.css Enjoy!

Access to admin areas when not logged in. Problem :- Issue, ability to view settings, options, limited details, unable to update details ( i cannot ) however options are available and viewable to an extent, applying changes creates an error popup -Sign in Error- "Access token is invalid or Expired" see, (Happy with that) Well the fact is that i can see things which are on the admin panels, most areas when I or you have not logged in to the server. I can even tell you if you have Emby premier or not. Now is this an issue??? Im not a hacker, so i dont know how far someone could go, what can actually be done etc. That's why i'm here. Hopefully someone can shed some light. Background setup: - Tested vulnerability on two Emby servers. Both run Dietpi OS as a base, both Emby Premier, Both Odroid C2 SBC, both have multiple USB SSD drives, both run on SD card installations, Both are accessible from the internet on Http and Https, one has a domain name redirected with an A record to a static IP address, one uses http only and a ddns address. Both are standard Emby installations apart from one having fail2ban installed as well, but no extra linux services apart from the minimal, as Odroid C2s are good but not that good. Some plugins are installed on both, Music Brainz, MDB, Opensubs, NFO, DLNA, Trailers, Playback reporting etc. (if you believe these could be a cause, i'll be glad to do more testing) Also, i dont know if this is a Dietpi issue, i guess someone will alert me of this , if the vulnerability doesn't work for you on another OS. Thanks in advance. Recreate the issue: - Logout of the Emby if you are in, try this in another browser, Firefox, edge, try an incognito window, new private window, (this works on all of them by the way in my instance) Anyway, just do it a computer or browser that is not logged in. Even my Samsung phone does this. 1. open a browser and visit your Emby web UI, Remotely, on the phone via the 4-5G internet, locally via your installation Ip or server name, or via a domain name, whatever works for you. If you are prompted to login, great, if not prompted logoff. You may or not see the usernames to choose from or perhaps not, depending on your settings. If you are being prompted to login, don't, instead go to the address bar and remove everything in the address and only leave this: - (of course i am giving you an Ip example, your browser will have your Emby server Ip or domain name). Examples :- http://192.168.178.188:8099/web/index.html#!/ http://192.168.170.148:8096/web/index.html#!/ https://emby.myemby.com.au:443/web/index.html#!/ (Whatever, you get the gist) 2. Once you have removed all of the trailing address sections the fun begins. add the word "dashboard" to the end of the address. you end up with Ie :- http://192.168.170.148:8096/web/index.html#!/dashboard https://emby.myemby.com.au:443/web/index.html#!/dashboard etc. 3. now refresh the page, click go, click enter, it doesn't matter but the important part is to refresh the page when the address is seen correctly, this is the trick. you will see the login page once reloaded .. 4. The magic. now that you have inserted https://emby.myemby.com.au:443/web/index.html#!/dashboard in the address bar, click the big ( < ) in the upper left next to the big Emby logo on the refreshed login page. Not back in the browser, back within the Emby Login Page itself. 5. Now tell me if you have Emby Premier or just the standard version? 6. Do this with any section in the admin panel you wish to try, just add the sections name to the address bar, refresh the browser, once back to the login page, click the ( < ) arrow top left next the the Emby Logo to view that particular section. Again, not back in the browser but the back arrow within the Emby login page . 7. Try this with any Emby admin panel section name, you get the gist of this by now or is it only me????? users, apikeys, logs, scheduledtasks, plugins, databases, network etc., all of it. If you try using the user directory, say for instance "home" at the end of the address, refresh and click the back< button you won't see much, but if you have a custom css background , you will see the background page load. 8. I was unable to shutdown the server even though the button is visible, apply any changes, add users, view libraries or make any useful changes to affect my Emby servers, i guess that's logical as anyone doing this is not actually logged in. So it's not that much of a vulnerability i guess, but I'm not a programmer and actually have no clue if someone could do something in this area by looking at the page code, page source, developer options and the like. They would also have to find the exposed server before even getting into this.. Probably should have other means of reporting a problem in the report a problem section? Anyway i believe someone should have a look and tell me, if its only me or it's a bug of some sort. I've attached some screenshots of the areas i entered within the admin Ui without being logged in for reference Sorry i couldn't screenshot the whole screen with the address bar, windows doesn't let me, but anyway i hope i've outlined it thoroughly enough that it can be reproduced.

Hi, we are working on improving this. Thanks.

Yes search can be slow, if you run Emby on a underpowered pc. This all started after search was reformed 4.9 server version. Using delimiters is always a good option. I guess its Emby's version of fuzzy search that comes into play here. More CPU power / quicker search. But WHY ??? Edit: Adding. I also guess it depends on the numbers of extras. Search = John Media items to search = 127.236 less than a 3 sec.

I will be attentive... because also now I have to go over all those changes I made again. I'll have to write them down separately to have them on hand. Thanks,... downloaded and will try it tomorrow

Movies and TV shows with commas (,) in the title are not recognized by the metadata scraper.

That'd do me

Thx for the hint. I have used the ATV App for ages and now tested the default Emby App. Seems ok for me and at a first test i did not missing something (and of course credit popup is working ). You have stated that the emby devs considering phase out the ATV app in favor of the default EMby app (which as an developer pov i can understand). Regarding the transition i found the blog post: and this from Luke: So yes, i think the way to go is to use the default Emby App from now on. Will test the default app further on my shields (also with DV content, denon receiver in between...). Again thx for this nice plugin.

Never saw that option! Thanks a lot!

Hi mainsupport, should be possible without any issues. I‘ll compile & upload a 4.8 version later today.

Yeah - that's it. Happy to run with this for a while and do some more tagging and importing... thank you!

Try demi-bold one: v1.8 GUI refined emby_album_tag_importer.py

I am trying out the plugin and am getting the below error on the configuration page. The top menu shows up, but nothing else. I am running the official container image (docker.io/emby/embyserver:latest) via podman. The plugin was working previously, and I tried to update to v2.4.7. I have been changing plugins, and maybe there is an incompatibility or missing dependency? + TimeMarkEdit + EmbyReporter (with container volumes as described in instructions, also tested the container without these) - ChapterAPI Things I have tried, without any change in behavior: downgraded back to 2.4.2 and get the same result rebuilt container with/without EmbyReporter volumes removed TimeMarkEdit and EmbyReporter restored from "Backup & Restore" backup (which apparently does not restore plugin dlls) removed EmbyCredits.xml config file (plugin did not recreate a fresh one) replaced EmbyCredits.xml from my backup Relevant entries from my logs 2026-04-14 20:07:43.996 Info App: Loading EmbyCredits, Version=2.4.2.0, Culture=neutral, PublicKeyToken=null from /config/plugins/EmbyCredits.dll 2026-04-14 20:07:47.474 Debug Server: Defaulting route to authenticated: EmbyCredits.Services.CreditsDetectionApiService.TriggerDetectionRequest 2026-04-14 20:07:47.475 Debug Server: Defaulting route to authenticated: EmbyCredits.Services.CreditsDetectionApiService.ProcessEpisodeRequest 2026-04-14 20:07:47.475 Debug Server: Defaulting route to authenticated: EmbyCredits.Services.CreditsDetectionApiService.ProcessSeriesRequest 2026-04-14 20:07:47.475 Debug Server: Defaulting route to authenticated: EmbyCredits.Services.CreditsDetectionApiService.ProcessSeasonRequest 2026-04-14 20:07:47.476 Debug Server: Defaulting route to authenticated: EmbyCredits.Services.CreditsDetectionApiService.ProcessSeasonMissingMarkersRequest 2026-04-14 20:07:47.477 Debug Server: Defaulting route to authenticated: EmbyCredits.Services.CreditsDetectionApiService.BatchUpdateSeasonMissingMarkersRequest 2026-04-14 20:07:47.477 Debug Server: Defaulting route to authenticated: EmbyCredits.Services.CreditsDetectionApiService.ProcessLibraryRequest 2026-04-14 20:07:47.478 Debug Server: Defaulting route to authenticated: EmbyCredits.Services.CreditsDetectionApiService.GetAllSeriesRequest 2026-04-14 20:07:47.478 Debug Server: Defaulting route to authenticated: EmbyCredits.Services.CreditsDetectionApiService.GetProgressRequest 2026-04-14 20:07:47.478 Debug Server: Defaulting route to authenticated: EmbyCredits.Services.CreditsDetectionApiService.GetBackupExportProgressRequest 2026-04-14 20:07:47.479 Debug Server: Defaulting route to authenticated: EmbyCredits.Services.CreditsDetectionApiService.GetBackupImportProgressRequest 2026-04-14 20:07:47.479 Debug Server: Defaulting route to authenticated: EmbyCredits.Services.CreditsDetectionApiService.CancelDetectionRequest 2026-04-14 20:07:47.479 Debug Server: Defaulting route to authenticated: EmbyCredits.Services.CreditsDetectionApiService.ClearQueueRequest 2026-04-14 20:07:47.480 Debug Server: Defaulting route to authenticated: EmbyCredits.Services.CreditsDetectionApiService.GetSeriesMarkersRequest 2026-04-14 20:07:47.480 Debug Server: Defaulting route to authenticated: EmbyCredits.Services.CreditsDetectionApiService.GetSeasonValidationRequest 2026-04-14 20:07:47.481 Debug Server: Defaulting route to authenticated: EmbyCredits.Services.CreditsDetectionApiService.DryRunSeriesRequest 2026-04-14 20:07:47.481 Debug Server: Defaulting route to authenticated: EmbyCredits.Services.CreditsDetectionApiService.TestOcrConnectionRequest 2026-04-14 20:07:47.482 Debug Server: Defaulting route to authenticated: EmbyCredits.Services.CreditsDetectionApiService.GetImageRequest 2026-04-14 20:07:47.482 Debug Server: Defaulting route to authenticated: EmbyCredits.Services.CreditsDetectionApiService.GetThumbnailRequest 2026-04-14 20:07:47.483 Debug Server: Defaulting route to authenticated: EmbyCredits.Services.CreditsDetectionApiService.DryRunSeriesDebugRequest 2026-04-14 20:07:47.483 Debug Server: Defaulting route to authenticated: EmbyCredits.Services.CreditsDetectionApiService.GetDebugLogRequest 2026-04-14 20:07:47.484 Debug Server: Defaulting route to authenticated: EmbyCredits.Services.CreditsDetectionApiService.ExportCreditsBackupRequest 2026-04-14 20:07:47.485 Debug Server: Defaulting route to authenticated: EmbyCredits.Services.CreditsDetectionApiService.ImportCreditsBackupRequest 2026-04-14 20:07:47.485 Debug Server: Defaulting route to authenticated: EmbyCredits.Services.CreditsDetectionApiService.BulkExportToFolderRequest 2026-04-14 20:07:47.486 Debug Server: Defaulting route to authenticated: EmbyCredits.Services.CreditsDetectionApiService.ExportSeriesCreditsRequest 2026-04-14 20:07:47.486 Debug Server: Defaulting route to authenticated: EmbyCredits.Services.CreditsDetectionApiService.ImportSeriesCreditsRequest 2026-04-14 20:07:47.486 Debug Server: Defaulting route to authenticated: EmbyCredits.Services.CreditsDetectionApiService.UpdateCreditsMarkerRequest 2026-04-14 20:07:47.487 Debug Server: Defaulting route to authenticated: EmbyCredits.Services.CreditsDetectionApiService.ApplyToSeasonRequest 2026-04-14 20:07:47.487 Debug Server: Defaulting route to authenticated: EmbyCredits.Services.CreditsDetectionApiService.AddTimestampFromDryRunRequest 2026-04-14 20:07:47.488 Debug Server: Defaulting route to authenticated: EmbyCredits.Services.CreditsDetectionApiService.GetMemoryUsageRequest 2026-04-14 20:07:47.488 Debug Server: Defaulting route to authenticated: EmbyCredits.Services.CreditsDetectionApiService.StartDetectionRequest 2026-04-14 20:07:47.489 Debug Server: Defaulting route to authenticated: EmbyCredits.Services.CreditsDetectionApiService.GetDetectionMethodsRequest 2026-04-14 20:07:47.489 Debug Server: Defaulting route to authenticated: EmbyCredits.Services.CreditsDetectionApiService.GetDetectionResultsRequest 2026-04-14 20:07:47.490 Debug Server: Defaulting route to authenticated: EmbyCredits.Services.CreditsDetectionApiService.GetDetectionHistoryRequest 2026-04-14 20:07:47.491 Debug Server: Defaulting route to authenticated: EmbyCredits.Services.CreditsDetectionApiService.GetEpisodeDetectionResultRequest 2026-04-14 20:07:47.491 Debug Server: Defaulting route to authenticated: EmbyCredits.Services.CreditsDetectionApiService.GetFailedEpisodesRequest 2026-04-14 20:07:47.492 Debug Server: Defaulting route to authenticated: EmbyCredits.Services.CreditsDetectionApiService.ClearFailureMarkersRequest 2026-04-14 20:07:47.492 Debug Server: Defaulting route to authenticated: EmbyCredits.Services.CreditsDetectionApiService.ClearAllFailureMarkersRequest 2026-04-14 20:07:47.493 Debug Server: Defaulting route to authenticated: EmbyCredits.Services.CreditsDetectionApiService.GetEpisodeChaptersRequest 2026-04-14 20:07:47.493 Debug Server: Defaulting route to authenticated: EmbyCredits.Services.CreditsDetectionApiService.SaveEpisodeChaptersRequest 2026-04-14 20:07:47.494 Debug Server: Defaulting route to authenticated: EmbyCredits.Services.CreditsDetectionApiService.GetTracerEpisodesRequest 2026-04-14 20:07:47.494 Debug Server: Defaulting route to authenticated: EmbyCredits.Services.CreditsDetectionApiService.DismissTracerEpisodeRequest 2026-04-14 20:07:47.495 Debug Server: Defaulting route to authenticated: EmbyCredits.Services.CreditsDetectionApiService.ClearTracerListRequest 2026-04-14 20:07:47.827 Info TaskManager: Daily trigger for Backup Credits Markers set to fire at 04/15/2026 01:15:00, which is 307.2028694 minutes from now. 2026-04-14 20:07:48.001 Info App: Starting entry point EmbyCredits.Plugin 2026-04-14 20:07:48.014 Debug XmlSerializer: Deserializing file /config/plugins/configurations/EmbyCredits.xml 2026-04-14 20:07:48.027 Warn Plugin: RUNNING ON LINUX WITHOUT CUSTOM TEMP FOLDER! If using Docker/Unraid, your image may fill up with temp files. Configure 'Custom Temp Folder Path' in plugin settings to point to a mapped volume (e.g., /mnt/user/appdata/emby-temp or /tmp). 2026-04-14 20:07:48.041 Info Plugin: Credits Detection Service started 2026-04-14 20:07:48.043 Info App: Entry point completed: EmbyCredits.Plugin. Duration: 0.0413932 seconds 2026-04-14 20:07:51.806 Debug WebAppService-0HNKQHDL1QU55:00000001: http/1.1 GET http://‌REDACTED‌/emby/web/configurationpage?name=CreditsDetectorConfiguration&v=4.9.3.0. Source Ip: ‌192.168.1.7‌, UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/147.0.0.0 Safari/537.36 2026-04-14 20:07:51.807 Debug WebAppService-0HNKQHDL1QU57:00000001: http/1.1 GET http://‌REDACTED‌/emby/web/configurationpages?Name=CreditsDetectorConfiguration&X-Emby-Client=Emby Web&X-Emby-Device-Name=Brave Windows&X-Emby-Device-Id=bd0e306e-c9df-4bf4-94c9-554fd434ed4a&X-Emby-Client-Version=4.9.3.0&X-Emby-Token=‌de17ec792a5b48429a71c8474d7dd778‌&X-Emby-Language=en-us. Source Ip: ‌192.168.1.7‌, UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/147.0.0.0 Safari/537.36 2026-04-14 20:07:51.830 Debug WebAppService-0HNKQHDL1QU55:00000001: http/1.1 Response 304 to ‌192.168.1.7‌. Time: 24ms. GET http://‌REDACTED‌/emby/web/configurationpage?name=CreditsDetectorConfiguration&v=4.9.3.0. 2026-04-14 20:07:51.870 Debug WebAppService-0HNKQHDL1QU57:00000001: http/1.1 Response completed after client disconnected to ‌192.168.1.7‌. Time: 62ms. GET http://‌REDACTED‌/emby/web/configurationpages?Name=CreditsDetectorConfiguration&X-Emby-Client=Emby Web&X-Emby-Device-Name=Brave Windows&X-Emby-Device-Id=bd0e306e-c9df-4bf4-94c9-554fd434ed4a&X-Emby-Client-Version=4.9.3.0&X-Emby-Token=‌de17ec792a5b48429a71c8474d7dd778‌&X-Emby-Language=en-us. 2026-04-14 20:07:51.917 Debug WebAppService-0HNKQHDL1QU5A:00000001: http/1.1 GET http://‌REDACTED‌/emby/web/configurationpage?name=CreditsDetectorConfigurationjs&v=4.9.3.0. Source Ip: ‌192.168.1.7‌, UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/147.0.0.0 Safari/537.36 2026-04-14 20:07:51.918 Debug WebAppService-0HNKQHDL1QU5A:00000001: http/1.1 Response 304 to ‌192.168.1.7‌. Time: 1ms. GET http://‌REDACTED‌/emby/web/configurationpage?name=CreditsDetectorConfigurationjs&v=4.9.3.0. 2026-04-14 20:07:51.941 Debug WebAppService-0HNKQHDL1QU5B:00000001: http/1.1 GET http://‌REDACTED‌/emby/web/configurationpage?name=CreditsDetectorConfigurationLoader&v=4.9.3.0. Source Ip: ‌192.168.1.7‌, UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/147.0.0.0 Safari/537.36 2026-04-14 20:07:51.941 Debug WebAppService-0HNKQHDL1QU5C:00000001: http/1.1 GET http://‌REDACTED‌/emby/web/configurationpage?name=CreditsDetectorConfigurationEvents&v=4.9.3.0. Source Ip: ‌192.168.1.7‌, UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/147.0.0.0 Safari/537.36 2026-04-14 20:07:51.941 Debug WebAppService-0HNKQHDL1QU5B:00000001: http/1.1 Response 304 to ‌192.168.1.7‌. Time: 1ms. GET http://‌REDACTED‌/emby/web/configurationpage?name=CreditsDetectorConfigurationLoader&v=4.9.3.0. 2026-04-14 20:07:51.941 Debug WebAppService-0HNKQHDL1QU5C:00000001: http/1.1 Response 304 to ‌192.168.1.7‌. Time: 1ms. GET http://‌REDACTED‌/emby/web/configurationpage?name=CreditsDetectorConfigurationEvents&v=4.9.3.0. 2026-04-14 20:07:51.943 Debug WebAppService-0HNKQHDL1QU5E:00000001: http/1.1 GET http://‌REDACTED‌/emby/web/configurationpage?name=CreditsDetectorConfigurationDataManager&v=4.9.3.0. Source Ip: ‌192.168.1.7‌, UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/147.0.0.0 Safari/537.36 2026-04-14 20:07:51.943 Debug WebAppService-0HNKQHDL1QU5F:00000001: http/1.1 GET http://‌REDACTED‌/emby/web/configurationpage?name=CreditsDetectorConfigurationSeriesManager&v=4.9.3.0. Source Ip: ‌192.168.1.7‌, UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/147.0.0.0 Safari/537.36 2026-04-14 20:07:51.943 Debug WebAppService-0HNKQHDL1QU5F:00000001: http/1.1 Response 304 to ‌192.168.1.7‌. Time: 1ms. GET http://‌REDACTED‌/emby/web/configurationpage?name=CreditsDetectorConfigurationSeriesManager&v=4.9.3.0. 2026-04-14 20:07:51.943 Debug WebAppService-0HNKQHDL1QU5E:00000001: http/1.1 Response 304 to ‌192.168.1.7‌. Time: 1ms. GET http://‌REDACTED‌/emby/web/configurationpage?name=CreditsDetectorConfigurationDataManager&v=4.9.3.0. 2026-04-14 20:07:51.944 Debug WebAppService-0HNKQHDL1QU5D:00000001: http/1.1 GET http://‌REDACTED‌/emby/web/configurationpage?name=CreditsDetectorConfigurationUtils&v=4.9.3.0. Source Ip: ‌192.168.1.7‌, UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/147.0.0.0 Safari/537.36 2026-04-14 20:07:51.945 Debug WebAppService-0HNKQHDL1QU5G:00000001: http/1.1 GET http://‌REDACTED‌/emby/web/configurationpage?name=CreditsDetectorConfigurationProcessingActions&v=4.9.3.0. Source Ip: ‌192.168.1.7‌, UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/147.0.0.0 Safari/537.36 2026-04-14 20:07:51.946 Debug WebAppService-0HNKQHDL1QU5G:00000001: http/1.1 Response 304 to ‌192.168.1.7‌. Time: 1ms. GET http://‌REDACTED‌/emby/web/configurationpage?name=CreditsDetectorConfigurationProcessingActions&v=4.9.3.0. 2026-04-14 20:07:51.946 Debug WebAppService-0HNKQHDL1QU5D:00000001: http/1.1 Response 304 to ‌192.168.1.7‌. Time: 6ms. GET http://‌REDACTED‌/emby/web/configurationpage?name=CreditsDetectorConfigurationUtils&v=4.9.3.0. 2026-04-14 20:07:51.948 Debug WebAppService-0HNKQHDL1QU5H:00000001: http/1.1 GET http://‌REDACTED‌/emby/web/configurationpage?name=CreditsDetectorConfigurationProgressMonitor&v=4.9.3.0. Source Ip: ‌192.168.1.7‌, UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/147.0.0.0 Safari/537.36 2026-04-14 20:07:51.949 Debug WebAppService-0HNKQHDL1QU5H:00000001: http/1.1 Response 304 to ‌192.168.1.7‌. Time: 1ms. GET http://‌REDACTED‌/emby/web/configurationpage?name=CreditsDetectorConfigurationProgressMonitor&v=4.9.3.0. 2026-04-14 20:07:51.949 Debug WebAppService-0HNKQHDL1QU5I:00000001: http/1.1 GET http://‌REDACTED‌/emby/web/configurationpage?name=CreditsDetectorConfigurationChapterEditManager&v=4.9.3.0. Source Ip: ‌192.168.1.7‌, UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/147.0.0.0 Safari/537.36 2026-04-14 20:07:51.950 Debug WebAppService-0HNKQHDL1QU5J:00000001: http/1.1 GET http://‌REDACTED‌/emby/web/configurationpage?name=CreditsDetectorConfigurationTracerManager&v=4.9.3.0. Source Ip: ‌192.168.1.7‌, UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/147.0.0.0 Safari/537.36 2026-04-14 20:07:51.950 Debug WebAppService-0HNKQHDL1QU5I:00000001: http/1.1 Response 304 to ‌192.168.1.7‌. Time: 1ms. GET http://‌REDACTED‌/emby/web/configurationpage?name=CreditsDetectorConfigurationChapterEditManager&v=4.9.3.0. 2026-04-14 20:07:51.951 Debug WebAppService-0HNKQHDL1QU5J:00000001: http/1.1 Response 304 to ‌192.168.1.7‌. Time: 1ms. GET http://‌REDACTED‌/emby/web/configurationpage?name=CreditsDetectorConfigurationTracerManager&v=4.9.3.0. 2026-04-14 20:07:51.952 Debug WebAppService-0HNKQHDL1QU5K:00000001: http/1.1 GET http://‌REDACTED‌/emby/web/configurationpage?name=CreditsDetectorConfigurationAutoSkipManager&v=4.9.3.0. Source Ip: ‌192.168.1.7‌, UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/147.0.0.0 Safari/537.36 2026-04-14 20:07:51.953 Debug WebAppService-0HNKQHDL1QU5L:00000001: http/1.1 GET http://‌REDACTED‌/emby/web/configurationpage?name=CreditsDetectorConfigurationMarkersManager&v=4.9.3.0. Source Ip: ‌192.168.1.7‌, UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/147.0.0.0 Safari/537.36 2026-04-14 20:07:51.953 Debug WebAppService-0HNKQHDL1QU5K:00000001: http/1.1 Response 304 to ‌192.168.1.7‌. Time: 2ms. GET http://‌REDACTED‌/emby/web/configurationpage?name=CreditsDetectorConfigurationAutoSkipManager&v=4.9.3.0. 2026-04-14 20:07:51.954 Debug WebAppService-0HNKQHDL1QU5L:00000001: http/1.1 Response 304 to ‌192.168.1.7‌. Time: 1ms. GET http://‌REDACTED‌/emby/web/configurationpage?name=CreditsDetectorConfigurationMarkersManager&v=4.9.3.0. 2026-04-14 20:07:51.962 Debug WebAppService-0HNKQHDL1QU5M:00000001: http/1.1 GET http://‌REDACTED‌/emby/web/configurationpage?name=CreditsDetectorConfigurationRulesManager&v=4.9.3.0. Source Ip: ‌192.168.1.7‌, UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/147.0.0.0 Safari/537.36 2026-04-14 20:07:51.962 Debug WebAppService-0HNKQHDL1QU5N:00000001: http/1.1 GET http://‌REDACTED‌/emby/web/configurationpage?name=CreditsDetectorConfigurationBackupManager&v=4.9.3.0. Source Ip: ‌192.168.1.7‌, UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/147.0.0.0 Safari/537.36 2026-04-14 20:07:51.963 Debug WebAppService-0HNKQHDL1QU5N:00000001: http/1.1 Response 304 to ‌192.168.1.7‌. Time: 1ms. GET http://‌REDACTED‌/emby/web/configurationpage?name=CreditsDetectorConfigurationBackupManager&v=4.9.3.0. 2026-04-14 20:07:51.963 Debug WebAppService-0HNKQHDL1QU5M:00000001: http/1.1 Response 304 to ‌192.168.1.7‌. Time: 1ms. GET http://‌REDACTED‌/emby/web/configurationpage?name=CreditsDetectorConfigurationRulesManager&v=4.9.3.0. ------------------------ Configuration page is mostly empty ----------------------- Error popup

Yeah, having the marker is still useful. It's up to the devs to make them "actionable"

Well "When you run PRAGMA synchronous; in your terminal or SQL editor, you are only seeing the setting for your own connection, not Emby’s." No way to play much with the SQLite settings outside Emby then as I understand.

Thank you Luke. Mama is fine today. Alzheimer's. You just never know when the lightning is going to strike. I appreciate your kind words! You have always been so kind and patient and it is much appreciated.

HI, this should be resolved in the server beta channel, and the fix will be included in the next stable release. Thanks.

HI, yes I really like this idea. The problem that makes it complicated for us is that sometimes turning on subtitles requires an entire stream change, meaning that it requires transcoding on the server. I don't think it would be ideal to have to suddenly reset the whole stream. On the other hand, we could have options to do this sort of thing when a stream change isn't required, but then users will be left wondering why they sometimes get the subtitles and sometimes don't. So either way we do it it's like we're asking for pain.

I owe you all an update: my problem had nothing to do with Emby or my network. You can read all about my adventure over here: https://forums.servethehome.com/index.php?threads/lsi-9400-16i-power-on-or-device-reset-occurred.55002/ but in summary, the backplane in my server chassis (Gooxi RMC4136-670-HSE chassis) had an old firmware that had issues with some health checking commands while drives were loaded (reading or writing). If I was streaming something from it and a TrueNAS health check occurred (which turns out is every 90 minutes in 25.10) then it would cause the drives to start timing out leading to ZFS halting the pool while it recovers the drives and while that is happening all further reading is blocked which from Emby's perspective looked like a network timeout. It would take about 5 minutes for all the drives to recover and then it would be fine until the next health check. Gooxi was able to provide a newer firmware and it has completely resolved the issue.

Hi. Please change your username on this forum to not be your email address. Thanks.

New bugfix release - Version 3.3.2.1 Download .dll and full release notes: https://github.com/soderlund91/HomeScreenCompanion/releases/tag/v3.3.2.1 This update contains fixes to match Emby server 4.10.0.10 and other bugs. IMPORTANT! Minimum required Emby server v4.10.0.10 Note Included a .NET V6 release, this is for MacOS or legacy support. This version is NOT tested. Release notes Fixes Updated Playstate function to work with Emby 4.10.0.10 Fixed an issue where private/locked list from MDBList didn't get accepted by the plugin even though correct API key was entered. HomeScreenCompanion.dll HomeScreenCompanion_NET6_MacOS.dll

Let's not play diplomat it's tacky. Most want this and have wanted this. Fixing the search function should be relatively straightforward since the bulk of the code is already there.

Hello. I'm experiencing the same issue with subtitles positioned in the upper left corner for some time. Is there any ETA for a fix? I've temporarily switched to another streaming app but it's frustrating to be forced to do this. Thank you.

The recently released Firefox MKV support doesn't allow for partial retrieval of the video content it seems. You can disable it by going to about:config and changing media.mkv.enabled to false.

My solution for a similar problem - maybe this helps someone! I wanted to move my Emby Server from my Synology NAS (because of better transcoding performance) to an Ubuntu server (virtual machine) that already runs multiple Docker containers. All my media should remain on the NAS and will be accessed via NFS. 1. I made a backup of everything inside Emby's /config folder on my NAS and copied it over to the Emby /config folder on my Ubuntu server. 2. I mounted the NFT share on my NAS to /mnt/nas/video on the Ubuntu server. 3. In docker-compose.yml I just defined a volume (/volume1/video) which is the same as it used to be on my NAS. This way I did not need to change anything inside the Emby DB. Even if I should move my media to a new location, I just need to update the docker volume entry. Here's the docker-compose.yml emby: image: emby/embyserver:latest container_name: embyserver network_mode: host environment: - UID=1000 - GID=1000 - GIDLIST=123 # Matches 'render' group ID volumes: - /opt/emby/config:/config - /mnt/nas/video:/volume1/video devices: - /dev/dri/renderD129:/dev/dri/renderD129 # Direct path to the Iris Xe restart: unless-stopped

Even if Emby's "heritage" is to be an all-purpose app, it does a pretty bad job keeping that "heritage". It's a matter of focused development and allocating resources where it matters when you want to deliver THE BEST product and experience. If you're doing gazillion things at once, some of them subpar, it's obvious that you don't have resources to deliver the best experience top to bottom. Ok, some of the user will prefer an "all-in-one" solution, that means they aren't "heavy" consumers of any of the media type, so they are fine with having just basic functionality for everything. If you are rising above entry-level into any of the media type (photos, music, audiobooks etc) you will notice that having a basic, sub-par "all-in-one" solution doesn't cut it anymore, because the experience it's just bad, featureless etc. We can dissect each media type and prove that it needs dedicated efforts and focused UI/UX for any consumption that rises above the absolute minimal, basic level. Emby It's just a nice movie server, that's it. Music comes with a "good enough" mindset and everything else (photos, audiobooks etc) it's meh ...

In my opinion, for users who pay for Emby Premiere every month, things should be simple. When something breaks right after activating Premiere, they shouldn’t have to read a long guide on how to manually create logs, worry about whether those logs contain sensitive information, and then post them publicly on a forum. It’s an app you install and run. It should be simple, fast, and user-friendly. There should be a single button inside the app to send a problem report directly and receive proper support. Can you really not live without that forum?