Jellyfin Forum
SOLVED: Plugin Manifest Error - Printable Version

+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: SOLVED: Plugin Manifest Error (/t-solved-plugin-manifest-error)

Plugin Manifest Error - xenodius - 2024-05-18

Been a user for years, generally without issue, but I just updated to 10.9.2 and found my server wasn't available. Checked logs and I see there's an issue getting the plugin manifest. No log entries from connection attempts to the server via Windows client or webui. Looked around and don't see others with this issue... 

The relevant logs:
Code:
[22:49:18] [ERR] [11] Emby.Server.Implementations.Updates.InstallationManager: An error occurred while accessing the plugin manifest: https://repo.jellyfin.org/files/plugin/manifest.json
System.Net.Http.HttpRequestException: Resource temporarily unavailable (repo.jellyfin.org:443)
---> System.Net.Sockets.SocketException (11): Resource temporarily unavailable
  at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken)
  at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource.GetResult(Int16 token)
  at System.Net.Sockets.Socket.<ConnectAsync>g__WaitForConnectWithCancellation|285_0(AwaitableSocketAsyncEventArgs saea, ValueTask connectTask, CancellationToken cancellationToken)
  at Jellyfin.Networking.HappyEyeballs.HttpClientExtension.AttemptConnection(AddressFamily addressFamily, SocketsHttpConnectionContext context, CancellationToken cancellationToken)
  at Jellyfin.Networking.HappyEyeballs.HttpClientExtension.OnConnect(SocketsHttpConnectionContext context, CancellationToken cancellationToken)
  at System.Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(String host, Int32 port, HttpRequestMessage initialRequest, Boolean async, CancellationToken cancellationToken)
  --- End of inner exception stack trace ---
  at System.Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(String host, Int32 port, HttpRequestMessage initialRequest, Boolean async, CancellationToken cancellationToken)
  at System.Net.Http.HttpConnectionPool.ConnectAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
  at System.Net.Http.HttpConnectionPool.CreateHttp11ConnectionAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
  at System.Net.Http.HttpConnectionPool.AddHttp11ConnectionAsync(QueueItem queueItem)
  at System.Threading.Tasks.TaskCompletionSourceWithCancellation`1.WaitWithCancellationAsync(CancellationToken cancellationToken)
  at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken)
  at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
  at System.Net.Http.DecompressionHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
  at Microsoft.Extensions.Http.Logging.LoggingHttpMessageHandler.<SendCoreAsync>g__Core|5_0(HttpRequestMessage request, Boolean useAsync, CancellationToken cancellationToken)
  at Microsoft.Extensions.Http.Logging.LoggingScopeHttpMessageHandler.<SendCoreAsync>g__Core|5_0(HttpRequestMessage request, Boolean useAsync, CancellationToken cancellationToken)
  at System.Net.Http.HttpClient.<SendAsync>g__Core|83_0(HttpRequestMessage request, HttpCompletionOption completionOption, CancellationTokenSource cts, Boolean disposeCts, CancellationTokenSource pendingRequestsCts, CancellationToken originalCancellationToken)
  at System.Net.Http.Json.HttpClientJsonExtensions.<FromJsonAsyncCore>g__Core|12_0[TValue,TJsonOptions](HttpClient client, Task`1 responseTask, Boolean usingResponseHeadersRead, CancellationTokenSource linkedCTS, Func`4 deserializeMethod, TJsonOptions jsonOptions, CancellationToken cancellationToken)
  at Emby.Server.Implementations.Updates.InstallationManager.GetPackages(String manifestName, String manifest, Boolean filterIncompatible, CancellationToken cancellationToken)
[22:49:18] [INF] [11] Emby.Server.Implementations.ScheduledTasks.TaskManager: Update Plugins Completed after 0 minute(s) and 10 seconds

I exec'd into my Jellyfin docker container, and I was nonetheless able to grab the manifest manually with wget:

Code:
[xenodius@MantisToboggan Jellyfin]$ wget https://repo.jellyfin.org/files/plugin/manifest.json
--2024-05-17 23:05:58--  https://repo.jellyfin.org/files/plugin/manifest.json
Resolving repo.jellyfin.org... 68.183.204.194, 2604:a880:cad:d0::cf3:f001
Connecting to repo.jellyfin.org|68.183.204.194|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://nyc1.mirror.jellyfin.org/files/plugin/manifest.json [following]
--2024-05-17 23:05:58--  https://nyc1.mirror.jellyfin.org/files/plugin/manifest.json
Resolving nyc1.mirror.jellyfin.org... 142.93.199.247, 2604:a880:400:d0::21a8:3001
Connecting to nyc1.mirror.jellyfin.org|142.93.199.247|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 120102 (117K) [application/json]
Saving to: ‘manifest.json’


RE: Plugin Manifest Error - TheDreadPirate - 2024-05-18

Can you try again? It may have been a transient issue. I don't see any blips in the NYC mirror's status.

RE: Plugin Manifest Error - xenodius - 2024-05-18

Yea... I tried deleting network.xml or setting
Code:
<IgnoreVirtualInterfaces>false</IgnoreVirtualInterfaces>
in network.xml, didn't work. No matter how long I leave the server running, there's no additional startup/log entries after the plugin manifest error. I also tried restarting the container several dozens of times over the last couple hours, and the QNAP NAS I'm running the container in several times...

Might try wiping the container directory and starting over/copying my old database tomorrow, I dunno what's wrong.

Can I manually put the manifest somewhere in the appdata directory to avoid it having to pull it?

RE: Plugin Manifest Error - TheDreadPirate - 2024-05-18

Try stopping the container, pruning the system of images and the VFS, then start it back up.

RE: Plugin Manifest Error - xenodius - 2024-05-18

Done-- stopped it, wiped the directory, pruned images, pulled, and with an absolutely fresh installation... I still get the same error. Makes me think it must be device related, but I've got a ton of other containers working perfectly fine and it worked before. I'll try again with 10.9.0 or earlier later, see what happens. In the meantime, open to other suggestions...

RE: Plugin Manifest Error - xenodius - 2024-05-18

I updated the firmware on my QNAP and performed a complete factory reset, but I still have this problem. Jellyfin hangs on start after failing to access the plugin manifest. My other 13 containers work perfectly fine. I tried using curl on some addresses in various containers, and despite being connected to the same virtual adapter, my Jellyfin container doesn't have internet access but everything else does. (e.g. curl http://www.google.com and curl https://repo.jellyfin.org/files/plugin/manifest.json both fail) I'm not sure why updating Jellyfin using the same compose file would break network connectivity, but at least I have a problem to investigate.

EDIT: Previously, I used
Code:
docker image prune
instead of
Code:
docker system prune -a
, after stopping the container, running the latter prune, and restarting it works just fine. Thanks TheDreadPirate!

RE: Plugin Manifest Error - TheDreadPirate - 2024-05-18

Neat. I would have given you that latter prune command if I knew QNAP could do straight up docker commands.