Search the Community

Hi, Running Emby 3.2.36.0 on my FreeNAS server, and lately i've seen some problems with Subtitle manager, it won't download the latest subs to latest tv-series/movies for me and im not getting the problem... im an VIP member on OpenSubtitle so it is not an issue with to many downloads, and it has worked perfekt the first half of this year atleast, and as you can see in download.txt logg it downloads subs, for some reason swedish versions of older series works, but getting error on newer subs as you can see in Error.txt looking for som new eyes on this, hopefully its something realy easy that i've missed. thanks in advance! from an swedish noob Error.txt Download.txt

New guy question. Everything seems to be working FreeNAS-11.0-U2 (e417d8aa5) and emby-3.2.26.0-amd64. But I don't understand what the Emby Dashboard info is telling me. When I selected the the folders for Emby I used a media folder I had made and the jail that the Emby plugin made. The storage folders show as /mnt/FNAS/Media/Movies which is a folder I made and /media/Movies which is in the emby_1 jail. However, when I look to see where the metadata is being stored using the Server Dashboard it shows /var/db/emby-server/root/default/Movies Now I cannot find that folder anywhere on the FreeNAS server. Everything is setup to the defaults. So is the server actually able to access the metadata with that designation? Is the data being saved? Or is this just pointing nowhere? Extra Question: I know I should do a different post. If the answer is long I will do so. Just let me know. If I need to reinstall FreeNAS can I get emby to reuse the jail that already exists or must I allow it to use a new jail.

Note that there's a lot of steps to this, but individually none are particularly difficult... I'm not a linux or bsd expert by any means, in fact I'd consider myself a complete amateur. I just pieced this all together from guides I read online, none of this is really my own, I'm just compiling it all in one place. I'm a newb myself so I wrote this as newb-friendly as possible... not to insult anyone's intelligence, just to reach the largest audience possible. That said, docker for freenas has been getting a lot of attention since corral, and while I never migrated to corral, everyone seemed to rave about docker so I really wanted to give it a shot. It's now possible on freenas 11.0, thanks to native VM support. So here i'll explain step-by-step how I got an emby docker container running on ubuntu server VM in freenas. At the end you'll have emby server running in a docker container on a Ubuntu Server VM, with everything set to auto-start on reboot. Set up Docker for Ubuntu Server Note: I installed this on an Ubuntu Server 16.04 VM directly from the Freenas 11 GUI. PreReqs: freenas 11.0-U2 (may work on other 11.0 versions but it's confirmed working on this version for me) Ubuntu Server 16.04 ISO x64 vnc viewer (optional but highly recommended) - dedicated ssh app - i like secureCRT First Step - Create the Ubuntu VM Inside the freenas GUI: Go to VM tab, and create a new VM. Create VM name, and give it a good amount of resources, since this will be your container manager. Based on the specs of my server (xeon 1220v3 w/ 32GB RAM), I gave my VM 4 CPUs and 12GB of RAM. Once VM is created, before you start it, go to devices tab, add CDROM, and point it to Ubuntu Server 16.04 iso image (it's free, just grab it from wherever) Also add a disk, must have zvol to tie to. If no zvol, create a zvol with sufficient size. Mine was 80GB. I won't show how to set up a zvol here, but just search for it, it's a simple process Now you can start the VM and connect initially via vnc viewer to the port specified on the VM details. It should boot to the ubuntu cdrom and start the installation process. Install Ubuntu with basic settings. No GUI, no extra features. Just keep it bare bones to keep it lightweight as possible. It will come up with an option to use UEFI boot. Choose that option as that will allow you to auto-start the VM via the freenas GUI. UEFI Boot Fix One annoying thing is that the freenas VM system will not boot to uefi automatically. There's an extra step you need to follow to fix this. https://forums.freenas.org/index.php?threads/how-to-how-to-boot-linux-vms-using-uefi.54039/ Summarizing steps from that guide, if you have shutdown your VM already and try to reboot it (which was my case), it will not automatically start the VM. Instead it will boot to shell. To eliminate this - Just type exit at the shell prompt, and in the EFI menu system navigate to "Boot Maintenance Manager" and then select "Boot from file" to locate and select your grubx64.efi file. Once the VM is started, log in as root. sudo -i As root, cd to the /boot/efi/EFI directory of your VM in order to create the new BOOT directory and copy the existing grubx64.efi to /EFI/BOOT/bootx64.efi. mkdir /boot/efi/EFI/BOOT cp /boot/efi/EFI/ubuntu/grubx64.efi /boot/efi/EFI/BOOT mv /boot/efi/EFI/BOOT/grubx64.efi /boot/efi/EFI/BOOT/bootx64.efi The end result should look like this, using Ubuntu as an example: root@ubuntu-vm:/boot/efi# tree -L 3 . . └── EFI ├── BOOT │ └── bootx64.efi └── ubuntu ├── fbx64.efi ├── grub.cfg ├── grubx64.efi ├── mmx64.efi └── shimx64.efi 3 directories, 6 files root@ubuntu-vm:/boot/efi# The file bootx64.efi is a copy of the grubx64.efi in your VM. NB: If grubx64.efi gets updated you will need to re-create bootx64.efi Restart the VM from the freenas GUI, and see if it boots directly to VM. Now your ubuntu VM should be up and running, and it will auto-start on reboots. As soon as I got Ubuntu up and running, I made sure to enable ssh access. Set Up SSH Access (Optional but Reccomended) sudo apt-get install openssh-server Now you can access the VM via ssh (I like secureCRT) instead of relying on vnc viewer. Also, make sure to mount NAS folder to give NAS access to your VM - Install cifs-utils apt-get install cifs-utils Create the directory and mount the device using the following commands (I named my mount point "freenas". Name it whatever you want). sudo mkdir /mnt/freenas Now mount the device using cifs mount -t cifs //192.168.0.155/nas -o username=anonymous,password=,rw,nounix,iocharset=utf8,file_mode=0644,dir_mode=0755 /mnt/freenas Change the ip address and folders to match the path to your particular NAS setup. My nas is setup for anonymous access internally. You might want to be more secure if you have multiple users, so change those settings as you see fit. sudo df -Th /mnt/freenas/ Test the directory and make sure your VM now has access to your freenas files. Once tested, you'll wan to make permanent so it persists on reboot. edit /etc/fstab and append - //192.168.0.155/nas /mnt/freenas cifs username=anonymous,password=,rw,nounix,iocharset=utf8,file_mode=0755,dir_mode=0755 Again, change the path and options as it matches your particular setup. Test that all this is working by stopping your VM, restarting it, and making sure that your NAS is still accessible via your mount point. Now you're ready to actually install docker. Installing Dockertaken from here https://www.digitalocean.com/community/tutorials/how-to-install-and-use-docker-on-ubuntu-16-04 The Docker installation package available in the official Ubuntu 16.04 repository may not be the latest version. To get the latest and greatest version, install Docker from the official Docker repository. This section shows you how to do just that. First, add the GPG key for the official Docker repository to the system: curl -fsSLhttps://download.docker.com/linux/ubuntu/gpg | sudo apt-key add - Add the Docker repository to APT sources: sudo add-apt-repository "deb [arch=amd64] https://download.docker.com/linux/ubuntu/ $(lsb_release -cs) stable" Next, update the package database with the Docker packages from the newly added repo: sudo apt-get update Make sure you are about to install from the Docker repo instead of the default Ubuntu 16.04 repo: apt-cache policy docker-ce You should see output similar to the follow: Output of apt-cache policy docker-ce docker-ce: Installed: (none) Candidate: 17.03.1~ce-0~ubuntu-xenial Version table: 17.03.1~ce-0~ubuntu-xenial 500 500 https://download.docker.com/linux/ubuntu xenial/stable amd64 Packages 17.03.0~ce-0~ubuntu-xenial 500 500 https://download.docker.com/linux/ubuntu xenial/stable amd64 Packages Notice that docker-ce is not installed, but the candidate for installation is from the Docker repository for Ubuntu 16.04. The docker-ce version number might be different. Finally, install Docker: sudo apt-get install -y docker-ce Docker should now be installed, the daemon started, and the process enabled to start on boot. Check that it's running: sudo systemctl status docker The output should be similar to the following, showing that the service is active and running: ● docker.service - Docker Application Container Engine Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled) Active: active (running) since Sun 2016-05-01 06:53:52 CDT; 1 weeks 3 days ago Docs: https://docs.docker.com Main PID: 749 (docker) Installing Docker now gives you not just the Docker service (daemon) but also the docker command line utility, or the Docker client. All we need for now. Install and Set Up Portainer (Optional but recommended)taken from here https://www.ostechnix.com/portainer-an-easiest-way-to-manage-docker/ sudo docker pull portainer/portainer Let us check whether the Portainer image has been pulled or not. sudo docker images Sample output: portainer/portainer latest ec91653336d4 7 days ago 9.132 MB As you see in the above output, Portainer image size is less than 10 MB, which is very small so that I won’t consume more RAM and Hdd space. We have now Portainer in our local Ubuntu system. Let us start the container using command (this command allows portainer to be persistent on restart): docker run -d -p 9000:9000 --restart always --name portainer -v /opt/portainer-data:/data -v /var/run/docker.sock:/var/run/docker.sock portainer/portainer Now, Portainer is running! Let us go ahead and access the Portainer UI. To do so, open your wbe browser and point it to – http://localhost:9000/ or http://IP_Address:9000/.You will be presented with a screen like below that asks to setup a password for the admin user. Enter the password twice and hit Validate button to create the admin user password. Finally - Add Emby Docker ImageTaken from here - https://hub.docker.com/r/emby/embyserver/builds/b7pzevchadukrbdutjzkjtz/ We recommend you install directly from the Docker Hub. Before starting the install procedure please verify the following prerequisites are fulfilled: ensure the user running installation command can run dockerStart the installation by issuing the following command from within a terminal (restart always & define port will make persistent on restart): docker run -it --rm -v /usr/local/bin:/target emby/embyserver instl Set Up Embyrun the emby-server command emby-server It will ask you to add volume locations. Use the mounted freenas directory to give access to NAS (or whatever folder you set up to mount with your NAS) /mnt/freenas That's it for the cli portion of emby set-up. Just ctrl+D to exit. Now, go into portainer, check images. You should see emby server. Click the link hyperlink. Look for the expose detail. Use one of the available tcp ports. For me, it was tcp port 8096. Now just enter the url of the docker VM with the correct port number: That should go directly to the emby set up screen. You're done! But one last thing before we finish... Enable Systemd Emby (Optional - allows emby-server to auto-start with docker VM)By deafult, containers don't auto-start on reboot. If you want this to happen, which is extremely convenient, you need to give it an appropriate run command. There's several ways to do this with docker, but in Ubuntu, systemd seems to be the recommended way to go. This is probably the most complex part of this tutorial, since the contents of your custom unit will vary depending on your personal setup. Use mine as a general guide and tweak as needed. On some emby docker tutorials, there are one-line commands that get emby-server to get included in systemd, but I couldn't get any of them to work for me for some reason, so I had to set up my own systemd service to make it work. I installed an app called systemd-docker for docker auto starts. Found it in a suggestion in the emby docker thread and it worked for me. apt-get install systemd-docker Then create the unit emby-docker.service file that goes into /etc/systemd/system/ things to note on the switches used in the "ExecStart" section - -v = volume -e = environment variable A good tip is to go into Portainer, look at the emby-server container you set up earlier, and look at the details of the container to get the settings of your ENV and volume sections. Then use the switches as shown in my example to configure your unit to match your personal setup. Some other tips - For my set-up, my volume referred to my mount point of my NAS. Change that to match what yours is. I run my emby container as root user. I have no problem with this. If you want to run it as some other user, you need to change the user as needed TZ = timezone. It's important to have that match your local timezone. Look up linux timezones and find one that matches yours. The rest I think you can keep the same and it shouldn't cause you many issues, but of course depends on your set-up. This took me a while to figure out and get right, and there may very well be easier ways to do this. Here's my sample emby-docker.service file. Make sure to give the file full rw permissions so it can be executed by systemd. [Unit] Description=Emby-Server Docker After=docker.service Requires=docker.service [Service] ExecStart=/usr/bin/systemd-docker run --rm --name %n --net=host -v /home/root/.emby-server:/config -v /mnt/freenas:/mnt/freenas -e APP_UID=0 -e APP_GID=0 -e APP_USER=root -e EDGE=0 -e UMASK=002 -e TZ='America/New_York' emby/embyserver Restart=always RestartSec=10s Type=notify NotifyAccess=all TimeoutStartSec=120 TimeoutStopSec=15 [Install] WantedBy=multi-user.target Enable it to make it persistent - sudo systemctl enable emby-docker Then start it sudo systemctl start emby-docker You should see the container running in portainer in your containers list, and you should be able to access your emby server on the default 8096 port. This time however, the container will always auto-start with your VM.

Very much a NOOB. I am trying out Emby and Plex on a FreeNAS setup. I used the new Emby plugin (thank you!) Everything runs except: With Emby I can only put SMB shares for Windows into the Library: \\FREENAS\FN-Media\Movies Yet with Plex I can put the jail folders into its libraries: \\FreeNAS\jails\plex\Movies I understand this is not correct and I should be putting the Emby jail folders into its libraries. \\FREENAS\FN-Media\Movies \\192.168.1.219\jails\emby_1\Movies Also tried using // vice \ since I am on windows. When I try this I get: "There was an error adding the media path. Please ensure path is valid and Emby Server Process has access to that location" The jail folders are owned by user root, group wheel. I have made a user emby and assigned it to the group wheel. This user has the same ID as the user emby inside the jail (983). Can't find the solution to this in any post I have seen.

I've using Emby v3.2.20.0 plugin on a FreeNAS server and previously had DLNA running fine, but I was having issues with genres not displaying so I decided to do the I.T. thing of turning it off and on again. So unchecked "Enable Dlna server" click save and re-check "Enable Dlna server" and click saved, but now DLNA doesn't work at all. I've tried rebooting the plugin and rebooting FreeNAS but nothing works. server-63634445057.txt

hi all, hope this is the right place. i am running emby-server-3.2.10.0 (doesnt matter, happened on more than one version) using pkg on a freenas-9.10 server. i noticed that when i set a password for a user using the webinterface i get access to another field for local network login offering easy-pin-access stuff. nice. if i check the box for that it works as intended. if i disable the password for the user again by updating it to an empty one the field for local pin access goes away but is still active. meaning that i still see a little lock symbol next to the user on my fire-tv and need to enter the easy-access-pin to login. since i disabled the password i'd expected that all login restrictions would be gone now. if you feel like this is a valid point please look into that. thanks for making a great tool & product! edit: solved

IP ADDRESS FREENAS: 10.233.22.12 IP ADDRESS EMBY: 10.233.22.5:8096 Someone resolve this problem? i want to access emby like this : 10.233.22.5 (no port)

Hi I have strange remux on my Chrome browser, look at screenshot for better understand what I saying I have FreeNAS-Corral-10.0.3, Chrome 57.0.2987.133 (64-bit) I have the same result on Windows 10 and OSX too server_log.txt remux.txt

Hi my Emby work on FreeNAS on Docker image I have two strange things: I only download stable version, but now I have 3.2.11.0 beta, and I don't know why My setup on Docker config is EDGE = 1 ( automatic updates ON ) and a not able to update to version 3.2.11.1 I try to restart my docker, I try to start update command on Docker console, but nothing happened ... Is somebody ready answer why? Thanks

So I have installed Emby 3.2.8.0 inside docker on FreeNAS 10, everything works fine, but problem start when I try to change the resolution of the video, when I test on a web browser, everything works fine, but on a mobile application ( latest Android app ) or Windows theater (latest version ) app, another resolution just not work ... Emby transcode video correctly but nothing show on theater app or mobile app Logs are in Attached Files emby_serer_log.txt emby_transcode_log.txt

Hi, Just updated the media/emby-server port to 3.1.0, and the server keeps throwing an unhandled exception when starting (find the logs attached). Reverted back to 3.0.8500 in the meantime as that one works fine (server-63617782744 (8500 old success).txt). 2016-12-19 21:51:42.8663 Error App: LoaderException: Could not resolve type with token 0100005f 2016-12-19 21:51:42.8696 Error App: LoaderException: Could not load file or assembly or one of its dependencies. 2016-12-19 21:51:42.8696 Error App: LoaderException: Could not load file or assembly or one of its dependencies. 2016-12-19 21:51:42.8696 Error App: LoaderException: Could not load file or assembly or one of its dependencies. 2016-12-19 21:51:42.8696 Error App: LoaderException: Could not resolve type with token 01000128 2016-12-19 21:51:42.8696 Error App: LoaderException: Could not load file or assembly or one of its dependencies. 2016-12-19 21:51:44.4754 Error ServerManager: Error starting Http Server *** Error Report *** Version: 3.1.0.0 Command line: /usr/local/lib/emby-server/MediaBrowser.Server.Mono.exe -ffmpeg /usr/local/bin/ffmpeg -ffprobe /usr/local/bin/ffprobe -programdata /var/db/emby-server Operating system: Unix 10.3.0.0 64-Bit OS: True 64-Bit Process: True Mono: 4.6.2 (Stable 4.6.2.7/08fd525 Mon Nov 28 22:44:12 UTC 2016) Processor count: 12 Program data path: /var/db/emby-server Application directory: /usr/local/lib/emby-server System.AggregateException: One or more errors occurred. ---> MediaBrowser.Model.Net.SocketCreateException: ProtocolNotSupported ---> System.Net.Sockets.SocketException: Protocol not supported at System.Net.Sockets.Socket..ctor (System.Net.Sockets.AddressFamily addressFamily, System.Net.Sockets.SocketType socketType, System.Net.Sockets.ProtocolType protocolType) [0x0005d] in <bd46d4d4f7964dfa9beea098499ab597>:0 at Emby.Common.Implementations.Net.SocketFactory.CreateSocket (MediaBrowser.Model.Net.IpAddressFamily family, MediaBrowser.Model.Net.SocketType socketType, MediaBrowser.Model.Net.ProtocolType protocolType, System.Boolean dualMode) [0x00000] in <9922445e90a448f2a17d005b1cc33d56>:0 --- End of inner exception stack trace --- at Emby.Common.Implementations.Net.SocketFactory.CreateSocket (MediaBrowser.Model.Net.IpAddressFamily family, MediaBrowser.Model.Net.SocketType socketType, MediaBrowser.Model.Net.ProtocolType protocolType, System.Boolean dualMode) [0x00047] in <9922445e90a448f2a17d005b1cc33d56>:0 at SocketHttpListener.Net.EndPointListener.CreateSocket () [0x00017] in <5e2146744a844faab36e869c2bc89d0d>:0 --- End of inner exception stack trace --- at System.Threading.Tasks.Task.ThrowIfExceptional (System.Boolean includeTaskCanceledExceptions) [0x00014] in <8f2c484307284b51944a1a13a14c0266>:0 at System.Threading.Tasks.Task`1[TResult].GetResultCore (System.Boolean waitCompletionNotification) [0x00034] in <8f2c484307284b51944a1a13a14c0266>:0 at System.Threading.Tasks.Task`1[TResult].get_Result () [0x0000b] in <8f2c484307284b51944a1a13a14c0266>:0 at SocketHttpListener.Net.EndPointManager.AddPrefixInternal (MediaBrowser.Model.Logging.ILogger logger, System.String p, SocketHttpListener.Net.HttpListener listener) [0x0006a] in <5e2146744a844faab36e869c2bc89d0d>:0 at SocketHttpListener.Net.EndPointManager.AddListener (MediaBrowser.Model.Logging.ILogger logger, SocketHttpListener.Net.HttpListener listener) [0x00030] in <5e2146744a844faab36e869c2bc89d0d>:0 ---> (Inner Exception #0) MediaBrowser.Model.Net.SocketCreateException: ProtocolNotSupported ---> System.Net.Sockets.SocketException: Protocol not supported at System.Net.Sockets.Socket..ctor (System.Net.Sockets.AddressFamily addressFamily, System.Net.Sockets.SocketType socketType, System.Net.Sockets.ProtocolType protocolType) [0x0005d] in <bd46d4d4f7964dfa9beea098499ab597>:0 at Emby.Common.Implementations.Net.SocketFactory.CreateSocket (MediaBrowser.Model.Net.IpAddressFamily family, MediaBrowser.Model.Net.SocketType socketType, MediaBrowser.Model.Net.ProtocolType protocolType, System.Boolean dualMode) [0x00000] in <9922445e90a448f2a17d005b1cc33d56>:0 --- End of inner exception stack trace --- at Emby.Common.Implementations.Net.SocketFactory.CreateSocket (MediaBrowser.Model.Net.IpAddressFamily family, MediaBrowser.Model.Net.SocketType socketType, MediaBrowser.Model.Net.ProtocolType protocolType, System.Boolean dualMode) [0x00047] in <9922445e90a448f2a17d005b1cc33d56>:0 at SocketHttpListener.Net.EndPointListener.CreateSocket () [0x00017] in <5e2146744a844faab36e869c2bc89d0d>:0 <--- Anything I can do to fix this? Is everyone else also experiencing this problem? Thank you server-63617781102.txt unhandled_abcf3070-649e-4189-a769-b1c2efb9e65e.txt server-63617782744 (8500 old success).txt

Got a confusing dialog box when I logged into the web client today. It informed and thanked me for running a beta version of Emby. I've never seen this before, nor since. I'm running Version 3.0.5934.0 that I always install from the FreeNAS WebUI / Plugins interface. I last updated a few weeks ago. Just wondering what might be going on. Have others seen this?

scenario: I re-built my jails on freenas 9.10 as the PBI update kept failing via the freenas GUI (still have the old jail which works fine) copied the contents of /var/db/emby-server to the new jail started emby without issue db upgrade and full library scan completed without issue (version update to 5931 from 5786) the issue is now that all video media will not play in any client app (web, chromecast, android) from what i can tell in the logs it appears to be a transcoding issue but that is all that i can understand myself apologies for the size of the server logs..... debug on by the looks remux-f7099ad7-8d41-4e4b-bacd-1ae09bcc45f2.txt transcode-f9a011ef-cdd2-4a46-8b9e-a699330f4448.txt transcode-f051e420-cf72-4a3b-a82e-01d14775176b.txt server-63598495830 part1.txt

Hi, I've noticed in the past couple releases of Emby for FreeNAS that the cinema mode has stopped playing trailers. Currently I'm running version emby-3.0.5931-amd64. When I play a movie it just goes directly into the main feature as if the setting was disabled entirely. The trailers are stored locally with the movie and I am able to play the trailer directly from the web interface so it shouldn't be any kind of format/transcoding problem or anything wrong with the file location. Server>Playback>Cinema Mode settings (which haven't changed) Enable for: Movies Include Trailers from my Library Enable smart Parental control Cinema mode is also enabled under my User>Playback settings I've checked the server logs and didn't find any kinds of errors there. Just a bunch of HTTP 200 messages. Is this a known issue? Is there somewhere I should check next?

Hi, I've put some pictures (JPG) in a directory of a mixed library. Directory listing: The directory can be accessed by Emby, the pictures should also be accessible (other: r). But the content of the Folder "Dies-und-das" is not displayed, the folder in the library is empty: Log: log.txt Emby Version 3.0.5821.0 Thanks, Gebhard

Hey All, I have run a FreeNAS for my home media server for some time (over 6 years)... but my current box was quite outdated (running FN 0.7.2, SAB, SickBeard, Couchpotato) and was due for an upgrade. Long story short, I upgraded my FreeNAS with a whole new hardware build and am now running the latest 9.3.1 with SAB, SR, CP, and Emby! I am thrilled to start using this setup with my Kodi clients to stream my media library. This will be my first time using Emby to keep my media library updated at a central location and synced down to my Kodi clients! As of last night, Emby Server is up and running on my FreeNAS. Admittedly, I have not had much time to test yet so I tested a couple videos via web browser. I am now focusing on installing Emby plugin on my Kodi clients and have some questions. Once the plugin is installed I can test further to ensure things are working nicely together. Path Substitution. I believe I have configured this on the Emby Server so that the Kodi clients play the media from my CIFS/SMB shares. Any other tips/tricks/words of wisdom? Are any settings changes required on the Kodi Emby addon to ensure the media is playing from the CIFS/SMB share instead of transcoding and playing from Emby? CIFS Authentication. Do I need to tweak any settings in Emby Server or the Kodi plugin to store user/pass for CIFS authentication? Media Library ​I assume that Emby is handling all of the media locations so I do not need to add the remote locations (SMB shares) directly to Kodi. Also assuming that it would be smart to remove existing media sources and blow away my existing Kodi library... or will Emby handle the library portion automatically? I would hate to end up with a jumbled mess up duplicated items. Once Emby is up and running can I still access my media from 'Movies'/'TV Shows' on the Kodi boxes or do I need to configure custom playlists and shortcuts to Emby? Hopefully you all can help clear up some of this confusion for me. -bmcclure937

I've been using Emby for a while now and love it, but its been on a windows 7 server. I've been wanting to switch to FreeNAS for some time now and finally did (the windows server is still up and running in parallel). I transferred all 14TB of data/movies to the new server to /mnt/MyPool/MyPool dataset. I added the emby plugin and then it created the jails dataset. (mainshare wasn't there yet) I tried to add the storage for the emby plugin to /MyPool/MyPool but I got an error Error: The path could not be mounted failed (64) -> mount_nullfs: are not distinct paths (Copied and pasted from my google search, excluding the paths) I created the mainshare dataset and was able to add the storage without issues. But when I go into the emby configuration, I am greeted with Nothing. What would I need to do in order to permit access to view the file listing/Pool? I don't have any emby system user. EDIT: I used the /media endpoint which was the Destination in the jail storage for emby and I was able to get the listing but get a EDIT2: Updated to change Source to be new dataset and checked 'Mounted?'. Everything works.

When trying to update PBI I get the following error (see first pic). Web GUI says Version 3.0.5781.4. A way to fix this? Thanks. Web GUI

I have a samsung smart tv and a denon avr-e300 home theater receiver that both are DLNA ready. I have emby server installed on a FREENAS server with a static IP. The Server, TV and receiver are all networked and have Static IPs. Emby works beautifully on all my devices using the webserver IP except on the DLNA devices. It says the video files are music files, then error out when I try to play them. I have tried .mkv and .mp4. What other file type should I use?

Hi all I haven't been on the forums for a very long time and am back for a query. Since Media Browser and the rebranding to Emby I have seen Emby transform into a masterpiece and am very thankful for the teams that have put in the effort and time into this nifty set of software and different packages out there to suit peoples desires in terms of being compatible between Operating Systems and devices. This will most undoubtedly be mentioned throughout the forums but I just somewhat do not know what to search when it comes to this. I have looked among the different options for the NAS Servers but have not come to any conclusion as to what is better or for my needs. I also don't have much of an idea when it comes to hardware or OS and what's available. If any users that have experimented with more than one device or OS that can actually comment on what they found better in comparison would be much appreciated. I am still interested in what users have to say about one still if that is all they managed to use. 1 - People who have experience in the different NAS devices? (QNAP, Synology, WD, Seagates, etc.) What components benefit what and why? Possibly specs or a basic rule of thumb for when it comes to picking hardware The gist from what I've seen really is, if I am wanting the server to transcode, I will need a decent CPU to follow suite, but if I am direct streaming or direct playing, the hard work has been taken out of it and can go for something on the lighter end? 2 - The different OS and what each ones pro's and con's are? (ASUSTOR, FreeNAS, Open Media Vault, QNAP, Synology, etc.) Just an OS on the whole. Features and ease of use. Can I change OS regardless of the device I end up with and could I run into problems doing this? Mainly where Emby shines the most in terms of being easy to set up and close to error free as a package as this is my main purpose of wanting a NAS Server. (I am aware that none of them have been under development for long so expect bugs and fixes needed) 3 - Anyone who has built a NAS Device and/or decided against a NAS and decided to build another PC for a server? Would it be advisable to build my own NAS or PC in terms of getting more what I want for a better price?I currently use my PC as the server streaming to a Samsung TV with the App, from what I believe, I don't think in my scenario transcoding it taking place at all as the media plays almost instantly and my CPU/ram usage on my PC doesn't seem to increase while running the server. The TV naturally plays MP4's and the bitrate I imagine is within what the TV handles as the MP4's are around 2gig each with 1080p video and stereo output. I would potentially would want the server to do a few other things such as a monthly backup of mine and my GF's PC's and possibly have remote access. Sorry for the long post. Thanks in advance for anyone that can be of assistance and has some input on the subject. Cheers Strugglez/ Mike.

I am not sure why, but every now and then when I try to load Emby Server, I notice that the plugin in FreeNAS is turned off. I mean I can turn it back on by going into the FreeNAS interface, but does anyone know why it just turns itself off sometimes?

I have installed ServerWMC version 1.0.0.58 build 1199 on my HTPC and I have Emby version 3.0.5724.3 installed on my FreeNAS server. When I click on the Live TV tab on the left side of the dashboard, it seems to recognize everything properly like below: Also when I go to try and watch a live tv feed, it shows all of the channels and guide information on the interface like below: However, when I click on "play" after selecting a channel, the only thing I get is a spinning (loading icon) and I am unable to watch anything. I am including my log file if this helps. server-63577062861.txt

I have installed Emby Theater for Windows on aa fresh W10 installation. I have set up external player, left all path settings as default, and set up[ path substitution on Emby in Freenas such that. External player is VLC at the default path of C:\Program Files (x86)\VideoLAN\VLC\vlc.exe The CIFS share is at /mnt/LDATA/movies gets a path substitution to \\MYSERVER\movies oln my FreeNAS Emby server Now when I play a movie I get "Error request could not be processed" which is meaningless. Where can I see what the problem is please?

I have emby up and running on my home server running FreeNAS. Over the last few weeks emby is crashing at least once daily. Once it crashes, I cannot restart it through the webGUI, I have to go into the jail and manually start it using the command 'service emby-server onestart.' I cleared my logs yesterday and this morning I woke up, the plugin crashed again. My logs are posted below. In case it helps, here are specs on my machine: [a href=http://www.ebay.com/itm/231360168024?_trksid=p2057872.m2749.l2649&ssPageName=STRK%3AMEBIDX%3AIT]Supermicro 836TQ 16 bay chassis[/a] [a href=http://www.amazon.com/gp/product/B005FYNSZA/ref=oh_aui_detailpage_o02_s00?ie=UTF8&psc=1]SanDisk Cruzer 16GB thumb drive[/a] (for FreeNAS OS) [a href=http://www.amazon.com/gp/product/B006GD30UC/ref=oh_aui_detailpage_o02_s01?ie=UTF8&psc=1]5 x Noctua 80mm fans [/a] [a href=http://www.amazon.com/gp/product/B00DWFQ42I/ref=oh_aui_detailpage_o02_s04?ie=UTF8&psc=1]Noctua heatsink[/a] [a href=http://www.amazon.com/gp/product/B00JDBYE1I/ref=oh_aui_detailpage_o01_s01?ie=UTF8&psc=1]Cheap samsung console monitor[/a] [a href=http://www.amazon.com/gp/product/B003NREDC8/ref=oh_aui_detailpage_o01_s00?ie=UTF8&psc=1]Cheap console mouse and keyboard[/a] [a href=http://www.newegg.com/Product/Product.aspx?Item=N82E16813182927]Supermicro X10SRL motherboard[/a] [a href=http://www.newegg.com/Product/Product.aspx?Item=N82E16819117512]Intel Xeon E5 processor E5-1620[/a] [a href=http://www.newegg.com/Product/Product.aspx?Item=N82E16822145973]8 x HGST Deskstar NAS 6TB hard drives[/a] [a href=http://www.newegg.com/Product/Product.aspx?Item=N82E16820147382]4 x Samsung 16GB 288-pin DDR4 ECC RAM[/a] [a href=http://www.monoprice.com/Product?c_id=102&cp_id=10226&cs_id=1022602&p_id=5123&seq=1&format=2]A bunch of monoprice SATA cables[/a] A list of the logs: Here are the two logs labeled "unhandled" Any thoughts/ideas on how to fix this is much appreciated!

The FreeNas plugin has been updated to 3.0.5675.1. I assume the FreeBSD pbi as well, though I haven't looked. I've been running it overnight and so far it has fixed several problems on my FreeNAS 9.3 server (Xeon 1230v3): Restarts work now - maybe I was alone in this problem, but previous versions wouldn't restart, they would always hang and I'd have to go reboot the actual Jail. Now restarts work and are nice and quick too. The problem with Dynamic images, so far, appears to have been fixed - I get them for movies, tv, collections folders, and they appear to get updated when media is added. I'll keep an eye on them since they were a little squirrely last time. Also so far, the problem with Mono running out of control CPU during library scans, etc. appears to have been tamped down. This is another one that I'll need to keep an eye on; I've had it run to the point where it brings down the entire jail before. Looks like Mono was updated to the newer 4.x branch too. Syncing is improved, CPU throttling appears to be working, somewhat. It's not quite as fast as Plex (yet) and the client updates as far as progress, etc. are still lagging - it'll show a certain % (20, 30, 50) for a long time even after the sync is done - but it's definitely improved. I synced several movies to my Surface 3 for offline viewing and it's approaching the speed of Plex (and I prefer Emby overall). I don't know how well sync works on other platforms but it wasn't that great until recently on FreeNAS. Lots of other fixes not specific to the *BSD version, read the patch notes. If you are running this on FreeNAS you should definitely upgrade. Note that if you update from the plugin system itself it will take a while and seem to sit on 50% forever, however after about 20 minutes or so (in my case) it will complete.