SOLVED: Chromecast wont connect

[UnexpectedQuagmire]

Hello!

Not sure why but all of a sudden neither my Chromecast 4k or Chromecast HD are able to connect to my Jellyfin server. It discovers the correct address for my server on my LAN but gives an "Unable to connect, tried the following addresses:" error. 

Both the Chromecast worked flawlessly for the last year, it has only occurred in the last week.

The server is hosted on my PC with wifi (eero 6). I can still access the server on my PC without issue through http://localhost:8096/, and also on my Android Phone!

Server is running 10.9.9 and both Chromecast Jellyfin apps are up to date. 

Not really sure what to try next, any suggestions would be greatly appreciated! The failed login attempt doesn't seem to trigger any log.

Thank you

[TheDreadPirate]

I'm assuming the Android TV app updated to 0.18 recently. If that is correct, you will need to upgrade your server to 10.10, which is a requirement new to Android TV 0.18. Or you can downgrade the Android TV app to 0.17.9.

[UnexpectedQuagmire]

Thank you for the suggestion. I've updated it to 10.10.3, yet the problem is still persisting .

Some updates:

My Android phone app is no longer connecting. It shows my PC under Select Server, then when I try to connect it says "we're unable to connect to the selected server right now. Please ensure it is running and try again".

Using a Web Browser on both my Phone and Chromecast, when I go to the 192.168.4.27:8096 server IP it brings up the Jellyfin page but says "No servers have been found using the automatic server discovery".

[TheDreadPirate]

For the phone, clear the app cache. Same with the app on your Chromecast.

And can you share your jellyfin logs via pastebin?

[UnexpectedQuagmire]

For the phone, clear the app cache.  Same with the app on your Chromecast.

And can you share your jellyfin logs via pastebin?

https://pastebin.com/***

[UnexpectedQuagmire]

So it looks like "Allow remote connections to this server" was unticked. No idea why that was set to Off, as it was working fine all year. Anyway, it's all sorted now!