Closed ZigEEEEE closed 3 months ago
Are there two jellyfin
processes listed in the process list (ps
)? One will be the daemon and the other will be the jellyfin process.
Does sockstat
show ports that jellyfin
uses?
Finally: Running a jail that is newer than the host can result in unexpected/unknown behavior. You can look at https://github.com/Thefrank/jellyfin-server-freebsd/issues/75 to get a better idea of the problems that might occur between TrueNAS 13.0 (based on FreeBSD 13.1) and FreeBSD 13.2/13.3
Still, no ports are open
It seems jellyfin is not running after all?
If it is a TrueNAS version issue, how do you think I should proceed? Should I change to TrueNAS 13.3 beta?
oops! ps auxw | grep jellyfin
might be the easiest way to dig it out of a list. If the PID is changing often it means that the service is trying to restart a crashing program
This does seem to be a duplicate of #75. A few people have figured out workarounds, otherwise you can wait for a version of TrueNAS based on FreeBSD 13.3 or higher.
I might switch to the beta which is based on 13.3, thanks!
I have jellyfin 10.9.4 installed on a 13.2 jail in TrueNAS. The service IS running in the jail: However, no web interface is hosted and no ports have been opened: As you can see, no TCP or UDP ports have been opened. I have ensured mlock is enabled, IPv6 is set to inherit and all available versions of jail have been tried (13.2, 13.3, 12.4). My TrueNAS version is 13.0-U6.1 I have changed my pkg version to latest and not quarterly to get jellyfin 10.9.4 to install at all.
I really have no idea why I can't go to port 8096 on my PC (NAT forwarding is turned on for ports 8096, 8920, 1900, 7359). Help would be greatly appreciated.