hawkeye09 0 Posted December 1, 2025 Posted December 1, 2025 Hi, I have two emby instances running and i am having problems since updating to version 4.9.1.90. One instance is windows and was updated around 3 weeks ago. Since then i have found randomly it will go to a blank screen spinning state. the only way to fix it was to kill the emby program in task manager and start the instance back up again. I have tried to reboot the server uninstall emby and restore with a backup with the same problem. The other instance which i am running was Ubuntu which i didnt upgrade which was version 4.8 and has no issues. i recently upgraded its to 4.9.1.90 and now i am find the same problems as i am having on windows. embyserver-63900136114.txt
filecore 8 Posted December 29, 2025 Posted December 29, 2025 (edited) Just chiming in to say that this has been happening for me too, over the past month or so (using LSIO image on Docker on Ubuntu Server LTS). According to my images, I upgraded thusly to 4.9.1.90 - I don't recall what the previous version was but it wasn't too far behind: $ docker images | grep -i emby lscr.io/linuxserver/emby latest 0d398816babf 2 weeks ago 840MB linuxserver/emby latest af67644199bf 5 weeks ago 840MB It is happening across all client types (Samsung TV, official Android app, web browser), as well as both locally and via remote access. I've been examining Docker logs and Emby server logs but can't see anything (there are plenty of errors about malformed XML in series data, but I assume that's unrelated). I will try switching back to the previous version in Docker and see if that resolves things: oxide@cobalt:~/docker/emby$ docker tag af67644199bf linuxserver/emby:rollback oxide@cobalt:~/docker/emby$ nano docker-compose.yaml oxide@cobalt:~/docker/emby$ oxide@cobalt:~/docker/emby$ docker compose up -d --force-recreate [+] Running 1/2 s⠧ Network emby_default Created 0.7s s✔ Container emby Started 0.6s oxide@cobalt:~/docker/emby$ docker inspect -f 'Image={{.Config.Image}} ImageID={{.Image}}' emby Image=linuxserver/emby:rollback ImageID=sha256:af67644199bf39ed038f77fb95b4d725713ee50b596dbd3c469f96e9337542c2 oxide@cobalt:~/docker/emby$ docker logs emby | grep -E "Linuxserver.io version|Emby Server" | head -n 10 Connection to localhost (127.0.0.1) 8096 port [tcp/*] succeeded! Linuxserver.io version: 4.9.1.90-ls261 Info Main: Emby Server 4.9.1.90 Info App: Emby Server Version: 4.9.1.90 Info App: Emby Server 4.9.1.90 Info TaskManager: Daily trigger for Emby Server Backup set to fire at 12/30/2025 00:10:00, which is 674.579130525 minutes from now. Info Notifications: Registering event nofitier Emby Server User Notifications and those containers: oxide@cobalt:~/docker/emby$ docker inspect lscr.io/linuxserver/emby:latest --format=' Image ID: {{.Id}} Created: {{.Created}} OS/Arch: {{.Os}}/{{.Architecture}} Labels: {{range $k,$v := .Config.Labels}} {{$k}}={{$v}} {{end}} ' Image ID: sha256:0d398816babf4c891a25661f580f5255d519f821a9718d03eec01c5ce15bd2bb Created: 2025-12-13T16:53:48.322970769Z OS/Arch: linux/amd64 Labels: build_version=Linuxserver.io version:- 4.9.1.90-ls263 Build-date:- 2025-12-13T16:51:19+00:00 maintainer=thelamer org.opencontainers.image.authors=linuxserver.io org.opencontainers.image.created=2025-12-13T16:51:19+00:00 org.opencontainers.image.description=[Emby](https://emby.media/) organizes video, music, live TV, and photos from personal media libraries and streams them to smart TVs, streaming boxes and mobile devices. This container is packaged as a standalone emby Media Server. org.opencontainers.image.documentation=https://docs.linuxserver.io/images/docker-emby org.opencontainers.image.licenses=GPL-3.0-only org.opencontainers.image.ref.name=331904edd48e4c0fb2402079d7736527acae55c5 org.opencontainers.image.revision=331904edd48e4c0fb2402079d7736527acae55c5 org.opencontainers.image.source=https://github.com/linuxserver/docker-emby org.opencontainers.image.title=Emby org.opencontainers.image.url=https://github.com/linuxserver/docker-emby/packages org.opencontainers.image.vendor=linuxserver.io org.opencontainers.image.version=4.9.1.90-ls263 oxide@cobalt:~/docker/emby$ docker inspect linuxserver/emby:rollback \ --format=' Image ID: {{.Id}} Created: {{.Created}} OS/Arch: {{.Os}}/{{.Architecture}} Labels: {{range $k,$v := .Config.Labels}} {{$k}}={{$v}} {{end}} ' Image ID: sha256:af67644199bf39ed038f77fb95b4d725713ee50b596dbd3c469f96e9337542c2 Created: 2025-11-20T21:30:05.908413346Z OS/Arch: linux/amd64 Labels: build_version=Linuxserver.io version:- 4.9.1.90-ls261 Build-date:- 2025-11-20T21:28:35+00:00 maintainer=thelamer org.opencontainers.image.authors=linuxserver.io org.opencontainers.image.created=2025-11-20T21:28:35+00:00 org.opencontainers.image.description=[Emby](https://emby.media/) organizes video, music, live TV, and photos from personal media libraries and streams them to smart TVs, streaming boxes and mobile devices. This container is packaged as a standalone emby Media Server. org.opencontainers.image.documentation=https://docs.linuxserver.io/images/docker-emby org.opencontainers.image.licenses=GPL-3.0-only org.opencontainers.image.ref.name=8dc3d16cb47f9aa9588b6c6147b44265f500af5c org.opencontainers.image.revision=8dc3d16cb47f9aa9588b6c6147b44265f500af5c org.opencontainers.image.source=https://github.com/linuxserver/docker-emby org.opencontainers.image.title=Emby org.opencontainers.image.url=https://github.com/linuxserver/docker-emby/packages org.opencontainers.image.vendor=linuxserver.io org.opencontainers.image.version=4.9.1.90-ls261 oxide@cobalt:~/docker/emby$ docker inspect linuxserver/emby:latest --format=' Image ID: {{.Id}} Created: {{.Created}} OS/Arch: {{.Os}}/{{.Architecture}} Labels: {{range $k,$v := .Config.Labels}} {{$k}}={{$v}} {{end}} ' Image ID: sha256:af67644199bf39ed038f77fb95b4d725713ee50b596dbd3c469f96e9337542c2 Created: 2025-11-20T21:30:05.908413346Z OS/Arch: linux/amd64 Labels: build_version=Linuxserver.io version:- 4.9.1.90-ls261 Build-date:- 2025-11-20T21:28:35+00:00 maintainer=thelamer org.opencontainers.image.authors=linuxserver.io org.opencontainers.image.created=2025-11-20T21:28:35+00:00 org.opencontainers.image.description=[Emby](https://emby.media/) organizes video, music, live TV, and photos from personal media libraries and streams them to smart TVs, streaming boxes and mobile devices. This container is packaged as a standalone emby Media Server. org.opencontainers.image.documentation=https://docs.linuxserver.io/images/docker-emby org.opencontainers.image.licenses=GPL-3.0-only org.opencontainers.image.ref.name=8dc3d16cb47f9aa9588b6c6147b44265f500af5c org.opencontainers.image.revision=8dc3d16cb47f9aa9588b6c6147b44265f500af5c org.opencontainers.image.source=https://github.com/linuxserver/docker-emby org.opencontainers.image.title=Emby org.opencontainers.image.url=https://github.com/linuxserver/docker-emby/packages org.opencontainers.image.vendor=linuxserver.io org.opencontainers.image.version=4.9.1.90-ls261 embyserver.txt Edited December 29, 2025 by filecore
Luke 42077 Posted December 29, 2025 Posted December 29, 2025 8 hours ago, filecore said: Just chiming in to say that this has been happening for me too, over the past month or so (using LSIO image on Docker on Ubuntu Server LTS). According to my images, I upgraded thusly to 4.9.1.90 - I don't recall what the previous version was but it wasn't too far behind: $ docker images | grep -i emby lscr.io/linuxserver/emby latest 0d398816babf 2 weeks ago 840MB linuxserver/emby latest af67644199bf 5 weeks ago 840MB It is happening across all client types (Samsung TV, official Android app, web browser), as well as both locally and via remote access. I've been examining Docker logs and Emby server logs but can't see anything (there are plenty of errors about malformed XML in series data, but I assume that's unrelated). I will try switching back to the previous version in Docker and see if that resolves things: oxide@cobalt:~/docker/emby$ docker tag af67644199bf linuxserver/emby:rollback oxide@cobalt:~/docker/emby$ nano docker-compose.yaml oxide@cobalt:~/docker/emby$ oxide@cobalt:~/docker/emby$ docker compose up -d --force-recreate [+] Running 1/2 s⠧ Network emby_default Created 0.7s s✔ Container emby Started 0.6s oxide@cobalt:~/docker/emby$ docker inspect -f 'Image={{.Config.Image}} ImageID={{.Image}}' emby Image=linuxserver/emby:rollback ImageID=sha256:af67644199bf39ed038f77fb95b4d725713ee50b596dbd3c469f96e9337542c2 oxide@cobalt:~/docker/emby$ docker logs emby | grep -E "Linuxserver.io version|Emby Server" | head -n 10 Connection to localhost (127.0.0.1) 8096 port [tcp/*] succeeded! Linuxserver.io version: 4.9.1.90-ls261 Info Main: Emby Server 4.9.1.90 Info App: Emby Server Version: 4.9.1.90 Info App: Emby Server 4.9.1.90 Info TaskManager: Daily trigger for Emby Server Backup set to fire at 12/30/2025 00:10:00, which is 674.579130525 minutes from now. Info Notifications: Registering event nofitier Emby Server User Notifications and those containers: oxide@cobalt:~/docker/emby$ docker inspect lscr.io/linuxserver/emby:latest --format=' Image ID: {{.Id}} Created: {{.Created}} OS/Arch: {{.Os}}/{{.Architecture}} Labels: {{range $k,$v := .Config.Labels}} {{$k}}={{$v}} {{end}} ' Image ID: sha256:0d398816babf4c891a25661f580f5255d519f821a9718d03eec01c5ce15bd2bb Created: 2025-12-13T16:53:48.322970769Z OS/Arch: linux/amd64 Labels: build_version=Linuxserver.io version:- 4.9.1.90-ls263 Build-date:- 2025-12-13T16:51:19+00:00 maintainer=thelamer org.opencontainers.image.authors=linuxserver.io org.opencontainers.image.created=2025-12-13T16:51:19+00:00 org.opencontainers.image.description=[Emby](https://emby.media/) organizes video, music, live TV, and photos from personal media libraries and streams them to smart TVs, streaming boxes and mobile devices. This container is packaged as a standalone emby Media Server. org.opencontainers.image.documentation=https://docs.linuxserver.io/images/docker-emby org.opencontainers.image.licenses=GPL-3.0-only org.opencontainers.image.ref.name=331904edd48e4c0fb2402079d7736527acae55c5 org.opencontainers.image.revision=331904edd48e4c0fb2402079d7736527acae55c5 org.opencontainers.image.source=https://github.com/linuxserver/docker-emby org.opencontainers.image.title=Emby org.opencontainers.image.url=https://github.com/linuxserver/docker-emby/packages org.opencontainers.image.vendor=linuxserver.io org.opencontainers.image.version=4.9.1.90-ls263 oxide@cobalt:~/docker/emby$ docker inspect linuxserver/emby:rollback \ --format=' Image ID: {{.Id}} Created: {{.Created}} OS/Arch: {{.Os}}/{{.Architecture}} Labels: {{range $k,$v := .Config.Labels}} {{$k}}={{$v}} {{end}} ' Image ID: sha256:af67644199bf39ed038f77fb95b4d725713ee50b596dbd3c469f96e9337542c2 Created: 2025-11-20T21:30:05.908413346Z OS/Arch: linux/amd64 Labels: build_version=Linuxserver.io version:- 4.9.1.90-ls261 Build-date:- 2025-11-20T21:28:35+00:00 maintainer=thelamer org.opencontainers.image.authors=linuxserver.io org.opencontainers.image.created=2025-11-20T21:28:35+00:00 org.opencontainers.image.description=[Emby](https://emby.media/) organizes video, music, live TV, and photos from personal media libraries and streams them to smart TVs, streaming boxes and mobile devices. This container is packaged as a standalone emby Media Server. org.opencontainers.image.documentation=https://docs.linuxserver.io/images/docker-emby org.opencontainers.image.licenses=GPL-3.0-only org.opencontainers.image.ref.name=8dc3d16cb47f9aa9588b6c6147b44265f500af5c org.opencontainers.image.revision=8dc3d16cb47f9aa9588b6c6147b44265f500af5c org.opencontainers.image.source=https://github.com/linuxserver/docker-emby org.opencontainers.image.title=Emby org.opencontainers.image.url=https://github.com/linuxserver/docker-emby/packages org.opencontainers.image.vendor=linuxserver.io org.opencontainers.image.version=4.9.1.90-ls261 oxide@cobalt:~/docker/emby$ docker inspect linuxserver/emby:latest --format=' Image ID: {{.Id}} Created: {{.Created}} OS/Arch: {{.Os}}/{{.Architecture}} Labels: {{range $k,$v := .Config.Labels}} {{$k}}={{$v}} {{end}} ' Image ID: sha256:af67644199bf39ed038f77fb95b4d725713ee50b596dbd3c469f96e9337542c2 Created: 2025-11-20T21:30:05.908413346Z OS/Arch: linux/amd64 Labels: build_version=Linuxserver.io version:- 4.9.1.90-ls261 Build-date:- 2025-11-20T21:28:35+00:00 maintainer=thelamer org.opencontainers.image.authors=linuxserver.io org.opencontainers.image.created=2025-11-20T21:28:35+00:00 org.opencontainers.image.description=[Emby](https://emby.media/) organizes video, music, live TV, and photos from personal media libraries and streams them to smart TVs, streaming boxes and mobile devices. This container is packaged as a standalone emby Media Server. org.opencontainers.image.documentation=https://docs.linuxserver.io/images/docker-emby org.opencontainers.image.licenses=GPL-3.0-only org.opencontainers.image.ref.name=8dc3d16cb47f9aa9588b6c6147b44265f500af5c org.opencontainers.image.revision=8dc3d16cb47f9aa9588b6c6147b44265f500af5c org.opencontainers.image.source=https://github.com/linuxserver/docker-emby org.opencontainers.image.title=Emby org.opencontainers.image.url=https://github.com/linuxserver/docker-emby/packages org.opencontainers.image.vendor=linuxserver.io org.opencontainers.image.version=4.9.1.90-ls261 embyserver.txt 560.7 kB · 0 downloads Hi, can you try our official Docker container and let us know how things compare? Thanks.
filecore 8 Posted December 29, 2025 Posted December 29, 2025 I am now running it with the emby/embyserver image (had to recreate the compose because it seems the LSIO and Emby official images aren't drop-in compatible). $ docker images | grep -i emby emby/embyserver latest 8aa3c0224736 7 weeks ago 739MB $ docker pull emby/embyserver Using default tag: latest latest: Pulling from emby/embyserver Digest: sha256:50284133433841756686a8da2bb3122a7e2944546d74297f12dc700a731e5e26 Status: Image is up to date for emby/embyserver:latest docker.io/emby/embyserver:latest Seems like both images are on 4.9.1.90, so I'll give it a whirl for a couple of days and let you know if the same issues continue to persist. Just out of curiosity, since I was lazy and didn't realise how subtly different the LSIO image was... what's the link between you and them? Do they just package whatever they feel like, or is there some sort of two-way communication going on? Especially now if there's something flaky with their version but it doesn't reproduce in the official one.
filecore 8 Posted December 29, 2025 Posted December 29, 2025 (edited) Well it seems like I can already update you. Started the fresh server, tried to open a file on Android, nothing. Figured it might be stale data on the client, cleared cache and data from the app, still nothing. Just a spinner and a blank UI. Same thing whether I added my subdomain via the internet, or just via local IP:port. Edited December 29, 2025 by filecore
Luke 42077 Posted December 29, 2025 Posted December 29, 2025 29 minutes ago, filecore said: Well it seems like I can already update you. Started the fresh server, tried to open a file on Android, nothing. Figured it might be stale data on the client, cleared cache and data from the app, still nothing. Just a spinner and a blank UI. Same thing whether I added my subdomain via the internet, or just via local IP:port. Hi there, please attach the Emby server log from when the problem occurred: How to Report a Problem Thanks!
Luke 42077 Posted December 29, 2025 Posted December 29, 2025 OK can you please provide the log from the Android app: Thanks
Luke 42077 Posted December 29, 2025 Posted December 29, 2025 Is that from when the loading spinner was stuck on the home page?
hawkeye09 0 Posted December 29, 2025 Author Posted December 29, 2025 I found what works was to install emby fresh and not to restore my data. I didnt have the install after then.
filecore 8 Posted December 29, 2025 Posted December 29, 2025 2 minutes ago, Luke said: Is that from when the loading spinner was stuck on the home page? Yes - I enabled logging, force stopped the app, reproduced the behaviour, then uploaded the log.
Luke 42077 Posted December 29, 2025 Posted December 29, 2025 2 minutes ago, filecore said: Yes - I enabled logging, force stopped the app, reproduced the behaviour, then uploaded the log. Can you side load the latest build? https://emby.media/emby-for-android.html does it happen with that?
filecore 8 Posted December 29, 2025 Posted December 29, 2025 2 minutes ago, hawkeye09 said: I found what works was to install emby fresh and not to restore my data. I didnt have the install after then. I don't want to not restore my data! Was this just for testing purposes?
Luke 42077 Posted December 29, 2025 Posted December 29, 2025 3 minutes ago, filecore said: I don't want to not restore my data! Was this just for testing purposes? Your issue is likely distant so I wouldn’t put much stock into that. We should split this thread.
Luke 42077 Posted December 29, 2025 Posted December 29, 2025 18 minutes ago, Luke said: Can you side load the latest build? https://emby.media/emby-for-android.html does it happen with that? Can you try this?
filecore 8 Posted December 30, 2025 Posted December 30, 2025 Hi, sorry for the delay - my last message was at 1am local time and I decided it was time to go to bed! Sideloaded the Android build now, cleared cache and data, enabled logging, and force killed the app then relaunched. First I clicked on an episode of Parks and Rec and it played fine. Then I clicked on The Babadook and got a blank screen for about 20s before it rendered the listing. Clicking play on it gave another spinner. Tried to load a music playlist instead. Another blank screen. Babadook was still stuck as the entry in the notification area widget. Stopped testing at that point, and here are the logs. emby_android_1767086001870.txt emby_android_1767085994927.txt
filecore 8 Posted December 30, 2025 Posted December 30, 2025 As a test I pulled the latest beta server image and ran it, repeating the same sequence of actions as above. This time, Parks and Babadook loaded quickly and started playing just fine, but the playlist would only partially load (see screenshot). Random clicking around also found other shows not loading anything, just a black screen again.
filecore 8 Posted December 30, 2025 Posted December 30, 2025 As an experiment, dropped to emby/embyserver:4.9.2.2 and got the same results again. This makes me wonder if it's something in my setup. The weird thing is that it's been running fine for the entire year until December, in this exact configuration. Infrastructure and network topology: Proxmox on an Elitedesk 800 G2 Mini (i5-6500/32GB DDR4) --> Ubuntu VM (1c4t/24GB) | --> Docker and Compose | --> Emby container | --> Other containers, all of which are operating as expected right now | | [NFS shares mounted via /etc/fstab to the VM and shared as local mounts to containers] [Gigabit LAN, everything wired] | | Synology NAS --> config --> backups --> media subfolders ("entertainment") --> TV --> Movies --> Music Compose file: services: emby: image: emby/embyserver:4.9.2.2 container_name: emby-server environment: - TZ=somewhere - UID=1000 - GID=1000 volumes: - /mnt/emby-configs/emby:/config - /mnt/entertainment/Television:/data/tvshows - /mnt/entertainment/Movies:/data/movies - /mnt/entertainment/Music:/data/music - /mnt/emby-backups:/data/backups ports: - 8096:8096 # http - 8920:8920 # https devices: - /dev/dri:/dev/dri # VAAPI/NV* render nodes restart: always I also asked an LLM and it suggested that I move the config folder back onto the server's local SSD rather than the NAS. This is a possibility I'm sure, although again, it's been running fine for the past however long. But I'll give that a try next.
Neminem 1518 Posted December 30, 2025 Posted December 30, 2025 Hmm config folder should be on fast diskes. Well since your DB are in the config folder, and SQLite does NOT like being on remote storage. Although it might work. SQLite is a file system DB and not a multi user DB. Sqlite over a network share - Stack Overflow
filecore 8 Posted December 30, 2025 Posted December 30, 2025 (edited) Well it has been working, but I considered that it might be a factor. So I stopped the container, brought the configs back over from the NAS to the local server VM: sudo rsync -aAXH --numeric-ids --info=progress2 /mnt/emby-configs/emby/ /home/user/docker/emby/ 21,882,113,816 100% 8.19MB/s 0:42:28 (xfr#232922, to-chk=0/279286) (Would have reported back faster, but that took a looooong time to transfer!) Then restarted the container using the latest image, and the local version of the configs. I also reinstalled the Play Store version of the Emby app, to put as many of the original variables into place as possible. Repeating the steps above, everything seems to work smoothly again. Perhaps NFS for config was the problem after all. I would be interested to know if hawkeye09 had a similar setup. The curious thing is that according to my timestamps, I created (and have been using) this folder since May. Problems only surfaced now. Perhaps the database grew or fragmented over time? Edited December 30, 2025 by filecore
Neminem 1518 Posted December 30, 2025 Posted December 30, 2025 39 minutes ago, filecore said: Perhaps the database grew or fragmented over time? From what I have found about SQLite is that keep it local to app. I have over the years seen SQLite DB go corrupt when used on NAS / remote OS in stead of local file system. So I always keep a SQLite DB local, to not corrupt it, with bad requests, network latency, NAS shutdowns and what ever that can happen.
Luke 42077 Posted January 3 Posted January 3 On 12/30/2025 at 5:38 AM, Neminem said: Well since your DB are in the config folder, and SQLite does NOT like being on remote storage. yes this is true. it is even in their documentation. @filecorehas this helped?
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now