search

jellyfin / jellyfin-media-player

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

[Flatpak] Cannot connect to a 10.9.2 server after upgrading to JMP 1.10.1: Server's certificate is not trusted. #667

Open FranckRJ opened 1 month ago

FranckRJ commented 1 month ago

Describe the bug When I try to connect to my server I get this error message: image

Connection Failure We're unable to connect to the selected server right now. Please ensure it is running and try again.

It only happens with JMP 1.10.1, I reverted back to JMP 1.9.1 and this version works. In both cases my server was running the version 10.9.2.

To Reproduce

Expected behavior I can connect to my server.

Desktop (please complete the following information):

Logs

2024-05-26 15:56:38.009 [info] unknown @ 0 - JS: begin connectToServer
2024-05-26 15:56:38.009 [info] unknown @ 0 - JS: tryReconnect: https://myserver.com
2024-05-26 15:56:38.110 [info] unknown @ 0 - JS: getTryConnectPromise https://myserver.com
2024-05-26 15:56:38.110 [info] unknown @ 0 - JS: ConnectionManager requesting url: https://myserver.com/system/info/public
2024-05-26 15:56:38.110 [info] unknown @ 0 - JS: fetchWithTimeout: timeoutMs: 20000, url: https://myserver.com/system/info/public
2024-05-26 15:56:38.146 [debug] onCertificateError @ 221 - https://myserver.com/system/info/public :Server's certificate is not trusted.-202
2024-05-26 15:56:38.147 [info] unknown @ 0 - JS: fetchWithTimeout: timed out connecting to url: https://myserver.com/system/info/public 
2024-05-26 15:56:38.147 [info] unknown @ 0 - JS: ConnectionManager request failed to url: https://myserver.com/system/info/public
2024-05-26 15:56:38.147 [info] unknown @ 0 - JS: Reconnect failed to https://myserver.com
2024-05-26 15:56:38.147 [info] unknown @ 0 - JS: connectToAddress https://myserver.com failed
FranckRJ commented 1 month ago

Additionally, everything works on the web or the android application, the issue is only in Jellyfin Media Player.

psyleft commented 1 month ago

I can second this issue on the latest flatpak version. Was working fine beforehand but now trying to connect to a 10.9.2 server gives me the following: [2:68:0527/162010.792754:ERROR:ssl_client_socket_impl.cc(960)] handshake failed; returned -1, SSL error code 1, net_error -202

FranckRJ commented 1 month ago

I updated my server to 10.9.3 and it still doesn't work. I tried on an Ubuntu machine with the provided .deb and it works, so it's only an issue with the flatpak version.

flo-at commented 1 month ago

I used the Qt WebEngine debugger to take a look at it. For me it seems to be a problem with IPv6 and DNS. There's an ERR_NAME_NOT_RESOLVED in the console that shouldn't be there. Happens with the Flatpak and the AUR version for me.

Edit: I'm pretty sure this is a problem with Qt WebEngine, not JMP. I can use the debugger to navigate to https://google.com but not to https://ipv6.google.com with the same error being logged.

Edit2: This one seems related in my case: https://bugs.chromium.org/p/chromium/issues/detail?id=259940&no_tracker_redirect=1 This is not fixed for Qt 5 WebEngine (https://wiki.qt.io/QtWebEngine/ChromiumVersions)