SOLVED: Local Connection Issue

[sammyg2005]

What are the names of the host NICs on your system?

I am unsure if this is what you were referring to, since I only have one NIC. It is an old EliteDesk. Also, i cannot ping it from my laptop. Is there something in Arch that needs to be configured?  I just started using the Arch distro a month ago and I thought I set up all of the dependancies for Network Manager.

Code:

00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (2) I219-LM (rev 31)
        DeviceName: Onboard Lan
        Subsystem: Hewlett-Packard Company Device 8056
        Flags: bus master, fast devsel, latency 0, IRQ 141
        Memory at e1100000 (32-bit, non-prefetchable) [size=128K]
        Capabilities: [c8] Power Management version 3
        Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
        Capabilities: [e0] PCI Advanced Features
        Kernel driver in use: e1000e
        Kernel modules: e1000e

[TheDreadPirate]

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

[sammyg2005]

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

Ah I understand the assignment now. It seems I am ''Offline'' and having an issue with my loopback.

Code:

    Online state: offline
    DNS Addresses: 8.8.8.8
                  192.168.31.200
                  2001:578:3f::30
                  2001:578:3f:1::30

●  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 (unmanaged)
      MAC Address: c8:d3:ff:a0:61:15 (Intel Corporation)
        Addresses: 192.168.31.212/23
                  <IPv6 prefix>:<IPv6 address>/128
                  <IPv6 prefix>:<IPv6 address>/64
                  <IPv6 prefix>:<IPv6 address>/64 (link)
          Routes: default via 192.168.31.200 metric 100 (static)
                  192.168.30.0/23 via 192.168.31.200 metric 100 (static)
                  192.168.30.0/23 from 192.168.31.212 metric 100 (link)
                  2600:8805:3900:5502::1005 metric 100
                  <IPv6 prefix>:<IPv6 address>/1::/64 via  metric 100 (ra)
                  <IPv6 prefix>:<IPv6 address>/64 via metric 100 (ra)
                 <IPv6 prefix>:<IPv6 address>/64 metric 100 (ra)
                  <IPv6 prefix>:<IPv6 address>/64 metric 1024
                  default via <IPv6 prefix>:<IPv6 address> metric 100 (ra)

●  3: docker0 bridge UP (unmanaged)
      MAC Address: 02:42:69:1d:b5:84
        Addresses: 172.17.0.1/16
                  <IPv6 prefix>:<IPv6 address>/64 (link)
          Routes: 172.17.0.0/16 from 172.17.0.1 (link)
                  fe80::/64 metric 256

●  5: br-174032f1549a bridge UP (unmanaged)
      MAC Address: 02:42:4e:3a:94:45
        Addresses: 172.28.10.1/24
                  <IPv6 prefix>:<IPv6 address>/64 (link)
          Routes: 172.28.10.0/24 from 172.28.10.1 (link)
                  fe80::/64 metric 256

●  9: veth96513b5 ethernet UP (unmanaged)
      MAC Address: c6:11:b6:b2:df:fc
        Addresses: <IPv6 prefix>:<IPv6 address>/64 (link)
          Routes: <IPv6 prefix>:<IPv6 address>/64 metric 256

● 13: vetha61d1e2 ethernet UP (unmanaged)
      MAC Address: e6:76:75:f0:af:c1
        Addresses: <IPv6 prefix>:<IPv6 address>/64 (link)
          Routes: <IPv6 prefix>:<IPv6 address>/64 metric 256

● 15: veth58c9162 ethernet UP (unmanaged)
      MAC Address: 92:62:18:97:f6:66
        Addresses:<IPv6 prefix>:<IPv6 address>/64 (link)
          Routes: <IPv6 prefix>:<IPv6 address>/64 metric 256

● 17: veth89397f9 ethernet UP (unmanaged)
      MAC Address: 8a:f0:6c:86:86:00
        Addresses: <IPv6 prefix>:<IPv6 address>/64 (link)
          Routes: <IPv6 prefix>:<IPv6 address>/64 metric 256

● 19: veth0fc38d0 ethernet UP (unmanaged)
      MAC Address: f2:74:d9:0e:f6:5a
        Addresses: <IPv6 prefix>:<IPv6 address>/64 (link)
          Routes: fe80::/64 metric 256

[TheDreadPirate]

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.

[sammyg2005]

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.

The daemon file is blank. Was there an action you wanted me to trigger the log?  But here is jellyfin:

https://pastebin.com/KQe55w9p

[sammyg2005]

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.

I have a static IP, I may not have my route table setup correctly. I’ll have to check when I get home.

[TheDreadPirate]

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"]

[sammyg2005]

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"]

 Aren’t those the ones added in the Networking section of Jellyfin’s settings? I had some in there before, but it didn’t work. Or maybe I’m wrong. I think netplan saying my online state is offline is the culprit. I think without the tables set correctly my NIC isn’t showing available to clients.

[TheDreadPirate]

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.

[sammyg2005]

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.

Yeah I’m not sure. I run portainer as its own container and then add the stack into it. Not sure if that causes issues