DLNA issue
GoSpursGoNL opened this issue · 12 comments
Hi Franck, hope you can help! I migrated from HA (Core) Raspbian+Docker to HA (previously called hass.io) including your Plex addon.
Plex itself is working perfectly (via browser, mobile apps, Chromecast), except for the DLNA server not being discovered. DLNA is enabled in the Plex configuration.
I don't have other addons using the port 1900. The documentation mentions a possible port conflict (bind: address already in use) but this does NOT occur. I also followed the instructions regarding 'solving connection issues in Plex'.
In the past (Plex on Docker) DLNA worked fine. In that case it was running as networking_mode: host by the way.
But with your addon my DLNA clients can't find any server. What can I do to discover the cause?
👋 Thanks for opening your first issue here! If you're reporting a 🐛 bug, please make sure you include steps to reproduce it. Also, logs, error messages and information about your hardware might be useful.
It indeed can cause issues, right now, I don't have a proper method on improving on this.
Dropping the add-on to the host network, might be an option, but in general, I would avoid doing that as much as possible.
Thanks. Is there a way for me to change the networking mode (temporarily) to see if it solves the issue?
With the old setup I also really needed to change the networking mode to host, it wasn't sufficient to map/forward the individual ports.
/edit: I tried it via your Portainer addon. I can make the Plex container leave the hassio network, but can't connect it to the host network. I see that some of your other addons (thanks for those as well!) are connected to host (Nodered and SSH)
What I now did is via Portainer clone the Plex container created by your addion, and then I was able to change the networking mode to host. I stopped your addon and started up the new container, and immediately my DLNA players can see the Plex DLNA server!! :)
Would you consider changing the networking_mode to host for your addon frenck?
Yes, I would, right now I'm handling the rebranding change from Home Assistant with the community add-ons, which is kind of a big task.
This means I'm actually changing and updating each add-on I have.
I do pick up some simple things along the way, but changing the networking of an add-on, is something I'd like to spend a little time on before putting it out.
TL;DR, not right now, maybe later.
I understand, thanks in advance!
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
I also ran into this problem, dlna is not detected on TV
Same here
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This is still very much desired.
Hi frenck, changing the addon to use host networking currently is still needed to get DLNA to work properly. I hope you have time to consider making this the default.