I see jf.local in your screenshot, so I suppose there is no other firewall involved, and there is no router/NAT/VPN to deal with.
Can you connect to this port on the command line from your server itself? At first at localhost / 127.0.0.1, secondly at its external interface? Any difference using a domain name or an IP?
Sanity check: the service is running and no errors in diagnosis?
Can you connect to this port on the command line from your server itself? At first at localhost / 127.0.0.1,
admin@yuno:~ $ curl localhost:8095
admin@yuno:~ $ curl localhost:8096
curl: (7) Failed to connect to localhost port 8096 after 0 ms: Couldn't connect to server
Any difference using a domain name or an IP?
Currently I only access it from internally it’s not connected.
I meant 127.0.0.1 instead of localhost (and if localhost gave any reaction, connecting to ‘yuno’ and its IP).
It takes quite a strict firewall to have no answer via localhost. Any “proof” Jellyfin is actually running? Is it an option to reconfigure it, to try another port?
Oh, that may be obvious to you, but this is new information for readers of this forum. Implications:
there is no reason to waste time troubleshooting closed ports
there is no reason to waste time troubleshooting the Jellyfin installation
there is no reason to question the firewall settings (or other settings) on Yunohost
The Jellyfin docs seem to imply that when using nginx as a reverse proxy (as we do on Yunohost), it uses websockets for the endpoints.
It seems websocket support for curl is either new, or optional. Therefor, curl may be sub-optimal to troubleshoot this issue.
Seeing the proportions of the screenshot, it seems a screenshot from an app on Android. Is that on the same phone as the phone that has trouble connecting to Jellyfin?
Do you have access to another Android device for testing? Or, do you have access to another Jellyfin server to test with your current device?
There seems to be a number of apps available that can do something with Jellyfin. I don’t expect switching apps makes a difference at this point, but you never know.
What does that show when running it against localhost and 127.0.0.1?
I’m not familiar with Jellyfin. Does the interface presented in the browser implement a Javascript player that connects in the same way, and to the same service, as an Android app would do?
If so, I’d imagine that the web-player connects to localhost. Is there any configuration to edit before Jellyfin starts offering a connection at non-local netwerk interfaces?