search

flathub / com.github.iwalton3.jellyfin-media-player

https://flathub.org/apps/details/com.github.iwalton3.jellyfin-media-player
GNU General Public License v3.0
1 stars 5 forks source link

Jellyfin Media Player Flatpak is unable to access (non local?) Jellyfin servers #47

Open Constancies opened 3 months ago

Constancies commented 3 months ago

Whenever I attempt to access my server or Jellyfin's demo server, the Jellyfin Media Player client is unable to connect, with the error: We're unable to connect to the selected server right now. Please ensure it is running and try again. I'm not sure if it is able to access local servers either, as I haven't been able to test this just yet, but I do know that the Jellyfin Media Player .deb is perfectly capable of accessing non-local servers. Maybe this is a flatpak permission issue?

To reproduce, give this a shot with Jellyfin's demo instance, https://demo.jellyfin.org.

EDIT: For some reason this only seems to be an issue on my laptop running openSUSE Tumbleweed. I have another laptop running Linux Mint that doesn't have this bug. And yes, both are running the Flatpak. Extremely weird.

NAHFE commented 3 months ago

I seem to have the same problem on openSUSE Tumbleweed. When looking through the logs there is this message 2024-05-17 00:45:19.388 [debug] onCertificateError @ 221 - https://demo.jellyfin.org/system/info/public :Server's certificate is not trusted.-202

FranckRJ commented 2 months ago

Same issue on openSUSE Tumbleweed, I also opened an issue in the JMP repo: 667.

I have another laptop running Linux Mint that doesn't have this bug

Which version of flatpak do you have in linux mint ? On Tumbleweed I have Flatpak 1.15.8.

flo-at commented 2 months ago

Same issue on ArchLinux with Flatpak 1.15.8. I tried JMP 1.9.1 and 1.10.1. From the log:

  2024-05-31 23:23:06.010 [info] unknown @ 0 - JS: begin connectToServer
  2024-05-31 23:23:06.011 [info] unknown @ 0 - JS: tryReconnect: https://xxxxx
  2024-05-31 23:23:06.112 [info] unknown @ 0 - JS: getTryConnectPromise https://xxxxx
  2024-05-31 23:23:06.113 [info] unknown @ 0 - JS: ConnectionManager requesting url: https://xxxxx/system/info/public
  2024-05-31 23:23:06.114 [info] unknown @ 0 - JS: fetchWithTimeout: timeoutMs: 20000, url: https://xxxxx/system/info/public
  2024-05-31 23:23:06.126 [info] unknown @ 0 - JS: fetchWithTimeout: timed out connecting to url: https://xxxxx/system/info/public
  2024-05-31 23:23:06.126 [info] unknown @ 0 - JS: ConnectionManager request failed to url: https://xxxxx/system/info/public
  2024-05-31 23:23:06.127 [info] unknown @ 0 - JS: Reconnect failed to https://xxxxx
  2024-05-31 23:23:06.127 [info] unknown @ 0 - JS: connectToAddress https://xxxxx failed

The connection "timed out" immediately.

Edit: same problem when I compile the package (without Flatpak).

FranckRJ commented 2 months ago

I tried JMP 1.9.1 and 1.10.1.

It's strange because for me JMP 1.9.1 worked but not 1.10.1. And my error message is not the same, I don't have a timeout but a Server's certificate is not trusted (mentioned earlier). Maybe we don't have the same issue, I don't know.

flo-at commented 2 months ago

It's probably something else, you're right. My problem is more general and most likely not related to Jellyfin directly but to Chromium which is used in Qt WebEngine.