[Support] Linuxserver.io - Emby


Recommended Posts

22 minutes ago, Derek_ said:

How do i know what GPU this docker is using? I have onboard Intel, and an Nvidia GPU.

 

I ask because i basically can't skip/slide a movie. It kind of technically works, but it's unusable - it will take as long for it to skip to the point as it would just watching it. I wouldn't have thought it would do this even using the Intel GPU but thought i'd have a look. Perhaps there's some other setting i've overlooked?

 

Am i reading correctly that in order to use the Nvidia GPU i have to install the unRAID Nvidia Plugin? Will that help without also paying for Emby Premiere?

 

I've never used streaming software before, so i'm a tad confused.

As far as I know, you need emby premier to use hardware transcoding.

You have to install the unraid Nvidia plugin and download the Nvidia build and do the correct settings in docker template and in emby to get the Nvidia GPU to be used.

 

Have you done anything to make by see the Intel GPU? Anyway you need emby premier.

 

Link to comment
1 hour ago, saarg said:

As far as I know, you need emby premier to use hardware transcoding.

You have to install the unraid Nvidia plugin and download the Nvidia build and do the correct settings in docker template and in emby to get the Nvidia GPU to be used.

 

Have you done anything to make by see the Intel GPU? Anyway you need emby premier.

 

That's part of the question i suppose - even if i do all these things if i don't have Premier will it make any difference?

 

Do you know if that kind of performance is what i should expect without Premiere, regardless of the Nvidia plugin? I don't want to pay for Premiere only to find that wasn't the problem.

 

As an aside, what do people do with AMD cards?

Edited by Derek_
Link to comment
7 hours ago, Derek_ said:

That's part of the question i suppose - even if i do all these things if i don't have Premier will it make any difference?

 

Do you know if that kind of performance is what i should expect without Premiere, regardless of the Nvidia plugin? I don't want to pay for Premiere only to find that wasn't the problem.

 

As an aside, what do people do with AMD cards?

As we don't know what your issue is, I can't say if it's ping to help or not. You might have a network issue or your CPU might be too weak.

Is it transcoding or is it direct play? Which client is it?

Link to comment
  • 1 month later...

Could someone tell me if I am doing something wrong trying to update the beta version on this docker?  If I set the repository to: linuxserver/emby:beta it for some reason reverts me back to the 4.4.3.0 version of Emby.  If I use linuxserver/emby:4.5.0.13-ls48 or linuxserver/emby:4.5.0.12-ls46 it will install the correct version.  I'm definitely not a docker expert, but in looking at the "digest" numbers it seems like just the "beta" tag should be working.

Link to comment
6 hours ago, WackyWRZ said:

Could someone tell me if I am doing something wrong trying to update the beta version on this docker?  If I set the repository to: linuxserver/emby:beta it for some reason reverts me back to the 4.4.3.0 version of Emby.  If I use linuxserver/emby:4.5.0.13-ls48 or linuxserver/emby:4.5.0.12-ls46 it will install the correct version.  I'm definitely not a docker expert, but in looking at the "digest" numbers it seems like just the "beta" tag should be working.

From looking at docker hub, the beta tag points to 4.5.0.13-ls48

Screenshot_20200623-111758.png

Edited by saarg
Link to comment

Thanks for looking at it saarg.  I tried linuxserver/emby:amd64-beta and that gave me the correct 4.5.0.13 version.  Tried just "beta" again and it rolled back to 4.4.3.0.  I opened "advanced" in docker and hit "force update" on the beta tag and then it switched back to 4.5.0.13...  Weird, dunno if there was something cached somewhere but that appears to have resolved it.

Link to comment
2 hours ago, WackyWRZ said:

Thanks for looking at it saarg.  I tried linuxserver/emby:amd64-beta and that gave me the correct 4.5.0.13 version.  Tried just "beta" again and it rolled back to 4.4.3.0.  I opened "advanced" in docker and hit "force update" on the beta tag and then it switched back to 4.5.0.13...  Weird, dunno if there was something cached somewhere but that appears to have resolved it.

Most likely something with unraid that was the error then.

Link to comment
  • 1 month later...

Hi, 

 

I've made the move from PLEX to Emby as I was tired of the constant buffering errors (Emby seems a lot better up to now). 

 

Anyways, I've followed the Spaceinvader reverse-proxy youtube video and I'm happy with everything, EXCEPT for one thing, remote access. 

 

I can access Emby via browser; emby.mydomain.com and everything is great, however when I try and use the app, I can only connect via port 80 and even then it will not accept any username/password combination??? 

 

I have gone over all my settings and they are pretty much a mirror image of what I had with PLEX. The Letsencrypt config file has been left as default. 

 

Any advice would be greatly appreciated. 

 

Thanks. 

20200802_182814.jpg

20200802_183129.jpg

Screenshot_20200802-182728_Brave.jpg

20200802_183008.jpg

Link to comment
12 hours ago, LoneTraveler said:

Hi, 

 

I've made the move from PLEX to Emby as I was tired of the constant buffering errors (Emby seems a lot better up to now). 

 

Anyways, I've followed the Spaceinvader reverse-proxy youtube video and I'm happy with everything, EXCEPT for one thing, remote access. 

 

I can access Emby via browser; emby.mydomain.com and everything is great, however when I try and use the app, I can only connect via port 80 and even then it will not accept any username/password combination??? 

 

I have gone over all my settings and they are pretty much a mirror image of what I had with PLEX. The Letsencrypt config file has been left as default. 

 

Any advice would be greatly appreciated. 

 

Thanks. 

20200802_182814.jpg

20200802_183129.jpg

Screenshot_20200802-182728_Brave.jpg

20200802_183008.jpg

What have you entered in the server settings of the app? If you want https you need to use port https in the URL and also might have to set the port to 443.

 

Do you access the url locally or remotely when testing?

Do you use https in the browser?

Edited by saarg
  • Thanks 1
Link to comment
15 minutes ago, saarg said:

What have you entered in the server settings of the app? If you want https you need to use port https in the URL and also might have to set the port to 443.

 

Do you access the url locally or remotely when testing?

Do you use https in the browser?

Hi, 

 

I have tried all kinds of variations in the app, the only one that gets me somewhere is entering; "emby.mydomain.com" along with port "80". However the login page that it takes me too won't accept any username/password combination, I've even removed the passwords from the emby user accounts, but it makes no difference. 

 

As for being able to login via my browser, I test this remotely by ensuring I'm on 4G rather than my local network. Any combination of;

emby.mydomain.com

http://emby.mydomain.com

https://emby.mydomain.com

emby.mydomain.com:80

emby.mydomain.com:443

into the browser, all get me to the emby server by directing me to https://emby.mydomain.com.

 

 

20200803_074005.jpg

Screenshot_20200803-073914_Emby.jpg

Edited by LoneTraveler
Link to comment

I

9 hours ago, LoneTraveler said:

Hi, 

 

I have tried all kinds of variations in the app, the only one that gets me somewhere is entering; "emby.mydomain.com" along with port "80". However the login page that it takes me too won't accept any username/password combination, I've even removed the passwords from the emby user accounts, but it makes no difference. 

 

As for being able to login via my browser, I test this remotely by ensuring I'm on 4G rather than my local network. Any combination of;

emby.mydomain.com

http://emby.mydomain.com

https://emby.mydomain.com

emby.mydomain.com:80

emby.mydomain.com:443

into the browser, all get me to the emby server by directing me to https://emby.mydomain.com.

 

 

20200803_074005.jpg

Screenshot_20200803-073914_Emby.jpg

You can't remove the login on remote access. So you will need to log in.

Use https://emby.domain.com in the server address and 443 in the port field.

Also try to remove the automatic port mapping setting under the secure connection mode.

 

It doesn't really make sense that you can't log in using the client. What does it say when you try to login?

  • Thanks 1
Link to comment
3 hours ago, saarg said:

I

You can't remove the login on remote access. So you will need to log in.

Use https://emby.domain.com in the server address and 443 in the port field.

Also try to remove the automatic port mapping setting under the secure connection mode.

 

It doesn't really make sense that you can't log in using the client. What does it say when you try to login?

Hi, 

 

I've just tried what you suggested and it worked first time, I honestly don't know why it is working now, but I won't dwell on that. 😂

 

Thank you very much for taking the time to help, much appreciated. 

Link to comment

Also just got this error

 

 

Pulling image: linuxserver/emby:latest

IMAGE ID [1072267517]: Pulling from linuxserver/emby.
IMAGE ID [403b1827a301]: Pulling fs layer. Downloading 100% of 25 MB. Verifying Checksum. Download complete. Extracting. Pull complete.
IMAGE ID [3829a800c467]: Pulling fs layer. Downloading 100% of 274 B. Verifying Checksum. Download complete. Extracting. Pull complete.
IMAGE ID [22bfdfc184fa]: Pulling fs layer. Downloading 100% of 13 MB. Verifying Checksum. Download complete. Extracting. Pull complete.
IMAGE ID [fbcd4727925d]: Pulling fs layer. Downloading 100% of 4 KB. Download complete. Extracting. Pull complete.
IMAGE ID [2d2fc0113757]: Pulling fs layer. Downloading 100% of 26 MB. Verifying Checksum. Download complete. Extracting. Pull complete.
IMAGE ID [2e1cb016efc6]: Pulling fs layer. Downloading 100% of 97 MB. Verifying Checksum. Download complete. Extracting. Pull complete.
IMAGE ID [8352618cf93d]: Pulling fs layer. Downloading 100% of 1 KB. Download complete. Extracting. Pull complete.
Status: Downloaded newer image for linuxserver/emby:latest

TOTAL DATA PULLED: 162 MB

 

Command:root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='emby' --net='bridge' --cpuset-cpus='4,5,6,24,25,26' -e TZ="America/New_York" -e HOST_OS="Unraid" -e 'NVIDIA_VISIBLE_DEVICES'='GPU-a33379ca-1c07-52ff-e7b9-547c44c9be22' -e 'PUID'='99' -e 'PGID'='100' -p '8096:8096/tcp' -p '8920:8920/tcp' -p '1900:1900/udp' -p '7359:7359/udp' -v '':'/movies':'rw' -v '':'/tv':'rw' -v '':'/music':'rw' -v '/mnt/user/appdata/emby':'/config':'rw' --runtime=nvidia 'linuxserver/emby'

dde619d5e30a74d6e591d75892a62461a59458033c2db485181a09cedc4133fc
/usr/bin/docker: Error response from daemon: error while creating mount source path '/mnt/user/appdata/emby': mkdir /mnt/user/appdata/emby: no space left on device.

The command failed.

 

 

Help !!

Link to comment

And the latest error

 

 

Pulling image: linuxserver/emby:latest

IMAGE ID [1005344308]: Pulling from linuxserver/emby.
IMAGE ID [403b1827a301]: Pulling fs layer. Downloading 100% of 25 MB. Verifying Checksum. Download complete. Extracting. Pull complete.
IMAGE ID [3829a800c467]: Pulling fs layer. Downloading 100% of 274 B. Verifying Checksum. Download complete. Extracting. Pull complete.
IMAGE ID [22bfdfc184fa]: Pulling fs layer. Downloading 100% of 13 MB. Verifying Checksum. Download complete. Extracting. Pull complete.
IMAGE ID [fbcd4727925d]: Pulling fs layer. Downloading 100% of 4 KB. Verifying Checksum. Download complete. Extracting. Pull complete.
IMAGE ID [2d2fc0113757]: Pulling fs layer. Downloading 100% of 26 MB. Verifying Checksum. Download complete. Extracting. Pull complete.
IMAGE ID [2e1cb016efc6]: Pulling fs layer. Downloading 100% of 97 MB. Verifying Checksum. Download complete. Extracting. Pull complete.
IMAGE ID [8352618cf93d]: Pulling fs layer. Downloading 100% of 1 KB. Verifying Checksum. Download complete. Extracting. Pull complete.
Status: Downloaded newer image for linuxserver/emby:latest

TOTAL DATA PULLED: 162 MB

 

Command:root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='emby' --net='host' --cpuset-cpus='4,5,6,24,25,26' -e TZ="America/New_York" -e HOST_OS="Unraid" -e 'TCP_PORT_8096'='8096' -e 'TCP_PORT_8920'='8920' -e 'UDP_PORT_1900'='1900' -e 'UDP_PORT_7359'='7359' -e 'NVIDIA_VISIBLE_DEVICES'='GPU-a33379ca-1c07-52ff-e7b9-547c44c9be22 ' -e 'PUID'='99' -e 'PGID'='100' -v '':'/movies':'rw' -v '':'/tv':'rw' -v '':'/music':'rw' -v '/mnt/user/appdata/emby':'/config':'rw' --runtime=nvidia 'linuxserver/emby'

05fdfdf9ee6f407fc310c6fa8b99b14047a937f857360389856d055bdcb33799
/usr/bin/docker: Error response from daemon: OCI runtime create failed: container_linux.go:346: starting container process caused "process_linux.go:449: container init caused "process_linux.go:432: running prestart hook 0 caused \"error running hook: exit status 1, stdout: , stderr: nvidia-container-cli: device error: unknown device id: GPU-a33379ca-1c07-52ff-e7b9-547c44c9be22 \\n\""": unknown.

The command failed.

Link to comment
5 hours ago, x88dually said:

Error response from daemon: error while creating mount source path '/mnt/user/appdata/emby': mkdir /mnt/user/appdata/emby: no space left on device.

You should post your diagnostics or verify that the settings for the appdata share allows it to write to a drive that has space on it.

3 hours ago, x88dually said:

device error: unknown device id: GPU-a33379ca-1c07-52ff-e7b9-547c44c9be22 \\n\""": unknown.

You're attempting to passthrough a GPU to the container, and it doesn't appear you did the entry correct

Link to comment

Virgin install, new drives.. 1tb cashe, 7 12tb data drives with 2 16tb parity drives.

Went back and did the whole linuxserver nvidia process again. everything copied exactly.

 

New error

 

 

Removing container: emby

Successfully removed container 'emby'

 

Command:root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='emby' --net='host' --cpuset-cpus='4,5,6,24,25,26' -e TZ="America/New_York" -e HOST_OS="Unraid" -e 'TCP_PORT_8096'='8096' -e 'TCP_PORT_8920'='8920' -e 'UDP_PORT_1900'='1900' -e 'UDP_PORT_7359'='7359' -e 'NVIDIA_VISIBLE_DEVICES'='GPU-a33379ca-1c07-52ff-e7b9-547c44c9be22 ' -e 'PUID'='99' -e 'PGID'='100' -v '':'/movies':'rw' -v '':'/tv':'rw' -v '':'/music':'rw' -v '/mnt/user/appdata/emby':'/config':'rw' --runtime=nvidia 'linuxserver/emby'

c1bfc4f171ac1325ad2a6b8c28312043f3af345cfa8040677c9bffb74a3a76c4
/usr/bin/docker: Error response from daemon: OCI runtime create failed: container_linux.go:346: starting container process caused "process_linux.go:449: container init caused "process_linux.go:432: running prestart hook 0 caused \"error running hook: exit status 1, stdout: , stderr: nvidia-container-cli: device error: unknown device id: GPU-a33379ca-1c07-52ff-e7b9-547c44c9be22 \\n\""": unknown.

The command failed.

karens-diagnostics-20200807-1647.zip

Edited by x88dually
Link to comment
1 hour ago, x88dually said:

Virgin install, new drives.. 1tb cashe, 7 12tb data drives with 2 16tb parity drives.

Went back and did the whole linuxserver nvidia process again. everything copied exactly.

 

New error

 

 

Removing container: emby

Successfully removed container 'emby'

 

Command:root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='emby' --net='host' --cpuset-cpus='4,5,6,24,25,26' -e TZ="America/New_York" -e HOST_OS="Unraid" -e 'TCP_PORT_8096'='8096' -e 'TCP_PORT_8920'='8920' -e 'UDP_PORT_1900'='1900' -e 'UDP_PORT_7359'='7359' -e 'NVIDIA_VISIBLE_DEVICES'='GPU-a33379ca-1c07-52ff-e7b9-547c44c9be22 ' -e 'PUID'='99' -e 'PGID'='100' -v '':'/movies':'rw' -v '':'/tv':'rw' -v '':'/music':'rw' -v '/mnt/user/appdata/emby':'/config':'rw' --runtime=nvidia 'linuxserver/emby'

c1bfc4f171ac1325ad2a6b8c28312043f3af345cfa8040677c9bffb74a3a76c4
/usr/bin/docker: Error response from daemon: OCI runtime create failed: container_linux.go:346: starting container process caused "process_linux.go:449: container init caused "process_linux.go:432: running prestart hook 0 caused \"error running hook: exit status 1, stdout: , stderr: nvidia-container-cli: device error: unknown device id: GPU-a33379ca-1c07-52ff-e7b9-547c44c9be22 \\n\""": unknown.

The command failed.

karens-diagnostics-20200807-1647.zip 128.11 kB · 0 downloads

You have a space at the end of the GPU id

Link to comment
15 minutes ago, x88dually said:

Ty saarg

 

Virgin install of 6.8.3 unraid.

in Emby, trying to add library, i cant find where to add Movies, TV, music.

 

whats the path ?

You can't see your media as you haven't added any host paths to the container paths. It's in the template, so all you have to do is to fill in the path.

Link to comment
9 hours ago, x88dually said:

/mnt/user/share/movies  ??  And  the same mnt/user/share/.... for tv and music also ?

That is specific for how you have set up your shares for media, so not for us to say as we don't know where you have your media stored.

Link to comment

I've moved from RPM install on openSUSE to this container on unRAID, everything works fine from an ShieldTV client once it loads, but initial loading of the server connection is kinda slow (10's of seconds).

 

I don't recall having this initial delay before, does it sound familiar?, is there anything I can tweak to fix that?

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.