Connection issues

[jimevt]

I have the Jellyfin server running on a Windows machine.  However, it is my wife's machine.  This makes it difficult to update, reboot, etc.

  So I'm trying to install Jellyfin on "Ubuntu 22.04.5 LTS".   I installed using the bash script method.  The jellyfin service was listed as "masked" so I unmasked it using instructions from the internet.

  I could now get to the Jellyfin login from the local machine using "localhost:8096" or "192.168.1.254:8096"   What I _couldn't_ do is use "192.168.1.254:8096" from any other machine on my local network.

   I've been trying everything I could find on the internet, but none of it has worked.

   I did set "Allow remote connections to this server", but I did not add any IP filters. 

     I tried it with "ufw" disabled, enabled, enabled with 8096 allowed in many different ways.
  ufw status currently shows:

        sudo ufw status | grep 8096
        8096                      ALLOW      Anywhere
        8096 (v6)                  ALLOW      Anywhere (v6)

  Trying to access it from the brave browser reports "This site can't be reached".   firefox says the connection timed out.
 


   I _don't_ want to access this server from the web, only my local network.   However, I _do_ have nginx running on this machine for a mastodon server.
   All the Jellyfin nginx setups I saw seemed to be for port-forwarding with certificates for access on the web.

 
   How can I figure out what is going wrong?  The Jellyfin logs don't show anything when I try to connect from another host, so I'm not getting in at all.
   The ufw logs are also showing nothing when I attempt to log in.  The nginx logs do not show anything either.

  I can ping 192.168.1.254, but telnet to 192.168.1.254 8096 fails.  I _can_ ssh to this server, so at least some of the ports are accessible.


   I tried uninstalling and re-installing, but was then worried about _why_ the service was listed as masked.  I uninstalled everything and have reinstalled from the "*.deb" files.   The service is no longer listed as masked, but that still doesn't fix the local access problem.

Thanks for your suggestions!


JimE.

[TheDreadPirate]

Run these commands and share the output.

Code:

sudo ss -tulpn | grep 8096
sudo ufw status
apt list --installed | grep jellyfin
systemctl show jellyfin

That last command will be very log. Share the output of THAT command via privatebin.net.

[jimevt]

Output is below.  Thanks again!

-------------------------------------------
: (620)>  sudo ss -tulpn | grep 8096
tcp  LISTEN 0      512                  0.0.0.0:8096      0.0.0.0:*    users:(("jellyfin",pid=1559267,fd=466))                 

-------------------------------------------

: (620)> sudo ufw status
Status: active

To                        Action      From
--                        ------      ----
22/tcp                    ALLOW      Anywhere
80/tcp                    ALLOW      Anywhere
443/tcp                    ALLOW      Anywhere
8096                      ALLOW      Anywhere
22/tcp (v6)                ALLOW      Anywhere (v6)
80/tcp (v6)                ALLOW      Anywhere (v6)
443/tcp (v6)              ALLOW      Anywhere (v6)
8096 (v6)                  ALLOW      Anywhere (v6)

-------------------------------------------
e: (623)> apt list --installed | grep jellyfin

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

jellyfin-ffmpeg7/unknown,now 7.0.2-9-jammy amd64 [installed]
jellyfin-server/now 10.10.5+ubu2004 amd64 [installed,upgradable to: 10.10.5+ubu2204]
jellyfin-web/now 10.10.5+ubu2004 all [installed,upgradable to: 10.10.5+ubu2204]


-----------------------------------------------------------------------------------
https://privatebin.net/?83af63cba0fa6122...uw9R8oqg2N

[TheDreadPirate]

And this is installed directly on your machine, right? This isn't WSL2, a VM, or a LXC?

And you're sure that 192.168.1.254 is the right IP?

Code:

sudo ipconfig -a

Also make sure you put "http://" before the IP. A lot of browsers won't even try http and will always assume https.

[jimevt]

This isn't a VM or anything like that.  It is my old desktop running Ubuntu.

I think you meant "ifconfig" not "ipconfig":


: (636)> sudo ifconfig -a
enp2s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.254  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fe80::ba97:5aff:fe04:cc98  prefixlen 64  scopeid 0x20<link>
        ether b8:97:5a:04:cc:98  txqueuelen 1000  (Ethernet)
        RX packets 67845500  bytes 82132097767 (82.1 GB)
        RX errors 0  dropped 591020  overruns 0  frame 0
        TX packets 67070932  bytes 59481998784 (59.4 GB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 94433730  bytes 70632115598 (70.6 GB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 94433730  bytes 70632115598 (70.6 GB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

[jimevt]

While driving to get groceries, it occurred to me that it probably has to be nginx.  I didn't think I needed a setup as I was not trying to access this server from the web, but... What else could be inhibiting this connection?

  I created an HTTP nginx setup (provided by the jellyfin docs, replacing "jellyfin.example.org" with "192.168.1.254".


  Still no luck.


nginx access log doesn't show anything interesting :-(

JimE.

[jimevt]

Well! I can now get to the jellyfin server, but only if I do _NOT_ include the port in the http line.

"http://192.168.1.254" works, "http://192.168.1.254:8096" does not.

So, I think that my troubles have all been in the nginx setup.

Working on getting the address with the port to work correctly.

JimE.

[TheDreadPirate]

Did you configure Jellyfin to only bind to the local loopback? This would explain why local connections work on 8096, but remote connections need to go through Nginx.

[jimevt]

How do I check that?  The "ss" command showed tcp  LISTEN 0      512                  0.0.0.0:8096      0.0.0.0:*    users:(("jellyfin",pid=1559267,fd=466))   

  Doesn't the "0.0.0.0" imply it is bound to any host?



Darn it all!! After a reboot, it fails connecting again :-(


JimE.

[jimevt]

Well.  Now I can no longer access jellyfin from the same server. 

  After the reboot, nothing was listening on port 8096.  After I restarted the jellyfin service, everything worked again.

  Rebooting shouldn't break jellyfin :-(


Jime.