mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-07-16 05:43:54 +03:00
Cannot cast at all (DLNA/Chromecast) #120
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @TheManchineel on GitHub (Dec 18, 2018).
Originally assigned to: @anthonylavado on GitHub.
Both my Chromecast (Android TV) and DLNA (Kodi) hosts are not working as casting destinations.
When I try to cast music or movies to DLNA, it shows me the last played song in the playback menu and the moving progress bar, but no casting occours.
When I try to cast to Chromecast, nothing happens.
I can "cast" to an open web browser window on the web interface or an open mobile web app, but that's it.
OS: Ubuntu Server 18.04 LTS
Build: I downloaded the .deb from the repo and replaced the libcurl3 dependency with libcurl4 as they can't coexist.
@anthonylavado commented on GitHub (Dec 18, 2018):
Possibly related to #144, but keeping both as you also mention DLNA
@TheManchineel commented on GitHub (Dec 18, 2018):
Does this work for anyone (i.e. is this a known bug) or is this exclusive to my installation?
@trumblejoe commented on GitHub (Dec 19, 2018):
I (believe) I've been able to cast successfully from the web interface to my tv. After attempting cast it reported "file not supported", reasonable given the limited file support this tv has. It certainly switched displays. I can spend some time testing casting to a roku tv this weekend.
@skug67 commented on GitHub (Dec 20, 2018):
I'm having troubles w/DLNA across the board. Can see files but not play on VLC (iOS), Infuse (iOS), SlickUPnP (Android -- whether I try to play to VLC or the stock Android video player). Also, if I use djmount to mount access the DLNA structure as a linux filesystem, I can again see the files but Mediainfo produces no information. The backend errors are all of the form:
HTTP Response 400 to [client ip]. Time: 13ms. http://[jellyfin server ip]:8096/videos/f7bbef2b94da79c009c946394f254719/stream.mk
v?DeviceId=test&MediaSourceId=f7bbef2b94da79c009c946394f254719&Static=true&AudioStreamIndex=1&Tag=db1fa9a190cfc3633e6606962cfb817f&dlnaheaders=true
@TheManchineel commented on GitHub (Dec 20, 2018):
Can confirm, active DLNA streaming not working via Yatse client on Android, untested on Kodi
@joshuaboniface commented on GitHub (Dec 21, 2018):
#238 appears to fix this.
@skug67 commented on GitHub (Dec 23, 2018):
Not fixed for me in 3.5.2-4 (debian buster).
@TheManchineel commented on GitHub (Dec 23, 2018):
Yeah, not fixed (actually it stopped seeing the Chromecast host). I moved to Docker and now it won't even see any DLNA host or be seen as a DLNA server. This is not a firewall issue as I didn't have any of these issues on Emby Emby. I'm not switching back to Emby's Emby either though.
@anthonylavado commented on GitHub (Dec 24, 2018):
Hi all, we'd like to gather some more information surrounding this. I know @joshuaboniface and I can work on the Chromecast part, but I'm unsure how to try testing the DLNA part.
Chromecast for me does work when I start it from the mobile app.
Can we consolidate all the information you each have about how you've tested it, and what your results are?
@skug67 commented on GitHub (Dec 24, 2018):
Uploading logs from trying to use VLC over DLNA
(note: I normally have the system set up to use nfs shares when streaming over LAN -- just in case that was contributing to the problems, I tried both w/ and w/o that setup. Separate logs are attached).
jellyfin-dlna-debug.txt
jellyfin-dlna-no-nfs-debug.txt
@LeoVerto commented on GitHub (Jan 3, 2019):
Are you running your container in host networking mode (i.e. by running it with
--net=host)? This seems to be required for DLNA to work.Also can someone check whether #378 fixes this issue?
@TheManchineel commented on GitHub (Jan 7, 2019):
I properly set up the Docker container with host networking, so that DLNA can detect devices on the network. Apparently the issue only happens with Kodi on my Raspberry Pis, since it seems functional with my Sony Bravia Android TV and UWP Kodi for Windows; Chromecast devices aren't detected at all on the other hand.
I captured some relevant log lines with
tail -f, hope it doesn't contain any private info about my system as I didn't modify it :DAfter clicking on the Play On tab I get the following in the log:
No log is produced upon selecting the host, which in my case is a Kodi (OSMC) Raspberry Pi called "Soggiorno" ("living room" in Italian), but this is what happens when I try to play e.g. a song:
Additional info:
My server has an IPv4 of
192.168.1.2and a hostnamearkMy web client has an IPv4 of
192.168.1.4and a hostnameZireaelThe DLNA Host has an IPv4 of
192.168.1.10and a hostnameSoggiornoThe NAT router is at
192.168.1.1@TheManchineel commented on GitHub (Jan 7, 2019):
Sorry everyone, I'm an idiot. I just realized this is due to a known Kodi/OSMC media database glitch that is easily resolved on the Kodi side by deleting the db and letting the mediacenter rebuild it. It was completely unrelated to Jellyfin. I am still unable to use Chromecast but I guess that is another matter and should be addressed separately.