Unable to access Jellyfin via Tailscale, but accessing the TrueNas dashboard works

Operating Systems & Open Source Linux
, ,
1

Hi,

I recently build myself a Nas and installed truenas scale and jellyfin via the Lauch Docker Image Interface in the Apps section of the truenas dashboard. Besides setting my own value for the node port (I left the container port as 8096) I didnt touch the other network settings (dns, external interface…). I configured the ip of the my nas as static in my router and all was well and good I could access the jellyfin dashboard within my network under the static ip and the port I set for the node port.
Now I wanted to setup remote access to jellyfin. Using Tailscale for that seemed like a good solution. So I installed Tailscale on the Nas via the truecharts chart app, added the two sysctl values as suggested in the truesharts how-to, enabled remote access and set the ip adress filter to blacklist in the jellyfin dashboard.
But now I can not access the jellyfin dashboard via the tailscale ip and the jellyfin port on any other device within or outside my local network that are on the tailscale network. I get a ERR_CONNECTION_REFUSED.
However via port 80 i can access the truenas dashboard on the other devices on the tailscale network. Pinging the tailscale ip of the nas from the other tailscale devices also works. Using nmap on another device on the tailscale network I get open for the status of the port of jellyfin for the local ip of the nas and closed for the tailscale ip of the nas.

I´m a bit of a noob in regards to containerization and networking and pretty confused about why the connection on the jellyfin port is refused… Any help would be very welcome. :slight_smile:

Cheers,

2

I am not sure if this helps but it might. TrueNAS Scale Virtualization Features and How To Get Started Building VM's - YouTube

3

Did you end up finding a solution? I am having the same issue.

4

I found a solution I think:

  1. Configure your tailscale server on the LAN to advertise the entire LAN subnet to Tailscale, then you can just access whatever app you have on your LAN via the usual IP and port (not 100.xx.xx.xx:yyyy) when the client is connected to Tailscale

For me this involved adding a route for the local IP address as well as the kubernetes cluster subnet under App Configuration > Routes

In Tailscale web interface I needed to Edit route Settings and enable the Subnet routes checkbox as well.

5

I am very new to this, could you please describe in more detail how to do this?