You are not logged in.

Pages: 1 2

#1 2026-07-03 09:02:01

Al4st0r
Member
Registered: 2026-07-03
Posts: 14

Cannot get DLNA to work on my server

Hello everyone,

I run a homelab server with Arch Linux, and I wanted to expose a DLNA server using minidlna, but it's not working. The weird thing is that with the exact same steps I can get it working on my main computer.

I have deactivated pihole and other such services that could interfere with dlna, but still nothing.

When running `sudo ss -ulnp | grep :1900` i get

UNCONN 0     0     239.255.255.250:1900      0.0.0.0:*     users:(("minidlnad",pid=201125,fd=5))

On the other hand, when running `sudo systemctl status minidlna` i do get a problematic output, but I don't know what's wrong...

minidlna.service - minidlna server
     Loaded: loaded (/usr/lib/systemd/system/minidlna.service; enabled; preset: disabled)
     Active: active (running) since Fri 2026-07-03 10:54:59 CEST; 3min 11s ago
 Invocation: c6cc403dcb654f998eaf308b89011ee2
   Main PID: 201125 (minidlnad)
      Tasks: 2 (limit: 18876)
     Memory: 13.5M (peak: 14.5M)
        CPU: 135ms
     CGroup: /system.slice/minidlna.service
             └─201125 /usr/bin/minidlnad -S

Jul 03 10:54:59 myuser systemd[1]: Starting minidlna server...
Jul 03 10:54:59 myuser systemd[1]: Started minidlna server.
Jul 03 10:54:59 myuser minidlnad[201125]: minidlna.c:1134: warn: Starting MiniDLNA version 1.3.3.
Jul 03 10:54:59 myuser minidlnad[201125]: minidlna.c:1182: warn: HTTP listening on port 8200
Jul 03 10:55:00 myuser minidlnad[201125]: upnphttp.c:1281: error: send(res_buf): Connection reset by peer
Jul 03 10:55:00 myuser minidlnad[201125]: upnphttp.c:1281: error: send(res_buf): Connection reset by peer
Jul 03 10:55:00 myuser minidlnad[201125]: upnphttp.c:1281: error: send(res_buf): Connection reset by peer

What have I done wrong? What should I do?

Thanks in advance!

Last edited by Al4st0r (2026-07-03 09:03:00)

Offline

#2 2026-07-03 13:32:11

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 77,006

Re: Cannot get DLNA to work on my server

Jul 03 10:55:00 myuser minidlnad[201125]: upnphttp.c:1281: error: send(res_buf): Connection reset by peer

General network issue/instablity? minidlnad starting before the network is up? (though the PID is pretty high)
=> check the system journal for that.

Otherwise stop the service and run "minidlna -d" in debug mode.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#3 2026-07-03 14:49:05

Al4st0r
Member
Registered: 2026-07-03
Posts: 14

Re: Cannot get DLNA to work on my server

Thank you for your answer!

MiniDLNA's service file requires network to be working before attempting to start. Network should be working fine as I am generally connected to the server via ssh.

In the system journal, `journalctl -xeu minidlna` i see the following:

Jul 03 13:12:24 myuser minidlnad[446]: minidlna.c:1134: warn: Starting MiniDLNA version 1.3.3.
Jul 03 13:12:24 myuser minidlnad[446]: minidlna.c:1182: warn: HTTP listening on port 8200
Jul 03 13:12:30 myuser minidlnad[446]: minissdp.c:816: error: sendto(udp_shutdown=9): Network is unreachable
Jul 03 13:12:30 myuser minidlnad[446]: minissdp.c:816: error: sendto(udp_shutdown=9): Network is unreachable
Jul 03 13:12:30 myuser minidlnad[446]: minissdp.c:324: error: sendto(udp_notify=9, 172.20.0.1): Network is unreachable
Jul 03 13:12:30 myuser minidlnad[446]: minissdp.c:324: error: sendto(udp_notify=9, 172.20.0.1): Network is unreachable
Jul 03 13:12:30 myuser minidlnad[446]: minissdp.c:324: error: sendto(udp_notify=9, 172.20.0.1): Network is unreachable
Jul 03 13:12:30 myuser minidlnad[446]: minissdp.c:324: error: sendto(udp_notify=9, 172.20.0.1): Network is unreachable
Jul 03 13:12:30 myuser minidlnad[446]: minissdp.c:324: error: sendto(udp_notify=9, 172.20.0.1): Network is unreachable
Jul 03 13:12:30 myuser minidlnad[446]: minissdp.c:324: error: sendto(udp_notify=9, 172.20.0.1): Network is unreachable
Jul 03 16:34:00 myuser minidlnad[446]: minidlna.c:199: warn: received signal 15, good-bye
Jul 03 16:34:00 myuser systemd[1]: Stopping minidlna server...
░░ Subject: A stop job for unit minidlna.service has begun execution
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A stop job for unit minidlna.service has begun execution.
░░ 
░░ The job identifier is 231667.
Jul 03 16:34:00 myuser systemd[1]: minidlna.service: Deactivated successfully.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ The unit minidlna.service has successfully entered the 'dead' state.
Jul 03 16:34:00 myuser systemd[1]: Stopped minidlna server.
░░ Subject: A stop job for unit minidlna.service has finished
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A stop job for unit minidlna.service has finished.
░░ 
░░ The job identifier is 231667 and the job result is done.

Using `minidlnad -d` to try to run in debug mode results in the error: `[2026/07/03 16:43:36] minidlna.c:781: fatal: Bad user 'minidlna'.`. I have found a thread in the Manjaro forum with this error but it just goes back to the arch wiki lol. After following those instructions, i got `minidlnad` working, but it still isn't being discovered by my other devices.

What else should I check?

Offline

#4 2026-07-03 14:53:01

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 77,006

Re: Cannot get DLNA to work on my server

Jul 03 13:12:30 myuser minidlnad[446]: minissdp.c:324: error: sendto(udp_notify=9, 172.20.0.1): Network is unreachable
ip a; ip r

docker?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#5 2026-07-03 15:04:30

Al4st0r
Member
Registered: 2026-07-03
Posts: 14

Re: Cannot get DLNA to work on my server

Well, I first wanted dlna as a jellyfin plugin to work (with jellyfin inside docker), seeing as how that didn't work, i installed minidlna as a docker container, which didn't work either, and now i'm just trying to get minidlna to work, without docker... I've started the thread when I was already on the dockerless dlna, but maybe the journal is prior to that...

Output of `ip a; ip r` is something like (real ip hidden and such):

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute 
       valid_lft forever preferred_lft forever
2: eno1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether d4:be:d9:2b:eb:9d brd ff:ff:ff:ff:ff:ff
    altname enp0s25
    altname enxd4bed92beb9d
3: wlp3s0b1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 08:ed:b9:2e:a0:dd brd ff:ff:ff:ff:ff:ff
    altname wlx08edb92ea0dd
    inet 192.168.0.3/32 scope global noprefixroute wlp3s0b1
       valid_lft forever preferred_lft forever
    inet6 fe80::6ea1:e0dc:7344:2b3b/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
4: br-5f6b1c4180bc: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default 
    link/ether f2:fe:89:a9:38:e8 brd ff:ff:ff:ff:ff:ff
    inet 172.20.0.1/16 brd 172.20.255.255 scope global br-5f6b1c4180bc
       valid_lft forever preferred_lft forever
    inet6 fe80::f0fe:89ff:fea9:38e8/64 scope link proto kernel_ll 
       valid_lft forever preferred_lft forever
5: br-70a078418075: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default 
    link/ether 36:bc:37:c4:2e:6d brd ff:ff:ff:ff:ff:ff
    inet 172.19.0.1/16 brd 172.19.255.255 scope global br-70a078418075
       valid_lft forever preferred_lft forever
    inet6 fe80::34bc:37ff:fec4:2e6d/64 scope link proto kernel_ll 
       valid_lft forever preferred_lft forever
6: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default 
    link/ether 0e:fd:4a:a2:2e:eb brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
       valid_lft forever preferred_lft forever
7: br-35adc897fa09: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default 
    link/ether 02:9e:10:e3:f0:c5 brd ff:ff:ff:ff:ff:ff
    inet 172.18.0.1/16 brd 172.18.255.255 scope global br-35adc897fa09
       valid_lft forever preferred_lft forever
    inet6 fe80::9e:10ff:fee3:f0c5/64 scope link proto kernel_ll 
       valid_lft forever preferred_lft forever
8: veth1d104c1@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-35adc897fa09 state UP group default 
    link/ether 76:c6:c6:7e:cd:a8 brd ff:ff:ff:ff:ff:ff link-netnsid 0
    inet6 fe80::74c6:c6ff:fe7e:cda8/64 scope link proto kernel_ll 
       valid_lft forever preferred_lft forever
...
20: vethbf4a94b@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-35adc897fa09 state UP group default 
    link/ether 82:7e:70:ea:44:e8 brd ff:ff:ff:ff:ff:ff link-netnsid 10
    inet6 fe80::807e:70ff:feea:44e8/64 scope link proto kernel_ll 
       valid_lft forever preferred_lft forever
default via 192.168.0.1 dev wlp3s0b1 proto static metric 600 
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
172.18.0.0/16 dev br-35adc897fa09 proto kernel scope link src 172.18.0.1 
172.19.0.0/16 dev br-70a078418075 proto kernel scope link src 172.19.0.1 
172.20.0.0/16 dev br-5f6b1c4180bc proto kernel scope link src 172.20.0.1 
192.168.0.1 dev wlp3s0b1 proto static scope link metric 600

Last edited by Al4st0r (2026-07-03 15:04:56)

Offline

#6 2026-07-03 15:10:45

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 77,006

Re: Cannot get DLNA to work on my server

Are you using docker for anything else or are all those virtual devices and bridges stale?
You can limit minidlna to specific interfaces (eno1, wlp3s0b1) - https://man.archlinux.org/man/extra/min … _interface but otherwise want to clean up the network setup (docker0 has no carrier)

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#7 2026-07-03 15:47:30

Al4st0r
Member
Registered: 2026-07-03
Posts: 14

Re: Cannot get DLNA to work on my server

Yes, I'm hosting various services on this server, all of them as docker containers, divided into three docker networks which correspond to the three bridges shown...

What do you mean with your second sentence? Do you mean i should limit minidlna to wlp3s0b1 to make sure that the dlna gets exposed to the wifi network instead of the other docker containers?

Ok, doing so kinda works... I've edited `/etc/minidlna.conf` and at least it removes part of the errors, now if i run `sudo systemctl status minidlna` i get:

● minidlna.service - minidlna server
     Loaded: loaded (/usr/lib/systemd/system/minidlna.service; enabled; preset: disabled)
     Active: active (running) since Fri 2026-07-03 17:44:36 CEST; 7s ago
 Invocation: 76d1986a9a7c4c44a0e17395121bb7ee
   Main PID: 40132 (minidlnad)
      Tasks: 2 (limit: 18876)
     Memory: 9.2M (peak: 11.1M)
        CPU: 116ms
     CGroup: /system.slice/minidlna.service
             └─40132 /usr/bin/minidlnad -S

Jul 03 17:44:36 myuser systemd[1]: Starting minidlna server...
Jul 03 17:44:36 myuser systemd[1]: Started minidlna server.
Jul 03 17:44:36 myuser minidlnad[40132]: minidlna.c:1134: warn: Starting MiniDLNA version 1.3.3.
Jul 03 17:44:36 myuser minidlnad[40132]: minidlna.c:396: warn: New media_dir detected; rebuilding...
Jul 03 17:44:36 myuser minidlnad[40132]: minidlna.c:1182: warn: HTTP listening on port 8200
Jul 03 17:44:36 myuser minidlnad[40148]: scanner.c:731: warn: Scanning /opt
Jul 03 17:44:36 myuser minidlnad[40148]: scanner.c:820: warn: Scanning /opt finished (1 files)!
Jul 03 17:44:36 myuser minidlnad[40148]: playlist.c:135: warn: Parsing playlists...
Jul 03 17:44:36 myuser minidlnad[40148]: playlist.c:269: warn: Finished parsing playlists.

Which would look correct except it says "warn" on each line? And it's still not showing up on other devices.

EDIT: my /etc/minidlna.conf looks like this now (i've remove the default comments that are in the file before posting it here):

port=8200
network_interface=wlp3s0b1
user=minidlna
media_dir=/opt
friendly_name=My DLNA Server

Last edited by Al4st0r (2026-07-03 15:49:42)

Offline

#8 2026-07-03 15:51:23

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 77,006

Re: Cannot get DLNA to work on my server

I'd not pay too much attention to the "warn" thing, does it work on the localhost (ie. can you access the dlna data from eg. a local vlc instance)?
Compare "ss -tulpen" on this and nmap from a host that's supposed to be a DLNA client, you earlier greeped for 1900/udp, make sure 8200/tcp is allowed, too.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#9 2026-07-03 15:57:55

Al4st0r
Member
Registered: 2026-07-03
Posts: 14

Re: Cannot get DLNA to work on my server

The server doesn't actually have a desktop environment and i'd rather not add one for this... Here are the other two commands you mentioned...

When running `sudo ss -tulpen | grep minidlna`

udp   UNCONN 0      0         192.168.0.3:41944      0.0.0.0:*    users:(("minidlnad",pid=40132,fd=7)) uid:61737 ino:186504 sk:1001 cgroup:/system.slice/minidlna.service <->  
udp   UNCONN 0      0      239.255.255.250:1900       0.0.0.0:*    users:(("minidlnad",pid=40132,fd=5)) uid:61737 ino:186500 sk:1002 cgroup:/system.slice/minidlna.service <->  
tcp   LISTEN 0      16             0.0.0.0:8200       0.0.0.0:*    users:(("minidlnad",pid=40132,fd=6)) uid:61737 ino:186501 sk:2003 cgroup:/system.slice/minidlna.service <->

When running `sudo nmap -sU -sT -p U:1900,T:8200 192.168.0.3` i get:

Starting Nmap 7.99 ( https://nmap.org ) at 2026-07-03 17:55 +0200
Nmap scan report for al4st0rserver (192.168.0.3)
Host is up (0.000057s latency).

PORT     STATE  SERVICE
8200/tcp open   trivnet1
1900/udp closed upnp

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

I find it weird in the second one that the 1900/udp port is labeled as closed? Is this the issue i have?

Last edited by Al4st0r (2026-07-03 15:58:12)

Offline

#10 2026-07-03 16:10:00

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 77,006

Re: Cannot get DLNA to work on my server

No, UPNP is closed outwards, that's fine.
What do you get on http://192.168.0.3:8200 ?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#11 2026-07-03 16:11:53

Al4st0r
Member
Registered: 2026-07-03
Posts: 14

Re: Cannot get DLNA to work on my server

In a browser? Nothing. Sort of generic notfound error with title "Problem loading page" in firefox.

Offline

#12 2026-07-03 19:33:27

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 77,006

Re: Cannot get DLNA to work on my server

That would explain why you can't see anything but not why the webserver (ie. dlna) doesn't work respond - the port is obviously open (and I assume minidlna was still running at the time?)

curl -vL http://192.168.0.3:8200 > /tmp/wtf.txt 2>&1
cat /tmp/wtf.txt | curl -s -H "Accept: application/json, */*" --upload-file - 'https://paste.c-net.org/'

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#13 2026-07-04 06:47:24

Al4st0r
Member
Registered: 2026-07-03
Posts: 14

Re: Cannot get DLNA to work on my server

Good morning Seth. After the first command the content of `/tmp/wtf.txt` is:

*   Trying 192.168.0.3:8200...
* Established connection to 192.168.0.3 (192.168.0.3 port 8200) from 192.168.0.3 port 32882
  % Total    % Received % Xferd  Average Speed  Time    Time    Time   Current
                                 Dload  Upload  Total   Spent   Left   Speed
  0      0   0      0   0      0      0      0                              0* using HTTP/1.x
> GET / HTTP/1.1
> Host: 192.168.0.3:8200
> User-Agent: curl/8.21.0
> Accept: */*
>
* Request completely sent off
< HTTP/1.1 200 OK
< Content-Type: text/html
< Connection: close
< Content-Length: 940
< Server: 6.15.7-arch1-1 DLNADOC/1.50 UPnP/1.0 MiniDLNA/1.3.3
< Date: Sat, 04 Jul 2026 06:43:55 GMT
< EXT:
<
{ [940 bytes data]
100    940 100    940   0      0 157.2k      0          100    940 100    940   0      0 154.8k      0          100    940 100    940   0      0 152.5k      0                              0
* shutting down connection #0
<HTML><HEAD><TITLE>MiniDLNA 1.3.3</TITLE><meta http-equiv="refresh" content="20"></HEAD><BODY><div style="text-align: center"><h2>MiniDLNA status</h2></div><h3>Media library</h3><table border=1 cellpadding=10><tr><td>Audio files</td><td>1</td></tr><tr><td>Video files</td><td>0</td></tr><tr><td>Image files</td><td>0</td></tr></table><h3>Connected clients</h3><table border=1 cellpadding=10><tr><td>ID</td><td>Type</td><td>IP Address</td><td>HW Address</td><td>Connections</td></tr><tr><td>0</td><td>Generic DLNA 1.5</td><td>192.168.0.232</td><td>A8:6B:AD:D2:52:AF</td><td>0</td></tr><tr><td>1</td><td>Samsung Series [CDEFJ]</td><td>192.168.0.245</td><td>78:AB:BB:C6:C1:9B</td><td>0</td></tr><tr><td>2</td><td>Unknown</td><td>192.168.0.139</td><td>A4:F9:33:EC:A0:C7</td><td>0</td></tr><tr><td>3</td><td>Unknown</td><td>192.168.0.3</td><td>FF:FF:FF:FF:FF:FF</td><td>0</td></tr></table><br>0 connections currently open<br></BODY></HTML>

This output looks promising to me, and there are several ip addresses listed, maybe the list of devices that can connect via dlna? But this means that the problem lies elsewere...

But the second command does return the following (EDIT: it only uploads the previous output to pastebin, right?):

{"link":"PackerDriving","url":"https://paste.c-net.org/PackerDriving","delete_key":"XLlPIPT0X3HEuLsQ"}

Last edited by Al4st0r (2026-07-04 06:50:44)

Offline

#14 2026-07-04 10:46:35

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 77,006

Re: Cannot get DLNA to work on my server

it only uploads the previous output to pastebin, right?

Right.
The DLNA server works and you can reach it from that host (check again w/ FF and post the exact error it issues), but no client is connected to it (the browser connection doesn't count) and also the media library is only one audio file?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#15 2026-07-05 10:59:30

Al4st0r
Member
Registered: 2026-07-03
Posts: 14

Re: Cannot get DLNA to work on my server

Yes, there is only one audio file now (I'm not using my actual library yet).

After a bit more testing, I realized that the output shown above was run in the server itself... when curling for 192.168.0.3:8200 from my main laptop (with the exact same curl command) I get:

*   Trying 192.168.0.3:8200...
* Established connection to 192.168.0.3 (192.168.0.3 port 8200) from 192.168.0.139 port 37576 
  % Total    % Received % Xferd  Average Speed  Time    Time    Time   Current
                                 Dload  Upload  Total   Spent   Left   Speed
  0      0   0      0   0      0      0      0                              0* using HTTP/1.x
> GET / HTTP/1.1
> Host: 192.168.0.3:8200
> User-Agent: curl/8.21.0
> Accept: */*
> 
* Request completely sent off
* Recv failure: Connection reset by peer

* closing connection #0
curl: (56) Recv failure: Connection reset by peer

Offline

#16 2026-07-05 13:53:32

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 77,006

Re: Cannot get DLNA to work on my server

And is the nmap result from that host closed or filtered?

This is some netfilter (firewall)
Please post the output of

find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#17 2026-07-05 18:35:06

Al4st0r
Member
Registered: 2026-07-03
Posts: 14

Re: Cannot get DLNA to work on my server

I'm not sure... as far as i know there is no firewall on that computer. The output you requested is:

autovt@.service                          | system
cloudflared.service                      | multi-user.target.wants
dbus-org.freedesktop.nm-dispatcher.service | system
dbus-org.freedesktop.timesync1.service   | system
docker.service                           | multi-user.target.wants
getty@tty1.service                       | getty.target.wants
minidlna.service                         | multi-user.target.wants
NetworkManager-wait-online.service       | network-online.target.wants
NetworkManager.service                   | multi-user.target.wants
p11-kit-server.socket                    | sockets.target.wants
remote-fs.target                         | multi-user.target.wants
sshd.service                             | multi-user.target.wants
systemd-timesyncd.service                | sysinit.target.wants
systemd-userdbd.socket                   | sockets.target.wants

Offline

#18 2026-07-05 19:25:55

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 77,006

Re: Cannot get DLNA to work on my server

At least nothing that looks like a high level service… what does exactly nmap report from that host?

iptables -nvL
nft list ruleset

If either issues a "command not found" error, don't bother to install it.
Is there otherwise a firewall-adjacent system in that segment (pihole etc.)?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#19 2026-07-05 19:30:18

Al4st0r
Member
Registered: 2026-07-03
Posts: 14

Re: Cannot get DLNA to work on my server

Both commands worked but required sudo.

The output of `iptables -nvL` is:

Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination         

Chain FORWARD (policy DROP 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination         
  20M   14G DOCKER-USER  all  --  *      *       0.0.0.0/0            0.0.0.0/0           
  20M   14G DOCKER-FORWARD  all  --  *      *       0.0.0.0/0            0.0.0.0/0           

Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination         

Chain DOCKER (4 references)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 ACCEPT     udp  --  !br-35adc897fa09 br-35adc897fa09  0.0.0.0/0            172.18.0.5           udp dpt:53
    0     0 ACCEPT     tcp  --  !br-35adc897fa09 br-35adc897fa09  0.0.0.0/0            172.18.0.5           tcp dpt:53
    0     0 ACCEPT     tcp  --  !br-70a078418075 br-70a078418075  0.0.0.0/0            172.19.0.7           tcp dpt:443
    0     0 ACCEPT     tcp  --  !br-70a078418075 br-70a078418075  0.0.0.0/0            172.19.0.7           tcp dpt:81
    0     0 ACCEPT     tcp  --  !br-70a078418075 br-70a078418075  0.0.0.0/0            172.19.0.7           tcp dpt:80
    0     0 DROP       all  --  !br-5f6b1c4180bc br-5f6b1c4180bc  0.0.0.0/0            0.0.0.0/0           
    0     0 DROP       all  --  !br-70a078418075 br-70a078418075  0.0.0.0/0            0.0.0.0/0           
    0     0 DROP       all  --  !br-35adc897fa09 br-35adc897fa09  0.0.0.0/0            0.0.0.0/0           
    0     0 DROP       all  --  !docker0 docker0  0.0.0.0/0            0.0.0.0/0           

Chain DOCKER-BRIDGE (1 references)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 DOCKER     all  --  *      br-5f6b1c4180bc  0.0.0.0/0            0.0.0.0/0           
    0     0 DOCKER     all  --  *      br-70a078418075  0.0.0.0/0            0.0.0.0/0           
    0     0 DOCKER     all  --  *      br-35adc897fa09  0.0.0.0/0            0.0.0.0/0           
    0     0 DOCKER     all  --  *      docker0  0.0.0.0/0            0.0.0.0/0           

Chain DOCKER-CT (1 references)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 ACCEPT     all  --  *      br-5f6b1c4180bc  0.0.0.0/0            0.0.0.0/0            ctstate RELATED,ESTABLISHED
4622K  264M ACCEPT     all  --  *      br-70a078418075  0.0.0.0/0            0.0.0.0/0            ctstate RELATED,ESTABLISHED
 3449 2050K ACCEPT     all  --  *      br-35adc897fa09  0.0.0.0/0            0.0.0.0/0            ctstate RELATED,ESTABLISHED
    0     0 ACCEPT     all  --  *      docker0  0.0.0.0/0            0.0.0.0/0            ctstate RELATED,ESTABLISHED

Chain DOCKER-FORWARD (1 references)
 pkts bytes target     prot opt in     out     source               destination         
  20M   14G DOCKER-CT  all  --  *      *       0.0.0.0/0            0.0.0.0/0           
  16M   14G DOCKER-INTERNAL  all  --  *      *       0.0.0.0/0            0.0.0.0/0           
  16M   14G DOCKER-BRIDGE  all  --  *      *       0.0.0.0/0            0.0.0.0/0           
    0     0 ACCEPT     all  --  br-5f6b1c4180bc *       0.0.0.0/0            0.0.0.0/0           
  16M   14G ACCEPT     all  --  br-70a078418075 *       0.0.0.0/0            0.0.0.0/0           
 3158  288K ACCEPT     all  --  br-35adc897fa09 *       0.0.0.0/0            0.0.0.0/0           
    0     0 ACCEPT     all  --  docker0 *       0.0.0.0/0            0.0.0.0/0           

Chain DOCKER-INTERNAL (1 references)
 pkts bytes target     prot opt in     out     source               destination         

Chain DOCKER-USER (1 references)
 pkts bytes target     prot opt in     out     source               destination

The output of `nft list ruleset` is:

# Warning: table ip nat is managed by iptables-nft, do not touch!
table ip nat {
	chain DOCKER {
		iifname != "br-70a078418075" tcp dport 80 counter packets 0 bytes 0 xt target "DNAT"
		iifname != "br-70a078418075" tcp dport 81 counter packets 0 bytes 0 xt target "DNAT"
		iifname != "br-70a078418075" tcp dport 443 counter packets 0 bytes 0 xt target "DNAT"
		iifname != "br-35adc897fa09" tcp dport 53 counter packets 0 bytes 0 xt target "DNAT"
		iifname != "br-35adc897fa09" udp dport 53 counter packets 0 bytes 0 xt target "DNAT"
	}

	chain PREROUTING {
		type nat hook prerouting priority dstnat; policy accept;
		xt match "addrtype" counter packets 2154 bytes 715285 jump DOCKER
	}

	chain OUTPUT {
		type nat hook output priority dstnat; policy accept;
		ip daddr != 127.0.0.0/8 xt match "addrtype" counter packets 1069 bytes 381870 jump DOCKER
	}

	chain POSTROUTING {
		type nat hook postrouting priority srcnat; policy accept;
		ip saddr 172.17.0.0/16 oifname != "docker0" counter packets 0 bytes 0 xt target "MASQUERADE"
		ip saddr 172.18.0.0/16 oifname != "br-35adc897fa09" counter packets 64 bytes 3840 xt target "MASQUERADE"
		ip saddr 172.19.0.0/16 oifname != "br-70a078418075" counter packets 75653 bytes 7555715 xt target "MASQUERADE"
		ip saddr 172.20.0.0/16 oifname != "br-5f6b1c4180bc" counter packets 0 bytes 0 xt target "MASQUERADE"
	}
}
# Warning: table ip filter is managed by iptables-nft, do not touch!
table ip filter {
	chain DOCKER {
		ip daddr 172.18.0.5 iifname != "br-35adc897fa09" oifname "br-35adc897fa09" udp dport 53 counter packets 0 bytes 0 accept
		ip daddr 172.18.0.5 iifname != "br-35adc897fa09" oifname "br-35adc897fa09" tcp dport 53 counter packets 0 bytes 0 accept
		ip daddr 172.19.0.7 iifname != "br-70a078418075" oifname "br-70a078418075" tcp dport 443 counter packets 0 bytes 0 accept
		ip daddr 172.19.0.7 iifname != "br-70a078418075" oifname "br-70a078418075" tcp dport 81 counter packets 0 bytes 0 accept
		ip daddr 172.19.0.7 iifname != "br-70a078418075" oifname "br-70a078418075" tcp dport 80 counter packets 0 bytes 0 accept
		iifname != "br-5f6b1c4180bc" oifname "br-5f6b1c4180bc" counter packets 0 bytes 0 drop
		iifname != "br-70a078418075" oifname "br-70a078418075" counter packets 0 bytes 0 drop
		iifname != "br-35adc897fa09" oifname "br-35adc897fa09" counter packets 0 bytes 0 drop
		iifname != "docker0" oifname "docker0" counter packets 0 bytes 0 drop
	}

	chain DOCKER-FORWARD {
		counter packets 20142459 bytes 14237480449 jump DOCKER-CT
		counter packets 15514504 bytes 13971120219 jump DOCKER-INTERNAL
		counter packets 15514504 bytes 13971120219 jump DOCKER-BRIDGE
		iifname "br-5f6b1c4180bc" counter packets 0 bytes 0 accept
		iifname "br-70a078418075" counter packets 15511346 bytes 13970831806 accept
		iifname "br-35adc897fa09" counter packets 3158 bytes 288413 accept
		iifname "docker0" counter packets 0 bytes 0 accept
	}

	chain DOCKER-BRIDGE {
		oifname "br-5f6b1c4180bc" counter packets 0 bytes 0 jump DOCKER
		oifname "br-70a078418075" counter packets 0 bytes 0 jump DOCKER
		oifname "br-35adc897fa09" counter packets 0 bytes 0 jump DOCKER
		oifname "docker0" counter packets 0 bytes 0 jump DOCKER
	}

	chain DOCKER-CT {
		oifname "br-5f6b1c4180bc" xt match "conntrack" counter packets 0 bytes 0 accept
		oifname "br-70a078418075" xt match "conntrack" counter packets 4624506 bytes 264310546 accept
		oifname "br-35adc897fa09" xt match "conntrack" counter packets 3449 bytes 2049684 accept
		oifname "docker0" xt match "conntrack" counter packets 0 bytes 0 accept
	}

	chain DOCKER-INTERNAL {
	}

	chain FORWARD {
		type filter hook forward priority filter; policy drop;
		counter packets 20142459 bytes 14237480449 jump DOCKER-USER
		counter packets 20142459 bytes 14237480449 jump DOCKER-FORWARD
	}

	chain DOCKER-USER {
	}
}
# Warning: table ip6 nat is managed by iptables-nft, do not touch!
table ip6 nat {
	chain DOCKER {
	}

	chain PREROUTING {
		type nat hook prerouting priority dstnat; policy accept;
		xt match "addrtype" counter packets 0 bytes 0 jump DOCKER
	}

	chain OUTPUT {
		type nat hook output priority dstnat; policy accept;
		ip6 daddr != ::1 xt match "addrtype" counter packets 0 bytes 0 jump DOCKER
	}
}
table ip6 filter {
	chain DOCKER {
	}

	chain DOCKER-FORWARD {
		counter packets 0 bytes 0 jump DOCKER-CT
		counter packets 0 bytes 0 jump DOCKER-INTERNAL
		counter packets 0 bytes 0 jump DOCKER-BRIDGE
	}

	chain DOCKER-BRIDGE {
	}

	chain DOCKER-CT {
	}

	chain DOCKER-INTERNAL {
	}

	chain FORWARD {
		type filter hook forward priority filter; policy accept;
		counter packets 0 bytes 0 jump DOCKER-USER
		counter packets 0 bytes 0 jump DOCKER-FORWARD
	}

	chain DOCKER-USER {
	}
}
table ip raw {
	chain PREROUTING {
		type filter hook prerouting priority raw; policy accept;
		ip daddr 172.19.0.2 iifname != "br-70a078418075" counter packets 0 bytes 0 drop
		ip daddr 172.18.0.2 iifname != "br-35adc897fa09" counter packets 0 bytes 0 drop
		ip daddr 172.20.0.2 iifname != "br-5f6b1c4180bc" counter packets 0 bytes 0 drop
		ip daddr 172.19.0.3 iifname != "br-70a078418075" counter packets 0 bytes 0 drop
		ip daddr 172.20.0.3 iifname != "br-5f6b1c4180bc" counter packets 0 bytes 0 drop
		ip daddr 172.19.0.4 iifname != "br-70a078418075" counter packets 0 bytes 0 drop
		ip daddr 172.20.0.4 iifname != "br-5f6b1c4180bc" counter packets 0 bytes 0 drop
		ip daddr 172.19.0.5 iifname != "br-70a078418075" counter packets 0 bytes 0 drop
		ip daddr 172.19.0.6 iifname != "br-70a078418075" counter packets 0 bytes 0 drop
		ip daddr 172.19.0.7 iifname != "br-70a078418075" counter packets 0 bytes 0 drop
		ip daddr 172.20.0.5 iifname != "br-5f6b1c4180bc" counter packets 0 bytes 0 drop
		ip daddr 172.18.0.3 iifname != "br-35adc897fa09" counter packets 0 bytes 0 drop
		ip daddr 172.18.0.4 iifname != "br-35adc897fa09" counter packets 0 bytes 0 drop
		ip daddr 172.18.0.5 iifname != "br-35adc897fa09" counter packets 0 bytes 0 drop
	}
}

Most is related to docker, and nothing seems inherently wrong...

EDIT: Btw, there is not firewall-like service active... I used to have pihole but I stopped using it. I do use nginx proxy manager to route other services to my domain...

Last edited by Al4st0r (2026-07-05 19:35:45)

Offline

#20 2026-07-05 19:33:59

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 77,006

Re: Cannot get DLNA to work on my server

Afaict that's just really the docker stuff

seth wrote:

what does exactly nmap report from that host? [that fails to curl]
Is there otherwise a firewall-adjacent system in that segment (pihole etc.)?

ssh btw works?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#21 2026-07-05 19:37:08

Al4st0r
Member
Registered: 2026-07-03
Posts: 14

Re: Cannot get DLNA to work on my server

There is not firewall-like service active... I used to have pihole but I stopped using it. I do use nginx proxy manager to route other services to my domain...

Yes, ssh works, both through my domain and directly via ip (I'm actually executing most of this via ssh)

Offline

#22 2026-07-05 19:40:48

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 77,006

Re: Cannot get DLNA to work on my server

I do use nginx proxy manager to route other services to my domain...

Do you have to forward 22 for ssh to work?

seth wrote:

what does exactly nmap report from that host? [that fails to curl]

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#23 2026-07-05 20:23:45

Al4st0r
Member
Registered: 2026-07-03
Posts: 14

Re: Cannot get DLNA to work on my server

No, `ssh` works by itself, via `ssh al4st0r@192.168.0.3` without any config in .ssh/config. Nginx isn't set to reroute port 22 at all. I actually use cloudflared tunnels to route my domain to `ssh://localhost:22`.

When running `sudo nmap -sU -sT -p U:1900,T:8200 192.168.0.3` from my main computer (not the server) i get:

Starting Nmap 7.99 ( https://nmap.org ) at 2026-07-05 22:19 +0200
Nmap scan report for al4st0rserver (192.168.0.3)
Host is up (0.088s latency).

PORT     STATE  SERVICE
8200/tcp open   trivnet1
1900/udp closed upnp
MAC Address: 08:ED:B9:2E:A0:DD (Hon Hai Precision Ind.)

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

Offline

#24 2026-07-05 20:48:13

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 77,006

Re: Cannot get DLNA to work on my server

So 8200 is remotely open, access works from the localhost (server isn't crashing) but not remote, nothing in the mdlna config suggests the access is limited, there're not netfilter rules on the server limiting access either (which also would be reflected by nmap)
ssh works (so it cannot be MTU or network stability)

If you stop mdlna and run " ncat -lp 8200" on the server and then "echo snafu | ncat 192.168.0.3 8200" on the relevant client, does that make it to the server?
What about 

echo "Minions ipsum aute velit hahaha voluptate me want bananaaa! Qui wiiiii pepete duis underweaaar. Daa tempor consequat bee do bee do bee do pepete nostrud incididunt belloo! Ut bananaaaa jeje. Hana dul sae po kass tulaliloo daa magna bappleees. Belloo! exercitation qui reprehenderit wiiiii. Bee do bee do bee do duis butt veniam ex aaaaaah po kass magna incididunt poulet tikka masala. Chasy nostrud pepete duis ut et laboris la bodaaa duis para tú." | ncat 192.168.0.3 8200

?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#25 2026-07-05 21:44:24

Al4st0r
Member
Registered: 2026-07-03
Posts: 14

Re: Cannot get DLNA to work on my server

This works! I can recieve the message via ncat at the server!

And if i start minidlna again and try to use ncat again it says:

Ncat: bind to 0.0.0.0:8200: Address already in use. QUITTING.

So this looks ok i guess?

PS: I absolutely love Minions ipsum, I'm going to start using it

Offline

Pages: 1 2

Board footer

Powered by FluxBB