SOLVED: Accessing the web server

[ArbitraryRenaissance]

Sorry for the sporadic posts. I thought that the undetected interface addresses might have had something to do with me explicitly defining the bind address to 0.0.0.0 in the Jellyfin network settings, which I undid later.

Anyway, no -- I'm not able to access Jellyfin via the LAN IP now. As for port 8096 being open, I thought the Jellyfin service did that automatically. The output of sudo ss -tulpn is

Code:

Netid   State    Recv-Q   Send-Q                           Local Address:Port        Peer Address:Port   Process
udp     UNCONN   0        0                                      0.0.0.0:5353             0.0.0.0:*       users:(("systemd-resolve",pid=496,fd=15))
udp     UNCONN   0        0                                      0.0.0.0:5355             0.0.0.0:*       users:(("systemd-resolve",pid=496,fd=11))
udp     UNCONN   0        0                                      0.0.0.0:7359             0.0.0.0:*       users:(("jellyfin",pid=17862,fd=437))
udp     UNCONN   0        0                                   127.0.0.54:53               0.0.0.0:*       users:(("systemd-resolve",pid=496,fd=22))
udp     UNCONN   0        0                                127.0.0.53%lo:53               0.0.0.0:*       users:(("systemd-resolve",pid=496,fd=20))
udp     UNCONN   0        0                                      0.0.0.0:32920            0.0.0.0:*
udp     UNCONN   0        0                                         [::]:5353                [::]:*       users:(("systemd-resolve",pid=496,fd=16))
udp     UNCONN   0        0                                         [::]:5355                [::]:*       users:(("systemd-resolve",pid=496,fd=13))
udp     UNCONN   0        0                                         [::]:32920               [::]:*
udp     UNCONN   0        0          [fe80::b28b:ef2d:b148:1963]%enp42s0:546                 [::]:*       users:(("NetworkManager",pid=736,fd=28))
tcp     LISTEN   0        4096                                   0.0.0.0:5355             0.0.0.0:*       users:(("systemd-resolve",pid=496,fd=12))
tcp     LISTEN   0        512                                    0.0.0.0:8096             0.0.0.0:*       users:(("jellyfin",pid=17862,fd=466))
tcp     LISTEN   0        128                               192.168.1.23:22               0.0.0.0:*       users:(("sshd",pid=837,fd=8))
tcp     LISTEN   0        128                               10.100.100.3:22               0.0.0.0:*       users:(("sshd",pid=837,fd=7))
tcp     LISTEN   0        4096                                127.0.0.54:53               0.0.0.0:*       users:(("systemd-resolve",pid=496,fd=23))
tcp     LISTEN   0        4096                             127.0.0.53%lo:53               0.0.0.0:*       users:(("systemd-resolve",pid=496,fd=21))
tcp     LISTEN   0        4096                                      [::]:5355                [::]:*       users:(("systemd-resolve",pid=496,fd=14))

I also have a firewall rule in place in ufw that allows 8096 to be open:

Code:

(# ufw status numbered)
     To                         Action      From
     --                         ------      ----
[ 1] 22/tcp                     ALLOW IN    Anywhere
[ 2] 8096                       ALLOW IN    Anywhere
[ 3] 22/tcp (v6)                ALLOW IN    Anywhere (v6)
[ 4] 8096 (v6)                  ALLOW IN    Anywhere (v6)

I may need a similar rule in place on my OPNsense router, but I wouldn't know why, since I don't remember needing one for SSH.