-
-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DLNA "Play to" not working with plugin (and 10.9.x) #48
Comments
Thanks, just tried 10.9.1 (went straight from 10.8 to 10.9.2) and can confirm it immediately works. What happened on 10.9.2 ? Might not be plugin related ? |
Hi, same issue here with the "Cast to device/Play on" option. |
Hi, I think this is related to the various modifications of NetworkManager in the core application in 10.9.2. If it fails when "bind address" field is empty in the network configuration tab, it actually works, even on 10.9.2 when I fill this field with local LAN IP of the server. When doing so, the DLNA sessions are created and the targets appear in "Play to" menu :
Configuration field is in Dashboard -> Advanced -> Networking -> Bind to local IP : 192.168.0.61/24 (in my case) |
Hello Arpel. Good job! for the DNLA plugin to work well. Everything is well now. Thank you. |
hi, just to add more information/confirmation: it did work in .91 version but broke in .92 for me as well. also, in my case, binding to a single address as proposed by @arpel did indeed seem to fix the DLNA problem: from what I saw in the logs, it could detect my DLNA Sony hifi, fyi, for now, I will just leave it as is and watch closely this issue. I can live without DLNA. |
I too use macvlan, and we could specify two ips, make sure that the first one is your macvlan (the one for the DLNA) In my case it looks like this (192.168.1.0/24 is my network for dlna(where each devices are)) |
hi, thx a bunch for the idea of putting more than 1 address there o_0, it works for me too! nb. for the ones using the |
After I put an address in " Link to local IP",I can link my tv.But the movie did not play.There is nothing displaying just a black screen. |
This should now be fixed in #51. |
FYI, 'just tested, and without manually setting the bind addresses,
I don't know the thing at all, but my guess it sends the commands with a "source IP" from the wrong network. nb: I notice that the 'NetworkManager' detects the expected address (192.168.1.245) last in its list.
thanks for your work, btw! |
hi, me again, sorry! but I also noticed the interfaces got registered in a different order:
question, then: am I correct to understand this is only a question of chance that this is working ? |
There was a DLNA plugin release that was supposed to fix IP binding issues, and a server release that was also supposed to fix IP binding issues. I'm leaning towards the issue is fixed and not just chance 🤞 |
Strange, I'm still on 10.9.2 and with the new version of the plugin I can both find and stream to my DLNA music player without problems. |
@ms-afk ok, FYI, re-retested today and even when reverting back to version .92 the issue does not reappear...
so my guts feeling (and a little bit the code change in the merge request) is telling me it is taking the first address in the list (after the 127) and use it as source or something, and so rely on some "chance" to fall on the right one. again: thank you all for your work! |
The code added in the pull requests only takes the first address if there is only one address present. On the other hand the "old" code, still executed in some occasions, also takes the first address, but this address has to match the right network interface. This means that the order of those addresses should not matter. It is however possible that something else has been broken after 10.9.2, that is dependent on the order of the addresses. |
@zorro0109 this seems to be a totally different issue (session related), please open a new issue for it. |
Updated to version relevant log
|
It's just two weeks ago, I got network receiver and had the above issues to, till I tead this post and updated the server. One question @ALL
A bit OT, but you seem to use the DLNA feature much much longer, so hope you don't mind |
Jellyfin.Server 10.9.11.0 The above mentioned fix to enter local ip in the "Bind to local network address" has worked well for me the past few weeks until yesterday. Now my devices are undiscoverable if there is any value in the "Bind to local network address" field. The devices become discoverable if the field is blank but the playback fails to initiate with the following logs message: |
I can confirm that this issue is still there on v10.9.11. I also noticed that there's a seemingly erroneous status when no DLNA plugins are active:
After restarting Jellyfin, only 3.0.0.0 is shown with status "Active". I also see this in the error log during start-up:
Accessing it requires a user/password combo. Does this 127.0.0.1 address with port 8096 look ok? |
I too have the issue that it's not possible to send to device. Docker in host mode running 10.9.11 and DLNA 3.0.0.0
|
I started looking into this a bit on this issue post as it seems this one is the most specific to the playto functionality. still nothing conclusive but I found that when i removed the published url setting, and set the bind ip to a specific ip i was able to use playto on my lgtv. I suspect something with how this Sessions call is being made is going to the published url value and should be a local ip that is being registered as the publisher for dlna. the dlna plugin seems to have a lot of different locations where these urls are built...
note that the multiple double quotes seems odd and are getting injected there somehow, not sure if those could be causing a problem and not sure where they are coming from. yeah, this has to be related to the publisheduri setting again. i just removed the bind ip and i have full functionality doing playto to my lg tv, from both the web ui and the android app and i was able to play an audio and video file directly to the tv. |
Can you show which settings work for you? I'm not quite sure what I have to configure ... |
Could any oft you take a look at my post, please? |
@spacemanspiff2007 I thought I was on to something but it was my published url setting, it seems you dont need that any longer even when using nginx. When I'm playing to a device it seems to work fine without the published url. What does your network.xml file look like? |
Ok well I meant the xml file from your config folder but I think i see the problem there. i dont think that box for binding wants a CIDR address, try removing the /24 from the binden box. after you do that you have to restart jellyfin completely so the plugin pulls in the new value, i dont think the plugin reloads by itself when you save that |
If it saves, it should work. I reworked the logic for that field back in 10.9 and setting the CIDR should work just as well as without or even with fill netmask. Issues with devices not getting discovered are likely within how the ssdp listener binds to specific IPs/Interfaces |
Cool, I was playing around with that logic a bit locally. it does seem to build two different lists of adapters which seemed odd, i reworked that a bit to pass the same IPs as the published url but i didnt see a difference either way. maybe ill make a patch to test with since i couldnt get that to reproduce. thats separate than this play to issue though. im not able to reproduce that when im not using the published url. |
I tried it initially without the @Shadowghost |
I have a feeling this one could be closed, my play to functionality has been working fine since i made the changes to the publisher uri and the ssdp discovery in v4. |
It's still not working for me.
I'd be happy to try something out and provide logs if that results in a working play-to functionality. |
@spacemanspiff2007 I's suggest opening a separate issue with details about your setup. make sure youre on v4 of the plugin with 10.10, but that stacktrace does not seem to indicate anything with the dlna plugin and points more to something with your network config. |
@disgustipated When I open the sendto menu from my PC and try to send to the TV I get this:
|
@disgustipated
|
Hi, I've just updated 10.8.x version to latest 10.9.2, installed additional plugin-dlna and I can't get "Play to" to list something... as it used to do on 10.8.
I'm able to browse and play from a device to the Jellyfin DLNA : should not be a network issue (and was working before...).
I am using the official docker container in host networking mode and basically changed nothing to the configuration.
There's nothing in the logs, could you help?
Thanks!
The text was updated successfully, but these errors were encountered: