All Activity

TBH, I don't think there's much reason to hold off on the update at this point. It's been about a week, and there haven't been widespread reports of this issue. Did something change between 4.9 and 4.10? Yes. Luke's acknowledged that 4.10 is using an updated .NET 8 maintenance version and that it's possible a security-related change is now preventing something that previously worked. My setup and situation could just be unique enough that it happened to catch a change from behavior that was previously more lax to something that's now being enforced more implicitly. Another person running into the same thing and providing logs would definitely be beneficial in narrowing that down. That said, if you do update and run into the issue, downgrading is pretty easy and gets things working again. Good luck.

Here is the log appreciate any help! services: emby: image: emby/embyserver:beta container_name: embyserver network_mode: host runtime: nvidia environment: - UID=1026 - GID=100 - GIDLIST=937 - TZ=Europe/Amsterdam - NVIDIA_VISIBLE_DEVICES=all - NVIDIA_DRIVER_CAPABILITIES=compute,utility,video volumes: - /volume1/docker/emby/config:/config - /volume2/data:/volume2/data restart: unless-stopped this now works without crashing. hardware_detection-63925351890.txt

Hmmm What's not to understand with this text?

Starting a few days ago I started seeing dns failures while retrieving some images. It looks like emby is trying to resolve emby.tmsimg.com which does not appear to resolve. I checked a public dns resolver and it too is not able to resolve it leading me to wonder if the dns entry is bad. Either way I get tons of messages like this message below. If I drop the emby and go to www.tmsimg.com the image loads fine in my browser fwiw. I am running the latest 4.11.0.1 on Ubuntu but this was happening with an earlier beta version as well. Happy to provide the entire log if it is helpful. 2026-09-18 10:57:41.548 Error ImageService-0HNOL4VB6RHOU:00000033: Error processing request *** Error Report *** Version: 4.11.0.1 Command line: /opt/emby-server/system/EmbyServer.dll -programdata /var/lib/emby -ffdetect /opt/emby-server/bin/ffdetect -ffmpeg /opt/emby-server/bin/ffmpeg -ffprobe /opt/emby-server/bin/ffprobe -restartexitcode 3 -updatepackage emby-server-deb_{version}_amd64.deb Operating system: Linux version 7.0.0-31-generic (buildd@lcy02-amd64-060) (x86_64-linux-gnu-gcc-13 (Ubuntu 13.3.0-6ubuntu2~24.04.1) 13.3.0, GNU ld (GNU Binutils for Ubu OS/Process: x64/x64 Framework: .NET 8.0.28 Runtime: opt/emby-server/system/System.Private.CoreLib.dll Processor count: 6 Data path: /var/lib/emby Application path: /opt/emby-server/system MediaBrowser.Model.Net.HttpException: MediaBrowser.Model.Net.HttpException: Name or service not known (emby.tmsimg.com:443) ---> System.Net.Http.HttpRequestException: Name or service not known (emby.tmsimg.com:443) ---> System.Net.Sockets.SocketException (0xFFFDFFFF): Name or service not known at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource.GetResult(Int16 token) at System.Net.Sockets.Socket.<ConnectAsync>g__WaitForConnectWithCancellation|285_0(AwaitableSocketAsyncEventArgs saea, ValueTask connectTask, CancellationToken cancellationToken) at System.Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(String host, Int32 port, HttpRequestMessage initialRequest, Boolean async, CancellationToken cancellationToken) --- End of inner exception stack trace --- at System.Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(String host, Int32 port, HttpRequestMessage initialRequest, Boolean async, CancellationToken cancellationToken) at System.Net.Http.HttpConnectionPool.ConnectAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken) at System.Net.Http.HttpConnectionPool.CreateHttp11ConnectionAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken) at System.Net.Http.HttpConnectionPool.AddHttp11ConnectionAsync(QueueItem queueItem) at System.Threading.Tasks.TaskCompletionSourceWithCancellation`1.WaitWithCancellationAsync(CancellationToken cancellationToken) at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken) at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken) at System.Net.Http.DecompressionHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken) at System.Net.Http.HttpClient.<SendAsync>g__Core|83_0(HttpRequestMessage request, HttpCompletionOption completionOption, CancellationTokenSource cts, Boolean disposeCts, CancellationTokenSource pendingRequestsCts, CancellationToken originalCancellationToken) at Emby.Server.Implementations.HttpClientManager.CoreHttpClientManager.SendAsyncInternal(HttpRequestOptions options, String httpMethod) --- End of inner exception stack trace --- at Emby.Server.Implementations.HttpClientManager.CoreHttpClientManager.SendAsyncInternal(HttpRequestOptions options, String httpMethod) at Emby.Server.Implementations.HttpClientManager.BaseHttpClientManager.SendAsync(HttpRequestOptions options, String httpMethod) at Emby.Providers.Manager.ProviderManager.SaveImageFromRemoteUrl(BaseItem item, LibraryOptions libraryOptions, String url, ImageType type, Nullable`1 imageIndex, Int64[] generatedFromItemIds, IDirectoryService directoryService, Boolean updateImageCache, CancellationToken cancellationToken) at Emby.Server.Implementations.Library.LibraryManager.ConvertImageToLocal(BaseItem item, ItemImageInfo image, Int32 imageIndex, CancellationToken cancellationToken) at Emby.Drawing.ImageProcessor.ProcessImage(ImageProcessingOptions options, CancellationToken cancellationToken) at Emby.Api.Images.ImageService.GetImage(ImageRequest request, Int64 itemId, BaseItem item, Boolean isHeadRequest) at Emby.Server.Implementations.Services.ServiceController.GetTaskResult(Task task) at Emby.Server.Implementations.Services.ServiceHandler.ProcessRequestAsync(HttpListenerHost httpHost, IServerApplicationHost appHost, IRequest httpReq, IResponse httpRes, IStreamHelper streamHelper, RestPath restPath, String responseContentType, CancellationToken cancellationToken) at Emby.Server.Implementations.HttpServer.HttpListenerHost.RequestHandler(IRequest httpReq, RestPath restPath, String urlString, String localPath, String contentTypeInPath, CancellationToken cancellationToken) Source: Emby.Server.Implementations TargetSite: Void MoveNext() InnerException: System.Net.Http.HttpRequestException: Name or service not known (emby.tmsimg.com:443) Source: System.Net.Http TargetSite: Void MoveNext() at System.Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(String host, Int32 port, HttpRequestMessage initialRequest, Boolean async, CancellationToken cancellationToken) at System.Net.Http.HttpConnectionPool.ConnectAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken) at System.Net.Http.HttpConnectionPool.CreateHttp11ConnectionAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken) at System.Net.Http.HttpConnectionPool.AddHttp11ConnectionAsync(QueueItem queueItem) at System.Threading.Tasks.TaskCompletionSourceWithCancellation`1.WaitWithCancellationAsync(CancellationToken cancellationToken) at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken) at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken) at System.Net.Http.DecompressionHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken) at System.Net.Http.HttpClient.<SendAsync>g__Core|83_0(HttpRequestMessage request, HttpCompletionOption completionOption, CancellationTokenSource cts, Boolean disposeCts, CancellationTokenSource pendingRequestsCts, CancellationToken originalCancellationToken) at Emby.Server.Implementations.HttpClientManager.CoreHttpClientManager.SendAsyncInternal(HttpRequestOptions options, String httpMethod) InnerException: System.Net.Sockets.SocketException: Name or service not known Source: System.Net.Sockets TargetSite: Void System.Threading.Tasks.Sources.IValueTaskSource.GetResult(Int16) at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource.GetResult(Int16 token) at System.Net.Sockets.Socket.<ConnectAsync>g__WaitForConnectWithCancellation|285_0(AwaitableSocketAsyncEventArgs saea, ValueTask connectTask, CancellationToken cancellationToken) at System.Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(String host, Int32 port, HttpRequestMessage initialRequest, Boolean async, CancellationToken cancellationToken)

It's released.

thanks plz have a look, please note that i don't have this issue before

How did you setup the m3u?

Hi, we’ll take a look at it. Thanks.

The video was finished approx 8 hours prior but still shows a active. Here is the status of the GPU from the OS: root@Emby:~# nvidia-smi Fri Sep 18 07:44:22 2026 +-----------------------------------------------------------------------------------------+ | NVIDIA-SMI 550.163.01 Driver Version: 550.163.01 CUDA Version: 12.4 | |-----------------------------------------+------------------------+----------------------+ | GPU Name Persistence-M | Bus-Id Disp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap | Memory-Usage | GPU-Util Compute M. | | | | MIG M. | |=========================================+========================+======================| | 0 NVIDIA GeForce GTX 1060 3GB Off | 00000000:01:00.0 Off | N/A | | 47% 34C P0 29W / 120W | 0MiB / 3072MiB | 0% Default | | | | N/A | +-----------------------------------------+------------------------+----------------------+ +-----------------------------------------------------------------------------------------+ | Processes: | | GPU GI CI PID Type Process name GPU Memory | | ID ID Usage | |=========================================================================================| | No running processes found | +-----------------------------------------------------------------------------------------+ Showing the transcode isn't running. embyserver log for that period is attached (the video is the last video in that log). Also attached is the transcode (ffmpeg) log as well as the mediainfo for the video file. From all that it appears Emby restarted ffmpeg at 13:48, after the forced track’s last event at 13:25, while still asking ffmpeg to include that subtitle stream in HLS segmentation which caused a buffering failure and that is why it is still showing in Now Playing. Linux Emby 6.12.94+deb13-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.12.94-1 (2026-06-20) x86_64 (this is a proxmox VM w/the GPU in passthrough) Emby 4.9.30 embyserver-63925286400.txt ffmpeg-transcode-71fe674a-d9a3-456e-815e-08f7de18d40a_1.txt mediainfo.txt

Hi, yes we’ll take a look at this. Thanks.

I think this is a big factor. /N

Sorry, I didn't understand. I will send you in private

You might find a browser flag to disable it but to be specific, we’re using a css media query looking for pointer: coarse, which tells us that your primary input method is touch.

Do you have different subnets? Is the server on the same one? It may be that your device looks remote to the server. If it sees it as local, it will set the bitrate to 110Mbs

@Cr8iveLosr?

That video doesn't contain anything but short playback. I need to see you selecting the option to change speed and then see what happens. Thanks.

Hi, what metadata fetchers are enabled on the library?

That's not uncommon - even though they actually enabled it. You just forget or you don't mentally connect "spoiler information" with the episode image so don't think it has any bearing on the issue.

Yes, I'm still having the issue. I ran some more specific tests and here's what I found: - Casting DOES work perfectly from this same Emby server on AWS to a Google TV 4K (Direct Play, FLAC 994kbps, no errors). - Casting does NOT work to my JBL Authentics 500 (a speaker with Chromecast built-in) — it just sits on "Connecting..." and never actually connects. In the Emby logs (with debug logging enabled), there's no sign of any connection attempt from the JBL at all, as if it never even reaches out to the server. - I confirmed the JBL can receive casts from custom apps just fine: using Jellyfin, on the same AWS server, same domain, same network, casting to the JBL works without any issue. This makes me think it's not a problem with my network, my SSL certificate, or the JBL device itself (which we now know can receive casts from third-party apps), but something specific to how the "Emby for Chromecast" receiver app communicates with audio-only Cast devices (no screen), like the JBL, even though it works perfectly with Chromecasts that do have a screen. Is it possible the Emby receiver app has a known issue with audio-only Cast devices? Thanks again for the help.

Hello, Recently, I’ve been unable to use "Identify". I tried searching by the movie or TV series name and year, but I couldn’t find anything. I also tried entering the IMDb ID, but that didn’t help either. I’m not sure what the problem is, especially since the search was working fine before. Could you please check this and let me know what might be causing it? Thank you. embyserver.txt

What do you mean by that?

We're coming up to one year now since I requested this "logical" minor change in how notifications for photos/videos are processed from mixed media libraries (i.e. home libraries). That is to bundle notifications for photos/videos added, and send all of them in one email for all the media added for that day, rather than for every video or every photo which basically created spam emails. Can we please have this change made? TY

Did you do the repair sink and artwork cache reset?

Thanks for the update. I noticed that my backgrounds while browsing are black instead of fanart. I checked the settings for my skin (Aeon NOX Silvo) and they are correct. It happens in all views. It was fine before. Any ideas? Thanks

Sorry, should've been clearer. I'm not hitting this myself; I've stayed on 4.9.5.0 specifically because of this thread. Just trying to work out from others' experience whether it's worth updating and living with the regression short-term, or holding off until there's a fix. Nothing to try on my end yet since I haven't upgraded.