I installed minidlna on a Linux Orange Pi PC 6.12.23-current-sunxi and also on an Orange Pi Zero, but it doesn't work; it doesn't appear in the client, on an LG Smart TV. On a Raspberry Pi, it does work; the configuration files are the same, and there are no network rules blocking any traffic... Any ideas what it could be?

10 hours ago, llak arta said:

Linux Orange Pi PC 6.12.23-current-sunxi and also on an Orange Pi Zero

None of those boards are officially supported, so we are not aware on their hw support status. Those are also 32bit architecture, while we only provide 64bit support for Rpi.

 

10 hours ago, llak arta said:

On a Raspberry Pi, it does work

Did you use Armbian for Rpi? And which particular build? And on which Rpi?

There are many unknown things - big difference. Hard to determine the reason from current informations.

You aren't really giving us much of anything to work with.  Please provide some logs.  Is the process even running?  Are the ports open (nmap -p 8200 $IP_of_YOUR_BANANA)?

 

I did a quick local test on my Banana Pi M2+ and the port for minidlna at least is open.

 

$ nmap -p 8200 banana.local
Starting Nmap 7.94SVN ( https://nmap.org ) at 2025-04-25 06:43 PST
Nmap scan report for banana.local (192.168.8.108)
Host is up (0.0044s latency).
rDNS record for 192.168.8.108: banana

PORT     STATE SERVICE
8200/tcp open  trivnet1

Nmap done: 1 IP address (1 host up) scanned in 0.27 seconds

$ service minidlna status
● minidlna.service - MiniDLNA lightweight DLNA/UPnP-AV server
     Loaded: loaded (/usr/lib/systemd/system/minidlna.service; enabled; preset: enabled)
     Active: active (running) since Fri 2025-04-25 06:35:43 PST; 14min ago
       Docs: man:minidlnad(1)
             man:minidlna.conf(5)
   Main PID: 19814 (minidlnad)
      Tasks: 2 (limit: 2032)
     Memory: 53.3M (peak: 84.0M)
        CPU: 717ms
     CGroup: /system.slice/minidlna.service
             └─19814 /usr/sbin/minidlnad -f /etc/minidlna.conf -P /run/minidlna/minidlna.pid -S -r

Apr 25 06:35:43 banana systemd[1]: Started minidlna.service - MiniDLNA lightweight DLNA/UPnP-AV server.
Apr 25 06:35:45 banana minidlnad[19814]: minidlna.c:1163: warn: Starting MiniDLNA version 1.3.3.
Apr 25 06:35:45 banana minidlnad[19814]: minidlna.c:392: warn: Creating new database at /var/cache/minidlna/files.db
Apr 25 06:35:45 banana minidlnad[19814]: minidlna.c:1211: warn: HTTP listening on port 8200
Apr 25 06:35:45 banana minidlnad[19826]: scanner.c:730: warn: Scanning /var/lib/minidlna
Apr 25 06:35:45 banana minidlnad[19826]: scanner.c:819: warn: Scanning /var/lib/minidlna finished (0 files)!
Apr 25 06:35:45 banana minidlnad[19826]: playlist.c:135: warn: Parsing playlists...
Apr 25 06:35:45 banana minidlnad[19826]: playlist.c:269: warn: Finished parsing playlists.
Apr 25 06:35:46 banana minidlnad[19814]: monitor_inotify.c:223: warn: WARNING: Inotify max_user_watches [8406] is low or close to>
Apr 25 06:40:30 banana minidlnad[19814]: upnphttp.c:1108: error: recv (state0): Connection reset by peer

 

It was a problem with broadcast packet loss from the client to the server, depending on the situation... Client and server on a switch or on the same Wi-Fi, OK In all other situations, broadcast packets are lost even if they are on the same network 192.168.1/24...