Page 1 of 1

DLNA server not being seen over network

PostPosted: Mon Nov 16, 2020 12:29 pm
by tinybilbo
Hi,

I have Serviio Running via docker (with --network=host) and everything runs fine even when accessing from an external location via ServiGO.
However when i try to access the DLNA on my android phone or tablet, The clients find nothing...
The only thing that can find Serviio is VLC from my PC (via UPNP).

If I set up another DLNA server with docker (like Asset-Upnp), that server can be seen....

Is there a setting that I'm missing in Serviio to enable DLNA? and if not does anyone have an idea what might be the problem?

The docker image is running on Ubuntu server with firewall turned off.

Thanks

Re: DLNA server not being seen over network

PostPosted: Mon Nov 16, 2020 2:59 pm
by atc98092
I'm not familiar with running Serviio (or anything else) on a NAS. But no, there's no switch for the DLNA server. It can be toggled on/off from the Serviio console at the bottom of the Status page, so you can look there to see if it's running. But it's on by default and on a reboot. It sounds like some sort of networking configuration in the docker.

Re: DLNA server not being seen over network

PostPosted: Thu Nov 19, 2020 8:36 pm
by tinybilbo
atc98092 wrote:I'm not familiar with running Serviio (or anything else) on a NAS. But no, there's no switch for the DLNA server. It can be toggled on/off from the Serviio console at the bottom of the Status page, so you can look there to see if it's running. But it's on by default and on a reboot. It sounds like some sort of networking configuration in the docker.


Thanks for the reply.
Actually it's running on a headless server rather than a NAS, just in docker. As far as I can see there is much any difference between versions.
All other DLNA servers ran fine with docker, So I though it unlikely to be docker itself.
Knowing that it should work (from your reply) I just wiped the docker container and ran fresh one with exactly the same config.
To my surprise It could immediately be found by my Android devices. So I guess (you were right :-) ) some error had crept in somewhere to the actual container.
It's been bugging me for months! I just assumed that I had misconfigured something!