Emby Unresponsive To Users Shortly After Server Setup

[Savannah Mohawk 0]

Hello there,
Reaching out to see if anyone can assist with the issue I have been having with my Emby Server becoming unresponsive to users after Server setup.
Currently running Emby Server Version: 4.8.11.0 on Windows Server 2025 Version 24H2 - OS Build 26100.3476
This is running on a Server running Xeon E5-2670v3 / 16GB Ram / SSD Storage (81.4gb of 99.2 free)
OS is a fresh Windows Server install with only Emby installed and running.
Media library is stored and served from a RAID 10 NAS connected via dual 10Gbps pair bonded network connection..

I am able to install Emby and configure Users, Networking, and Settings.  I am able to import my media but after being up for around 12 to 24 hours the server appears to hang for Users trying to use the Server, be it locally (on box), Local (same internal network) or remote (external network).  This is presented as the User being able to login but not seeing any of the available media only a spinning blue circle.  (See Screen-Shot-01 attached).  Once this behavior starts server continues to show hang behavior even after server restart immediately.

I have tried the following:
-Rebooted Server via the Reboot Emby Server tray option.
-Rebooted entire OS and allowed Server to fully start and Emby to launch and fully boot.
-Reformatted Drive, Re-Installed Server OS and Reinstalled Emby fresh, imported Media, and let Server fully import and Scan Library Files until finished (24 hours)
-Used different Server Hardware (CPU, RAM, SSD Drive, etc), formated Drive, Re-Installed Server OS and Reinstalled Emby fresh.  Imported Media one folder at time (Movies, TV Shows, etc See Library-Import-01 screen shot attached for visual) one at a time and let Server fully import and Scan Library Files for each Major Folder before adding the next to the library.

No large errors have stuck out to me in the Logs (Downloaded via Web Interface and attached, Logs.zip)
CPU / Memory / Disk / Ethernet not showing being overly taxed - (See screen shot Performance-01)
During import setting Generate video preview thumbnails and Generate intro video markers to "Never"
(Screen shot Import-01)
 

logs.zip

[Abobader 3464]

Hello Savannah Mohawk,

** This is an auto reply **

Please wait for someone from staff support or our members to reply to you.

It's recommended to provide more info, as it explain in this thread:

Thank you.

Emby Team

[Luke 42078]

HI, what time did the problem occur?

[Savannah Mohawk 0]

Still occurring and started occurring about 1800 EDT yesterday 2025-03-25

[Carlo 4561]

Only one of the logs had anything of substance to it and that showed primarily all details of library scanning.

Your last log shows these toward the bottom:

2025-03-25 15:50:39.763 Info Server: http/1.1 POST http://localhost:8096/emby/Library/VirtualFolders/LibraryOptions?X-Emby-Client=Emby Web&X-Emby-Device-Name=Google Chrome Windows&X-Emby-Device-Id=ee64b2e7-6030-4957-90e8-93c49f00713a&X-Emby-Client-Version=4.8.11.0&X-Emby-Token=x_secret1_x&X-Emby-Language=en-us&reqformat=json. Source Ip: ::1, UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/134.0.0.0 Safari/537.36
2025-03-25 15:56:23.190 Info Server: http/1.1 Response 500 to ::1. Time: 1580297ms. GET http://localhost:8096/emby/Users/fd59c73b22324688bc6bb488b66013d6/Items/Latest?Limit=16&Fields=BasicSyncInfo,CanDelete,CanDownload,PrimaryImageAspectRatio,ProductionYear&ImageTypeLimit=1&EnableImageTypes=Primary,Backdrop,Thumb&ParentId=14987&X-Emby-Client=Emby Web&X-Emby-Device-Name=Google Chrome Windows&X-Emby-Device-Id=ee64b2e7-6030-4957-90e8-93c49f00713a&X-Emby-Client-Version=4.8.11.0&X-Emby-Token=x_secret1_x&X-Emby-Language=en-us
2025-03-25 15:56:23.199 Info Server: http/1.1 Response 204 to ::1. Time: 343436ms. POST http://localhost:8096/emby/Library/VirtualFolders/LibraryOptions?X-Emby-Client=Emby Web&X-Emby-Device-Name=Google Chrome Windows&X-Emby-Device-Id=ee64b2e7-6030-4957-90e8-93c49f00713a&X-Emby-Client-Version=4.8.11.0&X-Emby-Token=x_secret1_x&X-Emby-Language=en-us&reqformat=json
2025-03-25 15:56:23.199 Info Server: http/2 Response 500 to host1. Time: 1128981ms. GET https://host2:6060/emby/Users/593e0cf7f5884c00ad3bca19805c8d2d/Views?X-Emby-Client=Emby Web&X-Emby-Device-Name=Firefox Windows&X-Emby-Device-Id=9882479f-7e54-451c-9267-425bedb71507&X-Emby-Client-Version=4.8.11.0&X-Emby-Token=x_secret7_x&X-Emby-Language=en-us
2025-03-25 15:56:23.200 Info Server: http/2 Response 500 to host1. Time: 1098295ms. GET https://host2:6060/emby/Users/593e0cf7f5884c00ad3bca19805c8d2d/Views?X-Emby-Client=Emby Web&X-Emby-Device-Name=Firefox Windows&X-Emby-Device-Id=9882479f-7e54-451c-9267-425bedb71507&X-Emby-Client-Version=4.8.11.0&X-Emby-Token=x_secret7_x&X-Emby-Language=en-us
2025-03-25 15:56:23.200 Info Server: http/2 Response 500 to host1. Time: 1536014ms. GET https://host2:6060/emby/Users/593e0cf7f5884c00ad3bca19805c8d2d/Views?X-Emby-Client=Emby Web&X-Emby-Device-Name=Firefox Windows&X-Emby-Device-Id=9882479f-7e54-451c-9267-425bedb71507&X-Emby-Client-Version=4.8.11.0&X-Emby-Token=x_secret7_x&X-Emby-Language=en-us
2025-03-25 15:56:23.201 Info Server: http/2 Response 500 to host1. Time: 1570523ms. GET https://host2:6060/emby/Users/fd59c73b22324688bc6bb488b66013d6/Views?X-Emby-Client=Emby Web&X-Emby-Device-Name=Firefox Windows&X-Emby-Device-Id=9882479f-7e54-451c-9267-425bedb71507&X-Emby-Client-Version=4.8.11.0&X-Emby-Token=x_secret4_x&X-Emby-Language=en-us
2025-03-25 15:56:23.202 Info Server: http/2 Response 500 to host1. Time: 436827ms. GET https://host2:6060/emby/Users/593e0cf7f5884c00ad3bca19805c8d2d/Views?X-Emby-Client=Emby Web&X-Emby-Device-Name=Firefox Windows&X-Emby-Device-Id=9882479f-7e54-451c-9267-425bedb71507&X-Emby-Client-Version=4.8.11.0&X-Emby-Token=x_secret7_x&X-Emby-Language=en-us
2025-03-25 15:56:23.213 Info TaskManager: Download OCR Data Completed after 26 minute(s) and 19 seconds
2025-03-25 15:56:23.257 Info App: Sqlite: 284 - automatic index on LastWatchedEpisodes(SeriesPresentationUniqueKey)
2025-03-25 15:56:23.570 Info CodecManager: CodecList:
2025-03-25 15:56:23.570 Info TaskManager: Hardware Detection Completed after 26 minute(s) and 23 seconds
2025-03-25 16:19:02.964 Info Server: http/1.1 Response 500 to ::1. Time: 2940069ms. GET http://localhost:8096/emby/Users/fd59c73b22324688bc6bb488b66013d6/Items/Latest?Limit=16&Fields=BasicSyncInfo,CanDelete,CanDownload,PrimaryImageAspectRatio,ProductionYear&ImageTypeLimit=1&EnableImageTypes=Primary,Backdrop,Thumb&ParentId=6554&X-Emby-Client=Emby Web&X-Emby-Device-Name=Google Chrome Windows&X-Emby-Device-Id=ee64b2e7-6030-4957-90e8-93c49f00713a&X-Emby-Client-Version=4.8.11.0&X-Emby-Token=x_secret1_x&X-Emby-Language=en-us
2025-03-25 16:19:03.009 Info Server: http/1.1 Response 500 to ::1. Time: 2940242ms. GET http://localhost:8096/emby/Users/fd59c73b22324688bc6bb488b66013d6/Items/Latest?Limit=16&Fields=BasicSyncInfo,CanDelete,CanDownload,PrimaryImageAspectRatio,ProductionYear&ImageTypeLimit=1&EnableImageTypes=Primary,Backdrop,Thumb&ParentId=1888&X-Emby-Client=Emby Web&X-Emby-Device-Name=Google Chrome Windows&X-Emby-Device-Id=ee64b2e7-6030-4957-90e8-93c49f00713a&X-Emby-Client-Version=4.8.11.0&X-Emby-Token=x_secret1_x&X-Emby-Language=en-us
2025-03-25 16:19:03.098 Info Server: http/1.1 Response 500 to ::1. Time: 2940240ms. GET http://localhost:8096/emby/Users/fd59c73b22324688bc6bb488b66013d6/Items/Latest?Limit=16&Fields=BasicSyncInfo,CanDelete,CanDownload,PrimaryImageAspectRatio,ProductionYear&ImageTypeLimit=1&EnableImageTypes=Primary,Backdrop,Thumb&ParentId=2911&X-Emby-Client=Emby Web&X-Emby-Device-Name=Google Chrome Windows&X-Emby-Device-Id=ee64b2e7-6030-4957-90e8-93c49f00713a&X-Emby-Client-Version=4.8.11.0&X-Emby-Token=x_secret1_x&X-Emby-Language=en-us
2025-03-25 16:19:03.146 Info Server: http/1.1 Response 500 to ::1. Time: 2940248ms. GET http://localhost:8096/emby/Users/fd59c73b22324688bc6bb488b66013d6/Items/Latest?Limit=16&Fields=BasicSyncInfo,CanDelete,CanDownload,PrimaryImageAspectRatio,ProductionYear&ImageTypeLimit=1&EnableImageTypes=Primary,Backdrop,Thumb&ParentId=3476&X-Emby-Client=Emby Web&X-Emby-Device-Name=Google Chrome Windows&X-Emby-Device-Id=ee64b2e7-6030-4957-90e8-93c49f00713a&X-Emby-Client-Version=4.8.11.0&X-Emby-Token=x_secret1_x&X-Emby-Language=en-us
2025-03-25 16:19:03.147 Info Server: http/1.1 Response 500 to ::1. Time: 2940343ms. GET http://localhost:8096/emby/Users/fd59c73b22324688bc6bb488b66013d6/Items/Latest?Limit=16&Fields=BasicSyncInfo,CanDelete,CanDownload,PrimaryImageAspectRatio,ProductionYear&ImageTypeLimit=1&EnableImageTypes=Primary,Backdrop,Thumb&ParentId=1902&X-Emby-Client=Emby Web&X-Emby-Device-Name=Google Chrome Windows&X-Emby-Device-Id=ee64b2e7-6030-4957-90e8-93c49f00713a&X-Emby-Client-Version=4.8.11.0&X-Emby-Token=x_secret1_x&X-Emby-Language=en-us

You can see downloading OCR data and doing the standard hardware detection taking 26 minutes.
You can see the Response 500 codes and long ms times some of the http requests are taking.

Keep an eye on your server log to see what's going on with the server.
It may very well seem to run very slow while scanning libraries as trying to display a library while it's doing the initial scan puts even more burden on the tasks running on the server as it then has to download graphics, casts, etc and this might appear to be failing but there could be so much going on it just appears that way.

Carlo

[Savannah Mohawk 0]

Appreciate you taking a look Carlos.  

Still seeing the slowness. When a user logs in they might see the Library Folders after letting it sit for 5 to 10 minutes but nothing plays or responds when selected.

I'm giving it another 48 hours to chew on all the media even though again I don't see much resource usage on the Emby server.

For a frame of reference I spooled up a Jellyfin server with a copy of the same media on similar server hardware about an hour after my original post and my users are using that now without issue.

Shame to waste the Preimere license but I may switch the Jellyfin server if I still I can't play any media.

Appreciate any other fixes or ideas.

Is there a media library database limitation I missed?  Is Emby only meant for smaller libraries?

Total library media content with all folders is probably in the 15 Tb range but I assume after the initial processing time that shouldn't matter.