SOLVED: Upgrade killed server connection? :(

[ExistentialJazz]

Version: 10.9.11 (upgraded from 10.8.13)
Platform: Debian Linux server
Problem Summary: After upgrading Jellyfin running on my server, I can no longer access it.

I am sure this is easy, but networking and linux are not my strong suits.

I have been using jellyfin across many devices successfully for a while, it has been great! Lately I noticed Jellyfin was no longer working on Android TV (not how I normally access), so I decided to upgrade - the TV app said a newer version was needed.

I re-downloaded from the repository directly, which from my understanding should just install the latest version over the old one - keeping the server settings.

curl -s https://repo.jellyfin.org/install-debuntu.sh

---

Once this was completed it said, "Active and running" below it said, "You can access your new instance now at http://192.168.0.156:8096 in your web browser to finish setting up Jellyfin."
When I enter this IP (which is what I have been using locally all along) - the Jellyfin page comes up, and if I am in a browser/device that I have used before to access it, it will even show my server name as an option, but when I click to connect it says, "We're unable to connect to the selected server right now. Please ensure it is running and try again."

I have tried accessing on both Windows and Mac, both on the local IP and my VPN (which is how I normally hit the server).

---

So what have I done wrong??

Thanks for the assistance!

[gnattu]

Did you try clear your browser cache first>

[TheDreadPirate]

You can also do ctrl+f5 to fully refresh.  If you don't want to clear your entire browser's cache, you can just clear Jellyfin's cache.

   
   
   

[ExistentialJazz]

Yes, I did try connecting in a browser that has no previous cookies.
I did try deleting the cache on Windows and Mac this morning. When I hit the jellyfin splash screen it gives an option to "add server" and then it asks for the host IP. When I enter that in (the exact IP I have been using for many months and what Jellyfin gave as the access point when installed) it gives the same message, "We're unable to connect to the selected server right now. Please ensure it is running and try again."

----

Did I need to remove Jellyfin before reinstalling it on the Debian server?

Thanks again for the help, I appreciate it.

[TheDreadPirate]

Can you share your server logs via pastebin?

You would only see the "add server" window if you are viewing a cached page.

[ExistentialJazz]

Apologies,
what log file specifically are you looking for?

In Debian with ls /var/log/jellyfin

I am seeing:

FFmpeg.DirectStream-2024-09-10_17-24-03_c68860187c47463007747a5a96e4abf8_2177e2fe.log  FFmpeg.Transcode-2024-09-10_16-16-01_fa12dd59ca6cc0db435d6bd49c935042_ef83b831.log  jellyfin20240909.log
FFmpeg.Transcode-2024-09-09_22-17-48_0e1e16a38521b5e3bdf487467840e948_bd06449d.log    FFmpeg.Transcode-2024-09-10_16-56-18_c8e711cfcfca8d3909f60f5b3ddcc80a_f4125d50.log  jellyfin20240910.log
FFmpeg.Transcode-2024-09-09_22-42-02_686b2d33899ae3e75b7a8bdc903eee28_3a26228c.log    jellyfin20240908.log   jellyfin20240911.log

[TheDreadPirate]

jellyfin20240911.log

[ExistentialJazz]

Longer log file than I thought it would be - granted I haven't seen one before either though!


[/url][url=https://pastebin.com/yi9NFkvA]Paste-bin Linky

[TheDreadPirate]

Can you restart the service and then share the new log? I need to see the startup sequence.

[ExistentialJazz]

Rebooted: https://pastebin.com/4mKNLbyZ