(2024-07-24, 06:33 PM)TheDreadPirate Wrote: What are the names of the host NICs on your system?

(2024-07-24, 07:06 PM)TheDreadPirate Wrote: I was talking about the output of "sudo ifconfig" or "sudo netplan status".  Jellyfin, by default, ignores NICs that start with "veth".  See my example below.  The last two interfaces would be ignored by Jellyfin.  I don't know if you had some unorthodox setup and the "veth" interfaces were the only NICs available.

Code:

chris@rat-trap:~$ sudo netplan status
    Online state: online
    DNS Addresses: 127.0.0.53 (stub)
      DNS Search: <mydomain.tld>

●  1: lo ethernet UNKNOWN/UP (unmanaged)
      MAC Address: 00:00:00:00:00:00
        Addresses: 127.0.0.1/8
                  ::1/128

●  2: eno1 ethernet UP (networkd: eno1)
      MAC Address: a0:36:bc:35:7c:b7 (Intel Corporation)
        Addresses: 192.168.1.3/24 (dhcp)
                  <IPv6 prefix>:<IPv6 address>/128
                  <IPv6 prefix>:<IPv6 address>/64
                  fe80::a236:bcff:fe35:7cb7/64 (link)
    DNS Addresses: 192.168.1.1
                  <IPv6 prefix>::1
      DNS Search: <mydomain.tld>
          Routes: default via 192.168.1.1 from 192.168.1.3 metric 100 (dhcp)
                  192.168.1.0/24 from 192.168.1.3 metric 100 (link)
                  192.168.1.1 from 192.168.1.3 metric 100 (dhcp, link)
                  <IPv6 prefix>::/64 metric 100 (ra)
                  fe80::/64 metric 256
                  default via fe80::e6f4:c6ff:fe05:3b24 metric 100 (ra)

●  3: br-e1bdec8cf397 bridge UP (unmanaged)
      MAC Address: 02:42:c8:ba:10:51
        Addresses: 172.16.100.1/24
                  fe80::42:c8ff:feba:1051/64 (link)
          Routes: 172.16.100.0/24 from 172.16.100.1 (link)
                  fe80::/64 metric 256
      Interfaces: veth1a24fc4
                  vethdb4e1a0

● 52: veth1a24fc4 virtual-ethernet UP (unmanaged)
      MAC Address: e2:46:bf:48:46:67
        Addresses: fe80::e046:bfff:fe48:4667/64 (link)
          Routes: fe80::/64 metric 256
          Bridge: br-e1bdec8cf397

● 54: vethdb4e1a0 virtual-ethernet UP (unmanaged)
      MAC Address: 1e:7f:0c:3f:55:01
        Addresses: fe80::1c7f:cff:fe3f:5501/64 (link)
          Routes: fe80::/64 metric 256
          Bridge: br-e1bdec8cf397

(2024-07-24, 07:40 PM)TheDreadPirate Wrote: Can you share both the jellyfin log and docker daemon log?

For the jellyfin log, go to where you mounted /config and there should be a "log" folder in it.  Share the full log via pastebin.  We are checking to see what interfaces it found and if there were any issues binding to it.

For the docker daemon log, run this command.

Code:

sudo journalctl -u docker.server --no-tail > docker_daemon.txt

Also share that log via pastebin.

(2024-07-24, 07:40 PM)TheDreadPirate Wrote: Can you share both the jellyfin log and docker daemon log?

For the jellyfin log, go to where you mounted /config and there should be a "log" folder in it.  Share the full log via pastebin.  We are checking to see what interfaces it found and if there were any issues binding to it.

For the docker daemon log, run this command.

Code:

sudo journalctl -u docker.server --no-tail > docker_daemon.txt

Also share that log via pastebin.

(2024-07-24, 09:18 PM)TheDreadPirate Wrote: From your log.

Code:

[2024-07-24 07:30:46.839 -04:00] [INF] [1] Jellyfin.Networking.Manager.NetworkManager: Filtered interface addresses: []

I am not familiar with Portainer's quirks.  But I am thinking that Jellyfin can't see, or doesn't have access to, the host NIC.

My test instance of Jellyfin normally uses bridge networking, but when I switch it to host networking this is the output for the same line.

Code:

[21:16:28] [INF] [1] Jellyfin.Networking.Manager.NetworkManager: Filtered interface addresses: ["127.0.0.1", "192.168.1.3", "172.16.100.1", "::1", "<IPv6 Address>", "<IPv6 Address>", "fe80::a236:bcff:fe35:7cb7%2", "fe80::42:c8ff:feba:1051%3"]

(2024-07-24, 09:31 PM)TheDreadPirate Wrote: So you can add specific addresses or subnets so that Jellyfin selects a particular interface, but yours are the defaults (which is fine).

Code:

Jellyfin.Networking.Manager.NetworkManager: Used LAN subnets: ["127.0.0.1/8", "10.0.0.0/8", "172.16.0.0/12", "192.168.0.0/16"]

The log line I mentioned in my last post are the results of the filter.  It didn't find any interfaces that fall within the configured subnets.  And since 192.168.31.* falls within 192.168.0.0/16, if that interface was visible to the container, it would have been listed in the "Filtered addresses" log.  But it wasn't.

So there is some sort of issue with your networking/Portainer setup not making the host NIC available to the container.

I use plain docker on the command line so I can't really say whether Portainer is doing anything weird.  But your docker compose looks fine.