Unable to access webgui after update

[Huecuva]

I'm running Jellyfin in a headless Debian VM. I noticed today that I was unable to access my Jellyfin webgui to watch any of my movies. To fix it I restored a proxmox backup of my VM to before the last Jellyfin update and was able to reach the webgui. I then tried to run updates and again lost access to the webgui. Upon doing some research I've learned that is known and (more or less) expected behaviour for this particular significant update 

Following the recommendations here, I made sure my library listed only 100 items in the webgui. I made sure I was running 10.10.7 before doing up the update and made sure that I had stopped the Jellyfin service. I then ran

Code:

sudo apt update && sudo apt upgrade jellyfin -y 

in order to upgrade Jellyfin alone and take care of other upgrades to the server afterwords. However, I am still unable to access the webgui. 

I understand from the link I posted above that it could take several hours to finish migrating my media database based on the fact that I have several TB of movies and TV shows. However, there is mentioned something called the Startup UI. I am unable to access this. If it's supposed to appear in place of the standard webgui while the server does its thing, it's not working. If not, I don't know how to access it and I can't find anywhere on the Jellyfin site where it indicates how to access the Startup UI other than it is "only accessible in your configured local networks". What does that even mean? If it's accessible on the LAN via the same IP address as the server, what port do I need to go to? Again, if it's the same as the standard webgui, then it's not working.

Can anyone tell me if this is working correctly and how to access the Startup UI or how to fix this issue if it's not?

[conor]

What does "sudo systemctl status jellyfin" show?

Plugins have been causing some problems.

You can delete/ move the folders in /var/lib/jellyfin/plugins and try starting the server.

[Huecuva]

Of course I hadn't thought to check that myself before posting. That would have told me whether it was actually working or not. However, I would still have had to post. 

Code:

× jellyfin.service - Jellyfin Media Server
    Loaded: loaded (/lib/systemd/system/jellyfin.service; enabled; preset: enabled)
    Drop-In: /etc/systemd/system/jellyfin.service.d
            └─jellyfin.service.conf
    Active: failed (Result: signal) since Sun 2025-11-09 00:01:23 PST; 5h 31min ago
  Duration: 592ms
    Process: 2043 ExecStart=/usr/bin/jellyfin $JELLYFIN_WEB_OPT $JELLYFIN_FFMPEG_OPT $JELLYFIN_SERVICE_OPT $JELLYFIN_NOWEBAPP_OPT $JELLYFIN_ADDITIONAL_OPTS (code=killed, signal=ABRT)
  Main PID: 2043 (code=killed, signal=ABRT)
        CPU: 536ms

Nov 09 00:01:23 Ilithid systemd[1]: jellyfin.service: Scheduled restart job, restart counter is at 5.
Nov 09 00:01:23 Ilithid systemd[1]: Stopped jellyfin.service - Jellyfin Media Server.
Nov 09 00:01:23 Ilithid systemd[1]: jellyfin.service: Start request repeated too quickly.
Nov 09 00:01:23 Ilithid systemd[1]: jellyfin.service: Failed with result 'signal'.
Nov 09 00:01:23 Ilithid systemd[1]: Failed to start jellyfin.service - Jellyfin Media Server.

It's not running properly. What happened and how do I fix this? I've never installed any extra plugins and the only folders in /var/lib/jellyfin/plugins are configurations and .jellyfin-plugin. Nonetheless, I copied them elsewhere and deleted them and tried to restart jellyfin. It still will not start.

As of 20 days ago this was a known and apparently very common issue. Has it not yet been addressed? I'm starting to wonder if uninstalling and reinstalling might be an easier path.

EDIT: Well, for now I'm going to roll back to 10.10.7 and set a hold on upgrading it. If someone has some idea how to get past this particular hurdle without reinstalling I will attempt it again. Otherwise, maybe I will get around to reinstalling at some point.

[Huecuva]

So I just checked 

Code:

journalctl | grep jellyfin

and apparently /var/ wasn't big enough and it was running out of space. That was what was making the migration fail.

I created a bigger drive attached to the VM and changed that to /var/. The migration has completed successfully and my Jellyfin is all up to date now.

Thanks for the help guys.

[Minecodes]

I had a similar error. When I updated today, Jellyfin crashed because of permission errors to non-existing files. The problem was that the user and group field was reset to the default ("jellyfin"). I had changed that to my user so it wouldn't have as many problems accessing my media. That could be a possibility.

[Huecuva]

No. If I recall correctly, I added the Jellyfin user to my user group so that it could access the media without an issue. It's not having any permission problems and I never changed the jellyfin user group field. I preferred to have it running under its own user.

As I stated in my last post, the issue was that it was running out of space on /var/ to do the database migration. Once I created a larger drive in my VM and attached it and changed fstab to mount it as /var/, it all went off without a hitch.

However, now I have a 4.4GB partition on sda that I don't know what to do with. If I copy /var/ from the larger drive back to the 4.4GB drive and change fstab back to the way it was, it runs out of room again, even though the migration is already done. It looks like I need to keep the separate drive as /var/ and figure out another purpose for the 4.4GB partition. Unless I can find a way to steal a couple of GB from / and add them to the 4.4GB partition and set it back as /var/. Not sure how I'm going to pull that off, though. Gparted doesn't seem to want to work right in a VM.