mx5gr 1 Posted February 29 Share Posted February 29 Hello, I am running Emby 4.8.1.0 on a Raspi4, using the official Docker image and Ubuntu 24 as a host OS. As about 3-4 days ago, emby became completely unresponsive. In fact, it does not take much time to load the container (with no errors reported within the associated log) but it times out to almost (9/10) calls to the server, either from the desktop (browser) or through various apps, on different devices. Other containers on the same server, work fine. At first, I tried to stop all other containers and leave Emby the only one running... to no effect. I then moved the config mounted directory to a clean directory, so that the container starts completely "clean"... to no effect. I completely removed the Emby docker setup from the server and re-created it from scratch... to no effect. The resources on the server are less than 5% CPU and the network is anything but clogged!! Looking at embyserver.txt in debug mode, the only thing I can see is that there is a timeout in fetching https://www.mb3admin.com/admin/service/EmbyPackages.json, although the URL is reachable by other containers on the device and the device itself. There are no firewall rules restricting outbound access and I am not behind a VPN. Any ideas why Emby suddenly stopped responding to any network requests? embyserver.txt Link to comment Share on other sites More sharing options...
Luke 37112 Posted March 1 Share Posted March 1 Hi, are you sure this is the log from when the problem was experienced? I'm guessing you must have restarted the server and this log is from that server restart. That's why it's so small and only covering one minute of time. Link to comment Share on other sites More sharing options...
mx5gr 1 Posted March 1 Author Share Posted March 1 Hi Luke, The log is from the restart, as you mention. However, it spans at least 10 minutes after.. That is, no request reaches the container for some reason. In other cases, the requests arrive (e.g. authentication), however they take ages to execute... Something crazy that seems to have solved the issue -> I removed and recreated the container from scratch for more than 5 times... at the 6th (!) attempt, despite no errors recorded in any logs, the emby server became responsive again! .... completely baffled... 1 Link to comment Share on other sites More sharing options...
Luke 37112 Posted March 1 Share Posted March 1 Thanks for following up. Link to comment Share on other sites More sharing options...
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