jellyfin / jellyfin-media-player

Jellyfin Desktop Client
GNU General Public License v2.0
2.87k stars 297 forks source link

Only Windows clients unable to connect to server. #684

Open nhathaway opened 3 weeks ago

nhathaway commented 3 weeks ago

I updated to the latest jellyfin windows media player today and now it no longer connects. You can connect via the web browser but no longer via the jellyfin windows media player. It connected OK before the update. The new version is 1.11.0

nhathaway commented 3 weeks ago

I have downgraded back to 1.10.1 and everything is working OK on that version.

I looked at the server logs, and there was no mention of any attempt to connect using the new version.

nhathaway commented 3 weeks ago

I don't know if it makes any difference, but I access jellyfin over https using a reverse proxy.

Jellyfin server version: 10.9.6

kloon15 commented 3 weeks ago

Same issue, suddenly wont connect at all, and the button stays disabled so cant even retry.

nhathaway commented 3 weeks ago

Same issue, suddenly wont connect at all, and the button stays disabled so cant even retry.

Yes, I found that too. Once it had tried once, you can't retry without closing the app and restarting it again.

vincejv commented 3 weeks ago

I think we should merge it with https://github.com/jellyfin/jellyfin-media-player/issues/683

I'm experiencing the same with Linux Desktop client, all the mobile clients and chrome (web) works

oddstr13 commented 3 weeks ago

Button staying disabled seems to happen when hitting the public api endpoint succeeds, but navigating to the web interface fails

xAphex commented 3 weeks ago

issue still persists with JMP 1.11.1 and jellyfin 10.9.6

fatexs commented 3 weeks ago

can you try deleting C:\Users\user\AppData\Local\Jellyfin Media Player and C:\Users\user\AppData\Local\JellyfinMediaPlayer ?

xAphex commented 3 weeks ago

can you try deleting C:\Users\user\AppData\Local\Jellyfin Media Player and C:\Users\user\AppData\Local\JellyfinMediaPlayer ?

already did that and uninstalled JMP, its a problem with JMP, it reaches an endpoint that requires authentication and stops there.

IradColdheart commented 3 weeks ago

Just in case, i faced the same issue : it was working through the reverse proxy, but through a direct access. Adding the subpath to the IP for direct access corrected the issue though : http://192.168.1.x:8096/subpath (url subpath being defined in Jellyfin network settings).

valankar commented 23 hours ago

How come this is still not fixed? I still have to resort to older version.