![]() |
Jellyfin foz Android TV - Unable to connect - Printable Version +- Jellyfin Forum (https://forum.jellyfin.org) +-- Forum: Support (https://forum.jellyfin.org/f-support) +--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting) +--- Thread: Jellyfin foz Android TV - Unable to connect (/t-jellyfin-foz-android-tv-unable-to-connect) |
Jellyfin foz Android TV - Unable to connect - shadow82 - 2025-02-17 Hi! My friend, who has user account for my Jellyfin server can't connect when using Chromecast client. The client is unable to connect despite correct url. ![]() Connection from Android phone client works well for him. Also screen cast from phone to TV works well, but not jellyfin-androidtv. From my perspective: regular Android, WebOS client, Web App on Win11 works fine - from LAN and from public Internet Client unable to connect on Chromecast: jellyfin-androidtv 0.18.4 Jellyfin server 10.10.5 (running on Docker on Linux) [url=https://preview.redd.it/chromecast-client-unable-to-connect-v0-8s5jbkd7zpje1.jpg?width=1132&format=pjpg&auto=webp&s=624e5762948d8892511738c918291ab4c1e843af][/url] RE: Jellyfin foz Android TV - Unable to connect - theguymadmax - 2025-02-17 Upgrade to 10.10.6 RE: Jellyfin foz Android TV - Unable to connect - shadow82 - 2025-02-17 Did it sudo docker compose down sudo docker compose pull sudo docker compose up -d After that my versions are: Server version: 10.10.6 Network version: 10.10.6 Compilation version: 10.10.6 But hte behaviour is the same.
It seems it tries to connect also via ports 8096 and 8920 which are not allowed on my FW. It works like this:
Below my docker-compose.yml file Code: Services: RE: Jellyfin foz Android TV - Unable to connect - TheDreadPirate - 2025-02-18 You should configure Jellyfin to directly use port 8082. Also, where does your reverse proxy reside? RE: Jellyfin foz Android TV - Unable to connect - shadow82 - 2025-02-19 ok. changed the port redirection in docker-compose.yml file to: - 8082:8082 and in jellyfin config. No change after this one. I have a drawing here: https://imgur.com/qbDZkZo It shows which client flows work fine and which doesn't FW listens only on port 443. The rest of types of clients (Android app, Win11 web browser, LG WebOS client) work fine using the same way Here is wireshark dump when connecting to tv.acme.com (and it doesn't work) https://imgur.com/bT2GZcE Here is wireshark dump when connecting to demo.jellyfin.org (it it does work) https://imgur.com/zhQns8g Here is wireshark dump when connecting from my Win11 laptop webbrowser to tv.acme.com (same Wi-Fi) https://imgur.com/hHQFOcV Here is wireshark dmp with the same laptop connecting to demo.jellyfin.org https://imgur.com/45BgbqE I think the only bad thing here are 50% of retransmissions when connecting from Chromecast 4K, but if: - I'm getting them only when using Chromecast 4K - There are not retransmissions when connecting from my laptop - Other clients works fine both via home LAN and Internet except Jellyfin for Android TV Then something must be wrong with that client or Chromecast 4K is poor network endpoint... RE: Jellyfin foz Android TV - Unable to connect - TheDreadPirate - 2025-02-20 I have two Chromecast 4Ks. Neither have this issue. So it is either a faulty WiFi antenna, just a faulty device in general, or the signal is weak where the device is located. RE: Jellyfin foz Android TV - Unable to connect - shadow82 - 2025-02-20 (8 hours ago)TheDreadPirate Wrote: I have two Chromecast 4Ks. Neither have this issue. So it is either a faulty WiFi antenna, just a faulty device in general, or the signal is weak where the device is located. Well - antenna is like 50cm from Chromecast. The same Chromecast plays videos from the same source via SMB and VLC player with no issues. Truth is the client is being checked by FW and if it connects anyhow wrong, FW will drop the connection. 3 other type of clients work well using the same connection |