Search the Community

Hello everyone, first of all I am new here and also in Emby, you will see me actively here often asking questions. I have a question, I have a proxmox server and inside 2 LXC one of jellyfin which is the one I currently use and another that I created a while ago to test Emby, I really want to see how it is because I have been told it is more advanced than Jellyfin and has more features and better clients, my doubt to all this is that my server has an intel i5 12500 with an iGPU UHD 770, currently I have by passthrough the 770 in the LXC of jellyfin and transcoding works perfectly and makes use of it if necessary, my question here is: In Emby will it also work the same way? or do I need a premium version? PD: this is how I have it configured in both Jellyfin and Emby, that's why I ask if I need the premium version to transcode or not.

My setup is based on a Debian 12 Bookworm LXC Container running on ProxMox 8.1.3. Spent quite some time on this and maybe this helps someone else to get it working. If not, I'm sorry... As I'm using an NFS mount within the container I'm using a privileged container. Under Options -> Features I've enabled "Nesting" and "NFS". Don't touch the LXC's .conf file just yet! Make sure there's no mount entries in it! On the ProxMox host: Find out the GID of the "render" group: getent group render I'm using 104 in this example. In the LXC container: Find a unused GID: cat /etc/group I'm using 112 in this example. Find the group name for the GID of the host's render group getent group 104 I'm using sgx in this example. Change the GID of the sgx group to the unused GID and update the filesystem: groupmod -g 112 sgx find / -group 104 -exec chgrp -h sgx {} \; 112 = new GID, 104 = old GID, sgx = group name. Find the GID of the container's render group getent group render I'm using 106 in this example. Change the GID of the "render" group to the GID of the host's render group and update the file system: groupmod -g 104 render find / -group 106 -exec chgrp -h render {} \; 104 = new GID, 106 = old GID, render = group name. Update the sources list: nano /etc/apt/sources.list Add the following lines: #non-free firmwares deb http://deb.debian.org/debian bookworm non-free-firmware #non-free drivers and components deb http://deb.debian.org/debian bookworm non-free Install the drivers: apt update && apt install intel-media-va-driver-non-free intel-gpu-tools vainfo Shutdown the container. On the ProxMox host: Update the LXC's .conf file: nano /etc/pve/nodes/<NODE NAME>/lxc/<CT ID>.conf Add the following lines: lxc.cgroup2.devices.allow: c 226:0 rwm lxc.cgroup2.devices.allow: c 226:128 rwm lxc.mount.entry: /dev/dri/card0 dev/dri/card0 none bind,optional,create=file lxc.mount.entry: /dev/dri/renderD128 dev/dri/renderD128 none bind,optional,create=file Start the container. In the LXC container: Check if permissions are correct: ls -Alh /dev/dri Output should be similar to: total 0 crw-rw---- 1 root video 226, 0 Dec 10 21:21 card0 crw-rw---- 1 root render 226, 128 Dec 10 21:21 renderD128 Important is that it shows video and render as the groups! Check if VAAPI is available: vainfo Output should be similar to: Install Emby Server. I used the 4.8 Beta version as it seems to have some fixes for Intel Alder Lake-N CPUs. Add the Emby user to the video and render groups: sudo usermod -aG video emby sudo usermod -aG render emby Reboot your container and (hopefully) enjoy hardware acceleration! Try starting a movie and change the quality to something that would trigger transcoding. Check the CPU usage in the ProxMox Summary screen and watch the GPU in the container usage with: intel_gpu_top

I was messing around trying to get my server accessible from a private domain. I changed the ports on my server to match this post. I'm now unable to access it via the LAN IP or the remote IP. These were working just fine before I touched things. I'm wondering how to manually update this via command line since I can't access the GUI anymore. Previous paths I came across while searching didn't pan out. The only complicating factor is that I have the server installed in an LXC in proxmox. Any help would be appreciated.

I always had my server's services such as Emby running in bare-metal because I did't like the performance loss in VM/Hypervisor, etc (I know it's little, but it's something). But it's true that having all services in the same OS is a pain in the a** because if you need to change or reboot something, everything goes down. In addition I need VAAPI transcoding for my server so I needed direct access to iGPU through /dev/dri/renderD128 device. After reading a lot about LXC containers and the benefits of isolation and bare-metal peformance they have, I decided to change and go containerize everything. So installed Debian Strech in the server with LXC 2.0.8 (only available in testing repositories) and created an Ubuntu 16.04 container just for the Emby server. In order to get VAAPI working inside the Emby container, you need to "pass" the required device (/dev/dri/renderD128) from the host to the container and have all drivers installed in the host system. So let's do it. (I assume you already created a container and Emby and ffmpeg are installed in it) (All commands are ran in the host, not inside the container) Stop your container if it's running: lxc-stop -n containername Get the required drivers in the host (my server is a Skylake i5-6600) by installing vainfo (it will automatically install intel-i915-driver, etc.): apt install vainfo Check that vainfo outputs something like this (run vainfo in the command line): error: can't connect to X server! libva info: VA-API version 0.40.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_0_40 libva info: va_openDriver() returns 0 vainfo: VA-API version: 0.40 (libva ) vainfo: Driver version: Intel i965 driver for Intel(R) Skylake - 1.8.3 vainfo: Supported profile and entrypoints VAProfileMPEG2Simple : VAEntrypointVLD VAProfileMPEG2Simple : VAEntrypointEncSlice VAProfileMPEG2Main : VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointEncSlice VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264Main : VAEntrypointEncSliceLP VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileH264High : VAEntrypointEncSliceLP VAProfileH264MultiviewHigh : VAEntrypointVLD VAProfileH264MultiviewHigh : VAEntrypointEncSlice VAProfileH264StereoHigh : VAEntrypointVLD VAProfileH264StereoHigh : VAEntrypointEncSlice VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main : VAEntrypointVLD VAProfileVC1Advanced : VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc VAProfileJPEGBaseline : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointEncPicture VAProfileVP8Version0_3 : VAEntrypointVLD VAProfileVP8Version0_3 : VAEntrypointEncSlice VAProfileHEVCMain : VAEntrypointVLD VAProfileHEVCMain : VAEntrypointEncSlice Now we have to pass the /dev/dri/renderD128 device (which is in charge of VAAPI transcoding) to the container. To do so, we'll write a little script who creates the renderD128 device inside the container everytime this one is started. For that we need to know what kind of device we have and it's minor/major numers, so we run: ls -l /dev/dri Output: total 0 drwxr-xr-x 2 root root 80 ago 5 17:18 by-path crw-rw---- 1 root video 226, 0 ago 5 17:18 card0 crw-rw---- 1 root video 226, 128 ago 5 17:18 renderD128 The info we need is: the letter "c" (in crw-rw----) meaning it's a character device and "226 128" which are the major/minor numbers of the device. Let's create the script then, it will be inside your container's directory but you can place it anywhere changing the paths obviously. Run: nano /var/lib/lxc/containername/autodev And copy inside: #!/bin/bash cd ${LXC_ROOTFS_MOUNT}/dev mkdir dri mknod -m 0666 dri/renderD128 c 226 128 Save, exit and give it privileges with: chmod +x /var/lib/lxc/containername/autodev Perfect, now we have to grant container's access to the device and tell him to run the script when the container starts. To do so, you have to edit the container's configuration file. Run: nano /var/lib/lxc/containername/config And add these two lines at the en of the file: lxc.cgroup.devices.allow = c 226:128 rwm lxc.hook.autodev = /var/lib/lxc/containername/autodev The first line will grant container's access to the device and the second line will run the script which will create the device inside the container. That's all! Now you you can start your container again, attach to it, check the /dev/dri directory and you'll find the renderD128 device inside of it. You can now tell Emby to use it as if you where in a host machine! Enjoy LXC! Referece: https://blog.cavebeat.org/2016/02/how-to-create-tuntap-devices-for-lxc-in-proxmoxve-4-1/

Hi everyone I'm using emby for 3 years now and i'm getting a most powerful server now. I'm using proxmox and i need to set up my new emby server. LXC support is present on proxmox and i really like to use it, but i'm asking myself if it is a good idea. Have you tried emby in LXC with gpu passtrough ? Let me know

Hi everyone. I have a home server running Proxmox VE 4.5 on ZFS the server has several ZFS pools where I store my data. i.e. custom user pools not connected to Proxmox except that the main machine hosts the disks. I want to create a VM container (LXC) where I will run Emby and other apps. Proxmox have a number of templates from TurnKey that I can use to create my container(s). I have tried the turnkey Mediaserver which is a TurnKey fileserver plus Emby. it works for the most part and works nicely but as I tried to setup additional things on it I broke the config and it has issues now so i want to rebuild it. in order to manage my existing data and media I bind-mount my data pools into container like tank0/share0 ==> mediaserver /mnt/share0 and tank1/share1 ==> mediaserver /mnt/share1 so my questions are : #1. the TKMS has Emby configured that all media folders are in "/srv/storage/ " like so @mfs /srv/storage# ls -l total 7 drwxrwxr-x 2 emby users 2 Jul 18 2017 Movies drwxrwxr-x 2 emby users 2 Jul 18 2017 Music drwxrwxr-x 2 emby users 2 Jul 18 2017 Photos -rw-r--r-- 1 root root 79 Jul 18 2017 README.txt drwxrwxr-x 2 emby users 2 Jul 18 2017 TVShows "/srv/storage/ " is the default location that is also SAMBA share and WebDav share. standard config for TK fileserver the medisserver is based on. now is it possible to move this folders into my storage? that is I have a bind-mount in /mnt/share1 that has folder media. I want to locally(within the VM) bind-mount that into "/srv/storage/media" and move all the folders inside. can I ? and How? #2. if I want to setup an NZBGet in separate VM and bind-mount the same pools there, how can I setup user NZBGet will use to run so when it downloads something it can be moved into appropriate folder and Emby will be able to see the new files and use it? permissions issue was one of the more difficult issues with this setup so far. the current config, which I moved the folders with mv command and reconfigured Emby to use the new locations, sees some movies but not one I downloaded with NZBGet or Transmission. it ignores any of my existing pictures and home videos that I copied with cp or rsynk from my local lib. not user how to set permissions on those properly. please point me to some how-to and help that will work. PS>> I already did the general search on many of the topics here and read the pin on this forum about file/folder permission. I will be setting up new container for test using that info but maybe there is something more I need/want to know. PPS>> maybe some one can chime in on the best setup for my needs as well. I want to have a basic VM server (already setup with Proxmox) that will run some special VMs. but main config is a 1. File Server 2. Emby 3. Transmission for torrents (!! I do not do much torrenting or downloads but good to have when needed ) 4. CoachPotato (again not much downloading but want to use that to automate organization of my existing collection) 5. SickRage 6. Lazy Librarian 7 Calibre Server 8. MythTV or what ever to record LiveTV in the future. I do not have the tuner now and it may never come to live but plans are plans. the question here is how to set all this apps so they will play well together nicely. should I run each in it's own LXC to which I mount-bind my storage? if yes should I / can I create/clone Emby user to all of this containers and use that to run the services? if yes How? what are my options here? thanks Vlad.

Hello guys, After running Plex for a long time, I decided to switch to an opensource alternative, given all the new anti-privacy measures taken by Plex. I'm having a problem however: I did a fresh install of Emby 3.2.34.0 in a LXC container running Ubuntu 16.04, the server is not powerful enough to transcode high quality stuff, but this is not necessary. However, even when I do a DirectPlay, the CPU is utilised at 100% in the FFMPEG process, even though transcoding is disabled for the user requesting the stream, the stream play just fine, but it is strange to see this process running when no transcoding is present. Plex used only a few % of the CPU when Direct Playing or remuxing. Very strange. This problem looks similar to a problem people had a few weeks ago when using Emby with live recordings. Is there someone who can help me? Kind regards, Ronnie FFMPEG LOG.txt

So I have emby running in an LXC container on proxmox. It has access to all 4 cores, which are single threaded (Quad core Intel Core i5-6600K). I'm not overclocked at all. I am begining to get enough simultaneous users that sometimes it has trouble. Rarely, and only w/ 4k content so far. But, I was wondering if it would be worth spinning up another VM for emby and see if that helps? I would think not, as it's the same physical CPU *UNLESS* splitting the cores, 2 per vm, would make it more efficient. But it's always good to ask around to see what people have tried/discovered.

This is my current server setup: _________________ | | | Fedora 24 | ____________________ | Nginx proxy | | | | LXC ------------| Debian Jessie | |________________| | Emby Server | |___________________| The outer nginx procy forwards port 80 (so I can just type in "mediapc/" into firefox for the UI, port 443 and the standard emby port for the Android apps to find the server. But I've noticed that it's not possible to Chromecast anything from this server. I suspect that it's because the port the chromecast protocol is using isn't port forwarded. I tried to Wireshark the connection and couldn't figure out what needed to be open. I hope you guys can help me with this Would be nice to use Chromecast again!

So I've been running Emby in a virtual machine with OpenMediaVault for a while now. Now I'm migrating everything to LXC so I get more space and better performance. I now wanted to install and run Emby within a container (LXC not Docker), with a Ubuntu 14.04 container I've had problems since Emby didn't find ffmpeg. Because of that I installed it to a Ubuntu 15.04 container and I also installed the latest ffmpeg from that repo, even though it could now find ffmpeg and ffprobe, after scanning the library emby would randomly just crash. The last exception it throws was a NullPointerException because something went wrong with ffprobe and Object reference not set to an instance of an object Then I used a container with Arch where it seemed to be running okay but then again after a few minutes Emby just crashed with the same error as above. Sudo was installed, the emby user had all the permissions he and Emby ran fine, there is no indication what causes this, there is no error prior to the exception and the file that gets scanned is always random, so it's not my files that cause this... I also installed mediainfo. I don't have the log at the moment because I killed the container again after deciding I don't want Emby if I can't run it in a container. Now I reconsidered my decision and thought maybe someone here can help me. But as soon as I get home I'm going to install a new container with Emby and attach the logs. As soon as I get home I'll install a new container with Emby and attach the logs.