12

Can't connect to server after updating to 10.9.9

posted
*
by
Avatar
GeekySalsa@lemmy.world
in
Avatar
jellyfin@lemmy.ml
13 comments
hidereport

As the title says, I just upgraded to 10.9.9 and now I can’t connect to the server. I have it installed on a docker container on a headless ubuntu machine. This is the first time I’ve updated after installing and successfully using the server for several months. I followed the instructions in the first response here: link

Originally, the update/install seemed to work just fine. I opened up a client on a browser and it successfully connected and prompted the install wizard. So I went through it and re-pointed to all of my media. However, at the very last step when clicking submit, it got stuck. I saw online that this happened to others and what worked for them was to just try again.

So, after some time, I restarted the server and restarted the above process, except now I’m unable to connect at all.

When trying to connect from my Nvidia Shield, it tells me to complete the setup on a browser. When connecting on a browser, it asks me to select a server, lists the server, and then fails to connect to it with the error “We’re unable to connect to the selected server right now. Please ensure it is running and try again”. Connecting on my android phone and connecting in incognito prompts the same error.

Also, I’m unable to see any new logs now. ~/jellyfin/config/log has 3 log files from the last 3 days. But the latest one seems to have stopped around the time of the upgrade and shows no errors. I’ve updated the logging.json file as per the instructions here and this does not help: debug-logging

Does anyone have any advice here?

UPDATE: Issue seems to be solved. Tailscale seemed to be causing some problem on the client-side. Disabling and reattempting seemed to work. The library is still being scanned, so I haven’t validated playback. But I can at least navigate my content now.

UPDATE 2: Playback is validated

Sort:
HotTopControversialNewOld
Avatar
Shadow@lemmy.ca
4 points

What’s the output of docker log?

permalink
report
reply
Avatar
diminou@lemmy.zip
3 points

And what image are you using for your container?

permalink
report
parent
reply
Avatar
GeekySalsa@lemmy.worldOP
2 points

jellyfin/jellyfin:latest

permalink
report
parent
reply
Avatar
doeknius_gloek@discuss.tchncs.de
3 points

Do yourself a favor and do not use the latest tag. Always use the tag for the explicit version you want. Makes things a lot more stable.

You also mentioned that jellyfin prompted you with the installation wizard after the update. It seems like you fixed your problem but for the next time: this is not expected behaviour. A short downtime right after the new container started is normal but afterwards the server should run normally with the same configuration as before.

permalink
report
parent
reply
Avatar
GeekySalsa@lemmy.worldOP
1 point
*

These are the last logs before they stopped showing up:

spoiler
  • [2024-08-07 06:38:53.717 +00:00] [WRN] [11] Microsoft.EntityFrameworkCore.Model.Validation: The entity type ‘“AccessSchedule”’ is configured to use schema ‘“jellyfin”’, but SQLite does not support schemas. This configuration will be ignored by the SQLite provider.
  • [2024-08-07 06:38:53.718 +00:00] [WRN] [11] Microsoft.EntityFrameworkCore.Model.Validation: The entity type ‘“ActivityLog”’ is configured to use schema ‘“jellyfin”’, but SQLite does not support schemas. This configuration will be ignored by the SQLite provider.
  • [2024-08-07 06:38:53.718 +00:00] [WRN] [11] Microsoft.EntityFrameworkCore.Model.Validation: The entity type ‘“CustomItemDisplayPreferences”’ is configured to use schema ‘“jellyfin”’, but SQLite does not support schemas. This configuration will be ignored by the SQLite provider.
  • [2024-08-07 06:38:53.718 +00:00] [WRN] [11] Microsoft.EntityFrameworkCore.Model.Validation: The entity type ‘“DisplayPreferences”’ is configured to use schema ‘“jellyfin”’, but SQLite does not support schemas. This configuration will be ignored by the SQLite provider.
  • [2024-08-07 06:38:53.718 +00:00] [WRN] [11] Microsoft.EntityFrameworkCore.Model.Validation: The entity type ‘“HomeSection”’ is configured to use schema ‘“jellyfin”’, but SQLite does not support schemas. This configuration will be ignored by the SQLite provider.
  • [2024-08-07 06:38:53.718 +00:00] [WRN] [11] Microsoft.EntityFrameworkCore.Model.Validation: The entity type ‘“ImageInfo”’ is configured to use schema ‘“jellyfin”’, but SQLite does not support schemas. This configuration will be ignored by the SQLite provider.
  • [2024-08-07 06:38:53.718 +00:00] [WRN] [11] Microsoft.EntityFrameworkCore.Model.Validation: The entity type ‘“ItemDisplayPreferences”’ is configured to use schema ‘“jellyfin”’, but SQLite does not support schemas. This configuration will be ignored by the SQLite provider.
  • [2024-08-07 06:38:53.718 +00:00] [WRN] [11] Microsoft.EntityFrameworkCore.Model.Validation: The entity type ‘“Permission”’ is configured to use schema ‘“jellyfin”’, but SQLite does not support schemas. This configuration will be ignored by the SQLite provider.
  • [2024-08-07 06:38:53.718 +00:00] [WRN] [11] Microsoft.EntityFrameworkCore.Model.Validation: The entity type ‘“Preference”’ is configured to use schema ‘“jellyfin”’, but SQLite does not support schemas. This configuration will be ignored by the SQLite provider.
  • [2024-08-07 06:38:53.718 +00:00] [WRN] [11] Microsoft.EntityFrameworkCore.Model.Validation: The entity type ‘“ApiKey”’ is configured to use schema ‘“jellyfin”’, but SQLite does not support schemas. This configuration will be ignored by the SQLite provider.
  • [2024-08-07 06:38:53.718 +00:00] [WRN] [11] Microsoft.EntityFrameworkCore.Model.Validation: The entity type ‘“Device”’ is configured to use schema ‘“jellyfin”’, but SQLite does not support schemas. This configuration will be ignored by the SQLite provider.
  • [2024-08-07 06:38:53.718 +00:00] [WRN] [11] Microsoft.EntityFrameworkCore.Model.Validation: The entity type ‘“DeviceOptions”’ is configured to use schema ‘“jellyfin”’, but SQLite does not support schemas. This configuration will be ignored by the SQLite provider.
  • [2024-08-07 06:38:53.718 +00:00] [WRN] [11] Microsoft.EntityFrameworkCore.Model.Validation: The entity type ‘“User”’ is configured to use schema ‘“jellyfin”’, but SQLite does not support schemas. This configuration will be ignored by the SQLite provider.
  • [2024-08-07 06:39:17.228 +00:00] [INF] [10] Jellyfin.Networking.Manager.NetworkManager: Defined LAN addresses : “* [10.0.0.0/8,172.16.0.0/12,192.168.0.0/16]”
  • [2024-08-07 06:39:17.228 +00:00] [INF] [10] Jellyfin.Networking.Manager.NetworkManager: Defined LAN exclusions : “[]”
  • [2024-08-07 06:39:17.229 +00:00] [INF] [10] Jellyfin.Networking.Manager.NetworkManager: Using LAN addresses: “[10.0.0.0/8,172.16.0.0/12,192.168.0.0/16]”
  • [2024-08-07 06:39:18.297 +00:00] [INF] [20] Emby.Dlna.DlnaManager: No matching device profile found. The default will need to be used. DeviceIdentification { FriendlyName: “Aquaria”, ModelNumber: “1.0”, SerialNumber: “”, ModelName: “LG TV”, ModelDescription: “LG WebOSTV DMRplus”, ModelUrl: “”, Manufacturer: “LG Electronics.”, ManufacturerUrl: “http://www.lge.com”, Headers: [] }
  • [2024-08-07 06:39:18.303 +00:00] [INF] [20] Emby.Dlna.Main.DlnaEntryPoint: DLNA Session created for “Aquaria” - “LG TV”
  • [2024-08-07 06:39:19.233 +00:00] [INF] [20] Jellyfin.Networking.Manager.NetworkManager: Defined LAN addresses : “[10.0.0.0/8,172.16.0.0/12,192.168.0.0/16]”
  • [2024-08-07 06:39:19.233 +00:00] [INF] [20] Jellyfin.Networking.Manager.NetworkManager: Defined LAN exclusions : “[]”
  • [2024-08-07 06:39:19.234 +00:00] [INF] [20] Jellyfin.Networking.Manager.NetworkManager: Using LAN addresses: “[10.0.0.0/8,172.16.0.0/12,192.168.0.0/16]”
  • [2024-08-07 06:39:21.232 +00:00] [INF] [8] Jellyfin.Networking.Manager.NetworkManager: Defined LAN addresses : “[10.0.0.0/8,172.16.0.0/12,192.168.0.0/16]”
  • [2024-08-07 06:39:21.232 +00:00] [INF] [8] Jellyfin.Networking.Manager.NetworkManager: Defined LAN exclusions : “[]”
  • [2024-08-07 06:39:21.232 +00:00] [INF] [8] Jellyfin.Networking.Manager.NetworkManager: Using LAN addresses: “[10.0.0.0/8,172.16.0.0/12,192.168.0.0/16]”
  • [2024-08-07 06:39:23.237 +00:00] [INF] [11] Jellyfin.Networking.Manager.NetworkManager: Defined LAN addresses : “[10.0.0.0/8,172.16.0.0/12,192.168.0.0/16]”
  • [2024-08-07 06:39:23.237 +00:00] [INF] [11] Jellyfin.Networking.Manager.NetworkManager: Defined LAN exclusions : “[]”
  • [2024-08-07 06:39:23.237 +00:00] [INF] [11] Jellyfin.Networking.Manager.NetworkManager: Using LAN addresses: “[10.0.0.0/8,172.16.0.0/12,192.168.0.0/16]”
  • [2024-08-07 06:39:25.240 +00:00] [INF] [11] Jellyfin.Networking.Manager.NetworkManager: Defined LAN addresses : “[10.0.0.0/8,172.16.0.0/12,192.168.0.0/16]”
  • [2024-08-07 06:39:25.240 +00:00] [INF] [11] Jellyfin.Networking.Manager.NetworkManager: Defined LAN exclusions : “[]”
  • [2024-08-07 06:39:25.240 +00:00] [INF] [11] Jellyfin.Networking.Manager.NetworkManager: Using LAN addresses: “[10.0.0.0/8,172.16.0.0/12,192.168.0.0/16]”
  • [2024-08-07 06:45:16.881 +00:00] [INF] [2] Main: Received a SIGTERM signal, shutting down
  • [2024-08-07 06:45:16.881 +00:00] [INF] [2] Main: Running query planner optimizations in the database… This might take a while
  • [2024-08-07 06:45:16.888 +00:00] [INF] [2] Emby.Server.Implementations.ApplicationHost: Disposing “CoreAppHost”
  • [2024-08-07 06:45:16.889 +00:00] [INF] [2] Emby.Server.Implementations.ApplicationHost: Disposing “UserDataChangeNotifier”
  • [2024-08-07 06:45:16.889 +00:00] [INF] [2] Emby.Server.Implementations.ApplicationHost: Disposing “ExternalPortForwarding”
  • [2024-08-07 06:45:16.890 +00:00] [INF] [2] Emby.Server.Implementations.EntryPoints.ExternalPortForwarding: Stopping NAT discovery
  • [2024-08-07 06:45:16.892 +00:00] [INF] [2] Emby.Server.Implementations.ApplicationHost: Disposing “DlnaEntryPoint”
  • [2024-08-07 06:45:16.892 +00:00] [INF] [2] Emby.Dlna.Main.DlnaEntryPoint: Disposing PlayToManager
  • [2024-08-07 06:45:16.893 +00:00] [INF] [2] Emby.Dlna.Main.DlnaEntryPoint: Disposing DeviceDiscovery
  • [2024-08-07 06:45:16.893 +00:00] [INF] [2] Emby.Dlna.Main.DlnaEntryPoint: Disposing SsdpCommunicationsServer
  • [2024-08-07 06:45:16.893 +00:00] [INF] [2] Emby.Dlna.Main.DlnaEntryPoint: “SsdpCommunicationsServer” disposing _BroadcastListenSocket
  • [2024-08-07 06:45:16.895 +00:00] [INF] [2] Emby.Dlna.Main.DlnaEntryPoint: “SsdpCommunicationsServer” Disposing 3 sendSockets
  • [2024-08-07 06:45:16.895 +00:00] [INF] [2] Emby.Dlna.Main.DlnaEntryPoint: “SsdpCommunicationsServer” disposing sendSocket from “0.0.0.0”
  • [2024-08-07 06:45:16.895 +00:00] [INF] [2] Emby.Dlna.Main.DlnaEntryPoint: “SsdpCommunicationsServer” disposing sendSocket from “10.0.0.23”
  • [2024-08-07 06:45:16.895 +00:00] [INF] [2] Emby.Dlna.Main.DlnaEntryPoint: “SsdpCommunicationsServer” disposing sendSocket from “127.0.0.1”
  • [2024-08-07 06:45:16.895 +00:00] [INF] [2] Emby.Server.Implementations.ApplicationHost: Disposing “MusicBrainzAlbumProvider”
  • [2024-08-07 06:45:16.895 +00:00] [INF] [2] Emby.Server.Implementations.ApplicationHost: Disposing “DeviceAccessEntryPoint”
  • [2024-08-07 06:45:16.895 +00:00] [INF] [2] Emby.Server.Implementations.ApplicationHost: Disposing “EntryPoint”
  • [2024-08-07 06:45:16.895 +00:00] [INF] [2] Emby.Server.Implementations.ApplicationHost: Disposing “EntryPoint”
  • [2024-08-07 06:45:16.895 +00:00] [INF] [2] Emby.Server.Implementations.ApplicationHost: Disposing “NotificationEntryPoint”
  • [2024-08-07 06:45:16.896 +00:00] [INF] [2] Emby.Server.Implementations.ApplicationHost: Disposing “EmbyTV”
  • [2024-08-07 06:45:16.897 +00:00] [INF] [2] Emby.Server.Implementations.ApplicationHost: Disposing “SchedulesDirect”
  • [2024-08-07 06:45:16.897 +00:00] [INF] [2] Emby.Server.Implementations.ApplicationHost: Disposing “LibraryChangedNotifier”
  • [2024-08-07 06:45:16.898 +00:00] [INF] [2] Emby.Server.Implementations.ApplicationHost: Disposing “RecordingNotifier”
  • [2024-08-07 06:45:16.899 +00:00] [INF] [2] Emby.Server.Implementations.ApplicationHost: Disposing “UdpServerEntryPoint”
  • [2024-08-07 06:45:16.899 +00:00] [INF] [2] Emby.Server.Implementations.ApplicationHost: Disposing “LibraryMonitorStartup”
permalink
report
parent
reply
Avatar
Shadow@lemmy.ca
3 points

To clarify I mean specifically the output of the “docker logs jellyfin” command, not the log file you were looking at.

If jellyfin isn’t starting properly it may not make it to its own logs, but the docker output will likely catch more.

permalink
report
parent
reply
Avatar
GeekySalsa@lemmy.worldOP
0 points

Oh! I wasn’t aware of these logs. Yep, I’m seeing an error repeating many times here: “Unhandled exception. System.UnauthorizedAccessException: Access to the path ‘/config/config/migrations.xml’ is denied.”

permalink
report
parent
reply
Show more comments

Jellyfin: The Free Software Media System

!jellyfin@lemmy.ml

Create post

Current stable release: 10.9.7

Community Standards

Website

Forum

GitHub

Documentation

Feature Requests

Matrix (General Information & Help)

Matrix (Announcements)

Matrix (General Development)

Matrix (Off-Topic) - Come get to know the team and blow off steam!

Matrix Space - List of all the available rooms on Matrix.

Discord - Bridged to our Matrix rooms

Community stats

  • 413

    Monthly active users

  • 136

    Posts

  • 466

    Comments

Community moderators