5 hours ago, tjb_altf4 said:

@binhex made a fix in his base image to allow support for Tailscale based on a similar issue for Jellyfin recently, but might need to trigger a manual release to update for the current emby release.

 

 

22 hours ago, eventorism said:

Anyone successful in enabling Tailscale within the Docker for binhex - Emby? It throws this error for me/is unable to install the tailscale package. Just trying to launch it with default settings, besides enabling Tailscale, to see if it works. 

 

Running Unraid 7.0.0-rc.2 and the latest version of binhex-emby. I tried it with binhex-prowlarr first, and it works great there, no issues running tailscale with funnel or serve by enabling it via the docker settings, so it seems to be unique for the Emby build. 

 

 

 

i have triggered a new image build based off the latest base image which includes 'which', please 'check for updates' and apply or 'force update'.

24 minutes ago, binhex said:

 

 

i have triggered a new image build based off the latest base image which includes 'which', please 'check for updates' and apply or 'force update'.

 

That was super fast - thank you! Can confirm it's working great now \o/ 

Hello! Do you know if the image includes xe2 drivers for Intel B580 gpu? I'm trying to get the transcode working with this GPU. I can get it detected in the log but it always returns an error 18 (emby is not able to initiate it).

Hi when i change the open with association - its doesn't save and the dialogue box continues to pop up? any ideas how i fix this?

Hello, i'm trying to download last version i can use for WMC.. version 4.6.7.0-4-02. it pulls the data and starts but fails right away. is this image still useable? thanks in advance!

15 hours ago, da1stprince! said:

Hello, i'm trying to download last version i can use for WMC.. version 4.6.7.0-4-02. it pulls the data and starts but fails right away. is this image still useable? thanks in advance!

It works for me (just tested), ensure you are starting with a clean config path, also whats the error? 'fails right away'.

On 9/15/2025 at 12:08 PM, binhex said:

It works for me (just tested), ensure you are starting with a clean config path, also whats the error? 'fails right away'.

thanks, worked with a clean config path!

Hi. I tried to search and I’m sorry if this have already been asked.

But I have a problem with HW acceleration with an Intel iGPU. It works in the official EmbyDocker, after adding device /dev/dri to the docker. But not here, after adding device /dev/dri.

(Tailscale doesn’t work in the official EmbyDocker. That is why I switched.)

Is it possible for me to make any changes to get HW acceleration to work, or is changes to the container necessary? Any suggestions or help is appreciated. If any logs or other testing is necessary I will help.

Thank you.

56 minutes ago, raptorjr said:

Hi. I tried to search and I’m sorry if this have already been asked.

But I have a problem with HW acceleration with an Intel iGPU. It works in the official EmbyDocker, after adding device /dev/dri to the docker. But not here, after adding device /dev/dri.

(Tailscale doesn’t work in the official EmbyDocker. That is why I switched.)

Is it possible for me to make any changes to get HW acceleration to work, or is changes to the container necessary? Any suggestions or help is appreciated. If any logs or other testing is necessary I will help.

Thank you.

AFAIK, no one has been able to get HW transcoding to work in this container. Use the official one. If you need Tailscale, set up a reverse proxy using swag and install the Tailscale mod there. Works great. Tutorial here: https://www.youtube.com/watch?v=uznDiFPlvvM

7 hours ago, strike said:

AFAIK, no one has been able to get HW transcoding to work in this container. Use the official one. If you need Tailscale, set up a reverse proxy using swag and install the Tailscale mod there. Works great. Tutorial here: https://www.youtube.com/watch?v=uznDiFPlvvM

Thank you for the suggestion. I guess a lot smarter people than me have tried to get it to work =)

It would probably have been better if it didn’t work in any container. But if it works in one it should be possible in this also. I don’t have any knowledge of Docker, but is it because what kind of OS is in the bottom of the container? If that is a thing? Would just be interesting to know where the problem is.

Just looking at Unraid and what it can do, and all the different Dockers that is available, it feels like this should be possible. Although it needs someone smart to need it enough to take the time and look into it.

I noticed about 3 weeks ago an updated version of Emby was released. I was wondering if the docker was going to be updated to 4.9.1.90

21 hours ago, wookie104 said:

I noticed about 3 weeks ago an updated version of Emby was released. I was wondering if the docker was going to be updated to 4.9.1.90

waiting for upstream to update, once done the image will be automatically built.

After the latest update, it seems that I can't access emby through HTTPS/TLS any longer (neither locally nor externally). Anyone else with the same issue? HTTP working fine still/no isuess there.

Getting this in Chrome/Edge (can't seem to find a certificate at all when checking the TLS info box in the browser):

Started checking everything, even generated a new certificate, but all checks out as far as I can tell. Certificate is valid/ handshake works through terminal etc, but refuses to load in browser when connecting to Emby. All I can see that changed is that Emby got updated 2025-12-08. I also can't find anything in the Emby logs, it loads the certificate and is listening on the correct ports and so on. Didn't change my network config or Unraid in any way prior to having this error showing up and watched a movie before bedtime, so the error happened over night. Very curious if it's just me as I'm at a a loss as to what might be causing this 🫠

Emby version reads: 4.9.1.90

Edited December 15, 2025Dec 15 by eventorism

On 12/8/2025 at 2:27 PM, eventorism said:

After the latest update, it seems that I can't access emby through HTTPS/TLS any longer (neither locally nor externally). Anyone else with the same issue? HTTP working fine still/no isuess there.

Getting this in Chrome/Edge (can't seem to find a certificate at all when checking the TLS info box in the browser):

Started checking everything, even generated a new certificate, but all checks out as far as I can tell. Certificate is valid/ handshake works through terminal etc, but refuses to load in browser when connecting to Emby. All I can see that changed is that Emby got updated 2025-12-08. I also can't find anything in the Emby logs, it loads the certificate and is listening on the correct ports and so on. Didn't change my network config or Unraid in any way prior to having this error showing up and watched a movie before bedtime, so the error happened over night. Very curious if it's just me as I'm at a a loss as to what might be causing this 🫠

Emby version reads: 4.9.1.90

Still no idea what caused this, but copying over the appdata and simply switching to linuxserver-emby fixed the error/worked on first boot, so if anyone else runs into this same issue, maybe try that.

Edited December 25, 2025Dec 25 by eventorism