Jellyfin Forum
Can't access server after upgrade. - Printable Version

+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+---- Forum: Networking & Access (https://forum.jellyfin.org/f-networking-access)
+---- Thread: Can't access server after upgrade. (/t-can-t-access-server-after-upgrade)



Can't access server after upgrade. - faber3492 - 2024-10-17

I'm using docker version of jellyfin from long time.
I always used the same docker compose custom configuration tuned to access jellyfin on my LAN with no issues. Here it is the docker-compose.yml:

Code:
version: "3.7"

services:
  app_proxy:
    environment:
      APP_HOST: jellyfin_server_1
      APP_PORT: 8096
      PROXY_AUTH_ADD: "false"

  server:
    image: linuxserver/jellyfin:10.9.11@sha256:01cd85925160e4ed20d74cc7c59fd4b166d7ff6349788f6ce390f5672b6c019b
    restart: on-failure
    hostname: "${DEVICE_HOSTNAME}"
    environment:
      - PUID=1000
      - PGID=1000
    group_add:
      - "109"
    volumes:
      - ${APP_DATA_DIR}/data/config:/config
      - ${UMBREL_ROOT}/data/storage/downloads:/downloads
    devices:
      - /dev/dri/renderD128:/dev/dri/renderD128
    ports:
      # Service auto-discovery
      - 7359:7359/udp
    networks:
      - macvlan
      - default

networks:
    macvlan:
        driver: macvlan
        driver_opts:
            parent: enp0s1f2
        ipam:
            config:
                - subnet: 192.168.1.0/24


But now it doesn't work after upgrade to version 10.9.11 

From Docker logs found this:

Code:
[15:17:08] [INF] [1] Emby.Server.Implementations.ApplicationHost: Loading assemblies
[15:17:08] [INF] [1] Emby.Server.Implementations.Plugins.PluginManager: Loaded assembly Jellyfin.Plugin.OpenSubtitles, Version=20.0.0.0, Culture=neutral, PublicKeyToken=null from /config/data/plugins/Open Subtitles_20.0.0.0/Jellyfin.Plugin.OpenSubtitles.dll
[15:17:08] [INF] [1] Jellyfin.Networking.Manager.NetworkManager: Defined LAN subnets: ["::1/128", "fe80::/10", "fc00::/7", "127.0.0.1/8", "10.0.0.0/8", "172.16.0.0/12", "192.168.0.0/16"]
[15:17:08] [INF] [1] Jellyfin.Networking.Manager.NetworkManager: Defined LAN exclusions: []
[15:17:08] [INF] [1] Jellyfin.Networking.Manager.NetworkManager: Used LAN subnets: ["::1/128", "fe80::/10", "fc00::/7", "127.0.0.1/8", "10.0.0.0/8", "172.16.0.0/12", "192.168.0.0/16"]
[15:17:08] [INF] [1] Jellyfin.Networking.Manager.NetworkManager: Filtered interface addresses: ["127.0.0.1", "192.168.0.2", "10.21.0.6", "::1"]
[15:17:08] [INF] [1] Jellyfin.Networking.Manager.NetworkManager: Bind Addresses ["::"]
[15:17:08] [INF] [1] Jellyfin.Networking.Manager.NetworkManager: Remote IP filter is Allowlist
[15:17:08] [INF] [1] Jellyfin.Networking.Manager.NetworkManager: Filtered subnets: []
Fontconfig error: No writable cache directories
Fontconfig error: No writable cache directories
Fontconfig error: No writable cache directories
Fontconfig error: No writable cache directories
[15:17:12] [INF] [1] Emby.Server.Implementations.Plugins.PluginManager: Loaded plugin: Open Subtitles 20.0.0.0
[15:17:12] [INF] [1] Emby.Server.Implementations.Plugins.PluginManager: Loaded plugin: TMDb 10.9.11.0
[15:17:12] [INF] [1] Emby.Server.Implementations.Plugins.PluginManager: Loaded plugin: Studio Images 10.9.11.0
[15:17:12] [INF] [1] Emby.Server.Implementations.Plugins.PluginManager: Loaded plugin: OMDb 10.9.11.0
[15:17:12] [INF] [1] Emby.Server.Implementations.Plugins.PluginManager: Loaded plugin: MusicBrainz 10.9.11.0
[15:17:12] [INF] [1] Emby.Server.Implementations.Plugins.PluginManager: Loaded plugin: AudioDB 10.9.11.0
[15:17:12] [WRN] [1] Microsoft.AspNetCore.DataProtection.Repositories.EphemeralXmlRepository: Using an in-memory repository. Keys will not be persisted to storage.

Is there an issue with subnets? How to fix?


RE: Can't access server after upgrade. - TheDreadPirate - 2024-10-17

The "Filtered interface addresses" don't line up with your docker network. Not sure if that is the problem.

If you've been using this compose for a while, make sure that there wasn't an update to docker that might have broken it.