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
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.