2025-03-18, 09:30 PM
(This post was last modified: 2025-03-19, 03:12 AM by ArbitraryRenaissance. Edited 1 time in total.)
Here's the quick rundown of my current setup:
My goal is to get a Jellyfin server running directly on my NAS, but it's failing on pretty much the first step. I installed jellyfin-server, jellyfin-web, and jellyfin-ffmpeg, and then started the Jellyfin service. When I do this, Jellyfin starts listening on port 8096, but if I try navigating to my NAS's local IP address over this port in my main computer's browser, I get a failed connection. The same thing happens if I try accessing through its local IP associated with my VPN.
When I run "jellyfin status" [edit: I now know that this command will end up running a new instance of jellyfin, which won't work anyway because I have it running as a service], I see an error: The server is expected to host the web client, but the provided content directory is either invalid or empty: /usr/lib/jellyfin/jellyfin-web.
I double checked my firewall settings, but I don't think any of them should be obstructing to Jellyfin.
If there's something obvious I'm failing to do, let me know. Also, if any extra info is needed (like log files, but last I checked, they were empty), I'll be happy to provide them. Any help is appreciated. In the meantime, I'll se if I can get the server running with the WireGuard VPN disabled -- even though it will need to be activated again eventually.
- I have a NAS running Arch Linux, which I am accessing remotely from my main computer via SSH.
- I have an OPNsense router, on which I have a road warrior WireGuard VPN configured. My NAS and main computer are both connected to this VPN.
- I also have a gateway established to connect devices to Mullvad VPN servers through a firewall alias, but I can disable this and still have the problems I'm having.
My goal is to get a Jellyfin server running directly on my NAS, but it's failing on pretty much the first step. I installed jellyfin-server, jellyfin-web, and jellyfin-ffmpeg, and then started the Jellyfin service. When I do this, Jellyfin starts listening on port 8096, but if I try navigating to my NAS's local IP address over this port in my main computer's browser, I get a failed connection. The same thing happens if I try accessing through its local IP associated with my VPN.
When I run "jellyfin status" [edit: I now know that this command will end up running a new instance of jellyfin, which won't work anyway because I have it running as a service], I see an error: The server is expected to host the web client, but the provided content directory is either invalid or empty: /usr/lib/jellyfin/jellyfin-web.
I double checked my firewall settings, but I don't think any of them should be obstructing to Jellyfin.
If there's something obvious I'm failing to do, let me know. Also, if any extra info is needed (like log files, but last I checked, they were empty), I'll be happy to provide them. Any help is appreciated. In the meantime, I'll se if I can get the server running with the WireGuard VPN disabled -- even though it will need to be activated again eventually.
![[Image: GitHub%20Sponsors-grey?logo=github]](https://img.shields.io/badge/GitHub%20Sponsors-grey?logo=github){kind=icon}