Can't connect remotely

[alair]

我的情况是这样的：archlinux直接运行jellyfin，非包管理安装；前几天发现远程连不是jellyfin了，但是可以进入到选择服务器的界面，昨天我尝试了用docker的方式新安装了一个jellyfin，我没有限制容器的内存和cpu，宕机了好几次，所以我放弃了docker的方式；回到直接运行的方式，我关闭systemd服务后直接运行jellyfin，观察它输出的日志，在进入的选择服务器界面的时候就报了一个network interface相关的错误，同时我在本地的网络环境下尝试进入jellyfin是可以的，这让我想起来我之前有给服务器加装网卡，而目前外网映射的网卡shi新装的网卡，而且两张网卡是处于同一个网段中的，所以我指定了jellyfin监听的ip，我的本地和远程就都可以访问jellyfin了，在其他应用上没有出现这个问题，可能jellyfin内部没有验证我来的时候请求的ip是哪个吧……

[TheDreadPirate]

Hopefully Google translate did its job right. You installed a new NIC and had issues connecting to Jellyfin afterwards? But only Jellyfin had this issue and none of your other services?

If I got that right, did you configure Jellyfin to bind to a specific address in Dashboard > Networking?

[Duvel]

Hi

Just found this thread while searching for my log messages.

I got this on 10.9 when I try to auth with ldap/Authentik

[12:41:47] [WRN] [27] Jellyfin.Networking.Manager.NetworkManager: 81.x.x.172: External request received, no matching external bind address found, trying internal addresses.
[12:41:47] [WRN] [27] Jellyfin.Networking.Manager.NetworkManager: 81.x.x.172: External request received, but no external interface found. Need to route through internal network.
[12:41:48] [WRN] [33] Jellyfin.Networking.Manager.NetworkManager: 81.x.x.172: External request received, no matching external bind address found, trying internal addresses.
[12:41:48] [WRN] [33] Jellyfin.Networking.Manager.NetworkManager: 81.x.x.172: External request received, but no external interface found. Need to route through internal network.

Is it also an issue linked to 10.9?

Note that all tests in the ldap plugin config are successful.
I tried both from LAN and WAN, same issue.
My network settings/NAT/DNS are most probably NOT the problem as everything else works.

[TheDreadPirate]

Are you configuring Jellyfin to bind to a particular IP?

[Duvel]

Nope.
It just run in docker with no network defined on the container so its the default Bridge mode.

It ran on server 192.168.2.4:8097 (changed the port because the 8096 is running the real LIVE jellyfin 10 8 13 ), and Authentik/Ldap runs on 192.168.2.10 and there's no firewall in between (no ufw or anything).

Code:

version: '3'
services:
  jellyfin:
    image: jellyfin/jellyfin:unstable
    container_name: jellyfin_test
    ports:
      - 8097:8096
    user: 115:121
    restart: 'unless-stopped'
    environment:
      - JELLYFIN_CACHE_DIR=/var/cache/jellyfin
      - JELLYFIN_CONFIG_DIR=/etc/jellyfin
      - JELLYFIN_DATA_DIR=/var/lib/jellyfin
      - JELLYFIN_LOG_DIR=/var/log/jellyfin
      - TZ=Europe/Brussels
    volumes:
      - /opt/jellyfin_test/config:/etc/jellyfin
      - /opt/jellyfin_test/cache:/var/cache/jellyfin
      - /opt/jellyfin_test/lib:/var/lib/jellyfin
      - /var/log/jellyfin_test:/var/log/jellyfin
      - /media/plex/nanards:/media/plex/nanards

[Duvel]

Nevermind I found it out. It was a port issue.
Jellyfin let 8096 by default in networking config (even if I change to 8097:8097 in docker).
I adapted the all the ports to 8097 in the config and now I dont have the errors above but I am falling into :
https://forum.jellyfin.org/t-jellyfin-10...ldap-login
Which looks normal with ldap from stable repo