Replies: 6 comments 9 replies
-
I'm on macOS Apple Silicon and this version seems to not read my previous settings so it was asking for the server details. I initially downgraded back to v1.10.1 (which loaded up immediately) because I couldn't get 1.11 to connect to my server at all, but specifying the 8096 port finally got it working. Server version 10.9.2. |
Beta Was this translation helpful? Give feedback.
-
No longer connects to my server after the Client upgrade, using reverse proxy subpath/subfolder can't even provide any logs as it seems like it doesn't even reach the server at all, as no logs are produced on the server on the connection attempt |
Beta Was this translation helpful? Give feedback.
-
Same issue. Cannot connect to my server through either specifying the 8096 port or through the port 80 proxy I have setup. Specifying the port hasn't worked for awhile but now I can't even get around that. |
Beta Was this translation helpful? Give feedback.
-
Sorry if this is a dumb question but does this mean the client's interface will always actually be running on the server? Or if the client has an up to date jellyfin-web it will run its own? Will this increase the load on the server (even if little)? Thanks for the amazing work you're all doing btw |
Beta Was this translation helpful? Give feedback.
-
So using Jellyfin Media Player without running jellyfin-web on the server is not possible anymore? Or do I understand something wrong? |
Beta Was this translation helpful? Give feedback.
-
On Silicon mac, this update broke the rendering of ASS subtitle. Not sure if i am doing something wrongly. |
Beta Was this translation helpful? Give feedback.
-
This release switches Jellyfin Media Player to always use the external web client so that updates to
jellyfin-web
take effect immediately instead of when I get a chance to release the application.About Windows Downloads:
This discussion was created from the release v1.11.0 - External Web Client.
Beta Was this translation helpful? Give feedback.
All reactions