Jellyfin is slow or unresponsive after update

[cosci]

Hi, I have a question about the Jellyfin updates. Did any of you also have problems with the update to 10.11.5?
The update itself went smoothly, but since I installed the latest version in November or December, everything feels very sluggish and unresponsive. I often have problems with the Findroid app; no content loads, or I get a timeout error. Everything worked perfectly before.

At first, I didn't really notice it because I hadn't used Jellyfin much after the update, and I was also converting TV shows and movies on the same device. I thought that might be the reason, but even now, with the server idle, everything loads very slowly.

I'm using a Windows VM on a Proxmox server. The VM has 8 cores of an AMD Ryzen 3700x, 32GB of RAM, and an Nvidia Quadro P620.

Do you have any tips on how I could fix the problem, or would a reinstallation and data migration via API the better option?

I use Findroid and the official Jellyfin App on my Samsung Galaxy Tab S6 and an Alldocube iPlay, both are Android Tablets. I use Jellyfin behind an Nginx Reverse Proxy over Wifi or 5g on my Tablets. Same Problem happens when i use the IP and Port of my Server without Nginx Reverse Proxy. 

Code:

Connection timed out or was interrupted
ch.f: Connection timed out or was interrupted
at eh.f.b(r8-map-id-edb2440395329bf3056da4b43e38059a9bfb62f712e7be6cb5f4151d2de57a73:563)
at eh.e.invokeSuspend(r8-map-id-edb2440395329bf3056da4b43e38059a9bfb62f712e7be6cb5f4151d2de57a73:18)
at he.a.resumeWith(r8-map-id-edb2440395329bf3056da4b43e38059a9bfb62f712e7be6cb5f4151d2de57a73:9)
at hf.k0.run(r8-map-id-edb2440395329bf3056da4b43e38059a9bfb62f712e7be6cb5f4151d2de57a73:107)
at hc.t.run(r8-map-id-edb2440395329bf3056da4b43e38059a9bfb62f712e7be6cb5f4151d2de57a73:104)
at pf.j.run(r8-map-id-edb2440395329bf3056da4b43e38059a9bfb62f712e7be6cb5f4151d2de57a73:3)
at pf.a.run(r8-map-id-edb2440395329bf3056da4b43e38059a9bfb62f712e7be6cb5f4151d2de57a73:88)
Caused by: java.net.SocketTimeoutException: timeout
at og.w.k(r8-map-id-edb2440395329bf3056da4b43e38059a9bfb62f712e7be6cb5f4151d2de57a73:5)
at og.w.m(r8-map-id-edb2440395329bf3056da4b43e38059a9bfb62f712e7be6cb5f4151d2de57a73:9)
at og.q.c(r8-map-id-edb2440395329bf3056da4b43e38059a9bfb62f712e7be6cb5f4151d2de57a73:64)
at a6.g0.j(r8-map-id-edb2440395329bf3056da4b43e38059a9bfb62f712e7be6cb5f4151d2de57a73:5)
at mg.c.a(r8-map-id-edb2440395329bf3056da4b43e38059a9bfb62f712e7be6cb5f4151d2de57a73:223)
at g0.a0.f(r8-map-id-edb2440395329bf3056da4b43e38059a9bfb62f712e7be6cb5f4151d2de57a73:130)
at lg.a.a(r8-map-id-edb2440395329bf3056da4b43e38059a9bfb62f712e7be6cb5f4151d2de57a73:129)
at g0.a0.f(r8-map-id-edb2440395329bf3056da4b43e38059a9bfb62f712e7be6cb5f4151d2de57a73:130)
at jg.a.a(r8-map-id-edb2440395329bf3056da4b43e38059a9bfb62f712e7be6cb5f4151d2de57a73:602)
at g0.a0.f(r8-map-id-edb2440395329bf3056da4b43e38059a9bfb62f712e7be6cb5f4151d2de57a73:130)
at mg.a.a(r8-map-id-edb2440395329bf3056da4b43e38059a9bfb62f712e7be6cb5f4151d2de57a73:547)
at g0.a0.f(r8-map-id-edb2440395329bf3056da4b43e38059a9bfb62f712e7be6cb5f4151d2de57a73:130)
at mg.a.a(r8-map-id-edb2440395329bf3056da4b43e38059a9bfb62f712e7be6cb5f4151d2de57a73:219)
at g0.a0.f(r8-map-id-edb2440395329bf3056da4b43e38059a9bfb62f712e7be6cb5f4151d2de57a73:130)
at lg.n.h(r8-map-id-edb2440395329bf3056da4b43e38059a9bfb62f712e7be6cb5f4151d2de57a73:86)
at lg.k.run(r8-map-id-edb2440395329bf3056da4b43e38059a9bfb62f712e7be6cb5f4151d2de57a73:50)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1154)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:652)
at java.lang.Thread.run(Thread.java:1563)

[The Black Reverand]

Hi cosci

What is your original version? Migrate from xx to 10.11.5

Have you made backup before migration?

Do you have someting in Jellyfin logs?

The TimeOut, it's a log from your client?

[cosci]

Hi, the old version should be 10.10.7, i don't have the backups anymore. Before that i already upgraded a couple of times(most of the time i only update when my tv client says i have to update, so maybe 2 or 3 times a year.), i think i use jellyfin now for 3 or 4 years and startet with the client in a linux container and then moved it to the windows portable version and migratet my data with the api.
the timeout error is inside the findroid client, but the official app also doesn't load. so far i noticed that when i restart jellyfin or my windows vm that it's working again for some time.

[cosci]

might have found something, after checking the logs a couple of times with chatgpt and claude i disabled the kodi sync plugin which i might have tested a couple of years ago so far after 2 days it seems usable again