2024-09-26, 11:21 AM
(This post was last modified: 2024-09-26, 01:21 PM by raulx222. Edited 4 times in total.)
(2024-09-17, 02:11 PM)TheDreadPirate Wrote: There shouldn't be any additional configuration required for Caddy. Caddy handles all of that automatically.
I'm running a server for about a year, most users are using the Jellyfin Media Player (Windows), Findroid (Android), Infuse (iOS) and there are no problems. But with Jellyfin for Android TV for some users it doesn't connect, when they input the host address, the app says it can't connect. From 3 friends that want to connect from TV, only one friend can connect via Android TV app, but other 2 friends can't connect to the server, one with Android TV and one with Amazon Fire TV stick.
The error on Amazon Fire TV stick is the following (it's also the same error for the other friend with Android TV):
But the same address works fine on other clients or in browser. I can't replicate this error myself since I don't own an Android TV. I tried emulating Android TV, but the app connects to the server without any issues.
Here is my Caddy config:
Code:
jellyfin.mydomain.com {
reverse_proxy 192.168.3.85:8096
}
I did a SSL handshake simulation and looks good. Results:
I don't know how to debug this. What's the reverse proxy setup for the demo.jellyfin.org site? That one works on all TVs, it is possible to achieve the same setup with Caddy? Or the Android TV APK has some certificates baked in to allow the demo site to work properly?
Any help is appreciated. Thanks!