TiraelSedai 0 Posted September 27, 2019 Posted September 27, 2019 Hi. I am using Chromecast and when I'm pressing "broadcast to [my chromecast]" it launches Emby on Chromecast, and gets stuck in splash screen with Emby icon: Ready to cast. With that you can only disconnect, the actual playback never starts. What logs can I collect to help you debug this? Tried several phones (android app), haven't tried other clients.
Luke 42083 Posted September 28, 2019 Posted September 28, 2019 Hi there, can you please attach the emby server log from when this happened? thanks.
TiraelSedai 0 Posted September 30, 2019 Author Posted September 30, 2019 (edited) Alright, sorry for the late responce. User is "Mama" and the attempt starts at around 16:00 time (at least I think so, at least it was UTC+3 16:00 time, if you are logging in UTC always than its 13?) embyserver-63705312000.txt Edited September 30, 2019 by TiraelSedai
Luke 42083 Posted October 4, 2019 Posted October 4, 2019 Is the user connecting from the android app, or the web app? Are they inside the same local network as the server, or remote?
TiraelSedai 0 Posted October 6, 2019 Author Posted October 6, 2019 I've answered first question in the start post, it's remote. I'll try web app later today maybe.
Luke 42083 Posted October 21, 2019 Posted October 21, 2019 @@TiraelSedai how did this go? can you try accessing the server by ip address instead of host name?
TiraelSedai 0 Posted October 21, 2019 Author Posted October 21, 2019 I advised the people to ditch Emby in favor of competitors and both of them are working fine from the Android apps with Chromecast. No, accessing server by IP is not an option because Dynamic IP HTTPS
TiraelSedai 0 Posted October 21, 2019 Author Posted October 21, 2019 (edited) I use [letsencrypt + ngnix in Docker] that's routing traffic to Emby for Windows. Works flawlessly for any other Emby client I've tried (WebOS, Android, web)Here is ngnix config just in case:server { listen 443 ssl; listen [::]:443 ssl; server_name emby.*; include /config/nginx/ssl.conf; client_max_body_size 0; location / { include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; proxy_pass http://host.docker.internal:8096; proxy_set_header Range $http_range; proxy_set_header If-Range $http_if_range; } location ~ (/emby)?/socket { include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; proxy_pass http://host.docker.internal:8096; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection $http_connection; }} Edited October 21, 2019 by TiraelSedai
Luke 42083 Posted October 26, 2019 Posted October 26, 2019 Can you try the online web app and see how that compares? https://app.emby.media Note - the connection to your server may fail if the browser rejects the certificate. Thanks.
TiraelSedai 0 Posted October 26, 2019 Author Posted October 26, 2019 I can't atm, l'll try to remember to do it next time I visit my folks, but to be fair not likely
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now