- Joined
- Jan 20, 2017
- Messages
- 17
After testing Jellyfin, I wanted to look at emby, but somehow I fail to get it running.
I'm on TrueNAS SCALE 22.12.4, and installing "apps" from the official repository (charts).
With Jellyfin, I could disable remote connections without issues, and it was also able to access my media files via host path (while I temporarily disabled the SMB share).
Now, emby...
I log in as admin, from a private IP address, different subnet (my entire LAN is within
This really baffles me, as Jellyfin worked fine, with the same config concept, on the same system, just a few days earlier, with no changes to the system itself (I had seen the same issues already when first trying emby on TrueNAS SCALE 22.12.3.3, I just tried everything again today 22.12.4).
Has anyone recently tried to set up emby and encountered similar issues? Thanks!
Edit: The LAN vs. remote part in the config seems to be meant for bandwidth restrictions rather than access segregation. I therefore removed that part.
I'm on TrueNAS SCALE 22.12.4, and installing "apps" from the official repository (charts).
With Jellyfin, I could disable remote connections without issues, and it was also able to access my media files via host path (while I temporarily disabled the SMB share).
Now, emby...
LAN vs. remote:
10.0.0.0/8
), which is correctly shown in the activity section of emby. If I now disable remote access, I'm locked out after a few seconds, although private IP addresses should be accepted, based on how I read the description in the emby network section. But even when explicitly/redundantly entering 10.0.0.0/8
in the LAN config, I'm locked out as soon as remote connections are disabled.- Inaccessible dataset:
I have a test dataset
emby_test
, with the apps
user in a group with read-only access (the only addition to the standard permissions which are set after creation of the dataset). In the app config, this dataset is added as host path to be mounted as /mnt/emby_test
. I did this with "read-only" checked, and later also unchecked.
Selecting this folder via the add library function results in an empty box for the folder name/path. I can however enter the path
/mnt/emby_test
in that box and it gets accepted. However, scanning the library results in nothing being found.
Then I changed the dataset owner from
root:root
to apps:apps
, just like Jellyfin for some reason wants. But this also has no impact, no files are found, even after re-deploying.This really baffles me, as Jellyfin worked fine, with the same config concept, on the same system, just a few days earlier, with no changes to the system itself (I had seen the same issues already when first trying emby on TrueNAS SCALE 22.12.3.3, I just tried everything again today 22.12.4).
Has anyone recently tried to set up emby and encountered similar issues? Thanks!
Edit: The LAN vs. remote part in the config seems to be meant for bandwidth restrictions rather than access segregation. I therefore removed that part.
Last edited: