July 22, 20223 yr So, I'm not exactly a dev but I just tested it this does work. The problem, when DSD is sent as x-dsd many renderers like Jriver, BubbleUPnP, USB Audio Player, even receivers that should support DSD properly over DLNA are actually receiving PCM 352Mhz instead of 2.8Mhz. I forked somebody's copy of MiniDLNA (since the original source isn't on github) and made the changes here: https://github.com/fandangos/minidlna/commit/0f402a51120ca19d15d70291ae3d9cd629d76062 I tested it inside Unraid but since I compiled it on Ubuntu it required a lot of dependencies. After copying all to binhex-MiniDLNA docker container alongside my compiled binary - deps went to /usr/lib - binary went to /usb/sbin/minidlnad I can say it worked as it should I created a snapshot from binhex-minidlna container on my server but this resulted in a 1.5GB tar file and this isn't pratical to share. So, if anyone knows how to build a docker image I can share here for anyone interested in pure DSD playback.
September 20, 20223 yr Hey guys, I have been using this forever, but it stopped working in the last week. This is the log ___. .__ .__ \_ |__ |__| ____ | |__ ____ ___ ___ | __ \| |/ \| | \_/ __ \\ \/ / | \_\ \ | | \ Y \ ___/ > < |___ /__|___| /___| /\___ >__/\_ \ \/ \/ \/ \/ \/ https://hub.docker.com/u/binhex/ 2022-09-20 11:38:27.952087 [info] Host is running unRAID 2022-09-20 11:38:28.646084 [info] System information Linux b145c01db624 5.10.21-Unraid #1 SMP Sun Mar 7 13:39:02 PST 2021 x86_64 GNU/Linux 2022-09-20 11:38:29.539366 [info] OS_ARCH defined as 'x86-64' 2022-09-20 11:38:30.777404 [info] PUID defined as '99' 2022-09-20 11:38:32.657967 [info] PGID defined as '100' 2022-09-20 11:38:51.489580 [info] UMASK defined as '000' 2022-09-20 11:38:51.528883 [info] Permissions already set for '/config' 2022-09-20 11:38:53.063372 [info] Deleting files in /tmp (non recursive)... 2022-09-20 11:38:53.847467 [info] SCAN_ON_BOOT defined as 'Yes' 2022-09-20 11:38:53.877272 [info] SCHEDULE_SCAN_DAYS defined as '06' 2022-09-20 11:38:53.907330 [info] SCHEDULE_SCAN_HOURS defined as '02' 2022-09-20 11:38:54.050392 [info] Starting Supervisor... 2022-09-20 11:40:16,300 INFO Included extra file "/etc/supervisor/conf.d/minidlna.conf" during parsing 2022-09-20 11:40:16,301 INFO Set uid to user 0 succeeded 2022-09-20 11:40:17,122 INFO supervisord started with pid 6 2022-09-20 11:40:18,124 INFO spawned: 'crond' with pid 72 2022-09-20 11:40:18,126 INFO spawned: 'start' with pid 73 2022-09-20 11:40:18,127 INFO reaped unknown pid 7 (exit status 0) 2022-09-20 11:40:18,134 DEBG 'start' stdout output: [info] PID file from previous run found, deleting file /home/nobody/.config/minidlna/minidlna.pid... 2022-09-20 11:40:18,134 INFO success: start entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2022-09-20 11:40:19,135 INFO success: crond entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2022-09-20 11:40:51,153 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 22775648492304 for <Subprocess at 22775648487024 with name start in state RUNNING> (stdout)> 2022-09-20 11:40:51,153 DEBG fd 15 closed, stopped monitoring <POutputDispatcher at 22775648492352 for <Subprocess at 22775648487024 with name start in state RUNNING> (stderr)> 2022-09-20 11:40:51,153 INFO exited: start (exit status 0; expected) 2022-09-20 11:40:51,154 DEBG received SIGCHLD indicating a child quit Seems to just quit, I have tried deleting the .pid, reinstalled, entire directory delete + reinstall, plus I rebooted my server.. I'm out of idea's.. anyone able to point me in the correct direction?
March 22, 20233 yr Hey everyone, Trying very unsuccessfully to get Unraid SMB to work with a Denon HEOS amp. Realized SMB 1 has been long discontinued and, since the app doesn't support SMB 2, I'm stuck looking at alternatives. Currently, I have multiple paths with music stored in them. That is, I have a folder structure that looks something like this: AUDIO LOSSLESS/ALBUMS AUDIO LOSSLESS/Hi-RES (which has BLU-RAY AUDIO, DSF 2.0, DSF 5.1, DVD-A (FLAC), and FLAC in it) AUDIO LOSSLESS/SOME OTHER FOLDERS AUDIO LOSSY/ALBUMS Here's the conundrum. I've tried setting up two PATHS within the minidlna config because I don't want it looking at every single folder (i.e., BLU-RAY AUDIO won't help a 2.0 receiver NOR will DSF 5.1 or DVD-A FLAC files for that matter). Assuming it's looking for "/media", when it attempts to rebuild the config files, it errors out and drops the docker off my machine and I have to install. What I want to do is have it look at a handful of the above paths, specifically: AUDIO LOSSLESS/ALBUMS/ AUDIO LOSSLESS/HI-RES/DSF/2.0 AUDIO LOSSLESS/HI-RES/FLAC AUDIO LOSSLESS/A COUPLE OF OTHER FOLDERS AUDIO LOSSY/ALBUMS Is there a way to point to multiple paths within the config? Or do I have to edit something manually? Or, am I stuck doing what I really DON'T want to do, and put what I want to be seen in one folder so it can scan accordingly? I really don't want to do the last option so any help here is appreciated. EDIT/UPDATE: I did some further digging and could never get it to look at the folders structured the way I did. Only way around this was to restructure my folders into Stereo and Multi-Channel within one parent. Problem is solved but did notice another issue. When scrubbing (using the HEOS app), DSF files will get all static-y when they start playing from where they resume. Not a huge thing but noticed this quirk. I'm just glad to have my hi-res audio playable on my 2.0 amp now. Edited March 23, 20233 yr by AdrianF Updated at bottom of question
August 14, 20232 yr On 9/19/2022 at 10:26 PM, Addy said: Hey guys, I have been using this forever, but it stopped working in the last week. This is the log ___. .__ .__ \_ |__ |__| ____ | |__ ____ ___ ___ | __ \| |/ \| | \_/ __ \\ \/ / | \_\ \ | | \ Y \ ___/ > < |___ /__|___| /___| /\___ >__/\_ \ \/ \/ \/ \/ \/ https://hub.docker.com/u/binhex/ 2022-09-20 11:38:27.952087 [info] Host is running unRAID 2022-09-20 11:38:28.646084 [info] System information Linux b145c01db624 5.10.21-Unraid #1 SMP Sun Mar 7 13:39:02 PST 2021 x86_64 GNU/Linux 2022-09-20 11:38:29.539366 [info] OS_ARCH defined as 'x86-64' 2022-09-20 11:38:30.777404 [info] PUID defined as '99' 2022-09-20 11:38:32.657967 [info] PGID defined as '100' 2022-09-20 11:38:51.489580 [info] UMASK defined as '000' 2022-09-20 11:38:51.528883 [info] Permissions already set for '/config' 2022-09-20 11:38:53.063372 [info] Deleting files in /tmp (non recursive)... 2022-09-20 11:38:53.847467 [info] SCAN_ON_BOOT defined as 'Yes' 2022-09-20 11:38:53.877272 [info] SCHEDULE_SCAN_DAYS defined as '06' 2022-09-20 11:38:53.907330 [info] SCHEDULE_SCAN_HOURS defined as '02' 2022-09-20 11:38:54.050392 [info] Starting Supervisor... 2022-09-20 11:40:16,300 INFO Included extra file "/etc/supervisor/conf.d/minidlna.conf" during parsing 2022-09-20 11:40:16,301 INFO Set uid to user 0 succeeded 2022-09-20 11:40:17,122 INFO supervisord started with pid 6 2022-09-20 11:40:18,124 INFO spawned: 'crond' with pid 72 2022-09-20 11:40:18,126 INFO spawned: 'start' with pid 73 2022-09-20 11:40:18,127 INFO reaped unknown pid 7 (exit status 0) 2022-09-20 11:40:18,134 DEBG 'start' stdout output: [info] PID file from previous run found, deleting file /home/nobody/.config/minidlna/minidlna.pid... 2022-09-20 11:40:18,134 INFO success: start entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2022-09-20 11:40:19,135 INFO success: crond entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2022-09-20 11:40:51,153 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 22775648492304 for <Subprocess at 22775648487024 with name start in state RUNNING> (stdout)> 2022-09-20 11:40:51,153 DEBG fd 15 closed, stopped monitoring <POutputDispatcher at 22775648492352 for <Subprocess at 22775648487024 with name start in state RUNNING> (stderr)> 2022-09-20 11:40:51,153 INFO exited: start (exit status 0; expected) 2022-09-20 11:40:51,154 DEBG received SIGCHLD indicating a child quit Seems to just quit, I have tried deleting the .pid, reinstalled, entire directory delete + reinstall, plus I rebooted my server.. I'm out of idea's.. anyone able to point me in the correct direction? Seeing this exact same issue. Did you ever get it resolved? I even tried completely deleting the container/appdata and i'm still getting the issue.
August 14, 20232 yr Author Seeing this exact same issue. Did you ever get it resolved? I even tried completely deleting the container/appdata and i'm still getting the issue.This is odd! I am using this image myself, just restarted the container and it started with no problems. Can you verify that the host path you set for /media exists and has the correct permissions setSent from my 22021211RG using Tapatalk
September 28, 20232 yr On 8/14/2023 at 2:29 PM, binhex said: This is odd! I am using this image myself, just restarted the container and it started with no problems. Can you verify that the host path you set for /media exists and has the correct permissions set Sent from my 22021211RG using Tapatalk Apologies for the very late reply! I didn't get a notification email (I need to check the settings on this forum). The media folder did exist and the correct perms were there. It was working fine for a while and then just stopped one day. I did get it working again, however that was over a month ago and I don't exactly remember what I did to get it going again (I hate that I've now authored one of "those" posts). I want to say that maybe it was related to a change in the docker network settings (this was around the time that there were issues with macvlan with an unraid update). I currently have ipvlan in the docker settings.
February 19, 20242 yr Hi, I saw in logfile: [2023/10/04 20:53:40] upnphttp.c:1074: warn: /favicon.ico not found, responding ERROR 404 can I add a favicon into docker ? so that my TV is showing for example a unraid picture ?
February 23, 20242 yr I found: https://github.com/ZsBT/minidlna-custom-icon I´ve add these at the end of config: icon_png_small=/config/icons/icon_x48.png # 48px PNG icon icon_png_large=/config/icons/icon_x120.png # 120px PNG icon icon_jpeg_small=/config/icons/icon_x48.jpg # 48px JPEG icon icon_jpeg_large=/config/icons/icon_x120.jpg # 120px JPEG icon copied them: cp -r /mnt/user/media/icons/ /mnt/user/appdata/binhex-minidlna/icons/ chown -cR nobody:users /mnt/user/appdata/binhex-minidlna/icons/ restarted the docker --> error about the icons 😞 Edited February 23, 20242 yr by Avenga
April 8, 20242 yr why cant i get it to work? Simply ran the container, cant get to 8200, nor can i get vlc or my denon heos app to find it. I tried adding port 8200 manually, but to no avail. Logs: 2024-04-08 21:39:05.019086 [info] Host is running unRAID 2024-04-08 21:39:05.045991 [info] System information Linux server 6.1.79-Unraid #1 SMP PREEMPT_DYNAMIC Fri Mar 29 13:34:03 PDT 2024 x86_64 GNU/Linux 2024-04-08 21:39:05.081450 [info] PUID defined as '99' 2024-04-08 21:39:05.139614 [info] PGID defined as '100' 2024-04-08 21:39:05.217453 [info] UMASK defined as '000' 2024-04-08 21:39:05.249474 [info] Permissions already set for '/config' 2024-04-08 21:39:05.285858 [info] Deleting files in /tmp (non recursive)... 2024-04-08 21:39:05.320576 [info] SCAN_ON_BOOT defined as 'yes' 2024-04-08 21:39:05.355345 [info] SCHEDULE_SCAN_DAYS defined as '06' 2024-04-08 21:39:05.384852 [info] SCHEDULE_SCAN_HOURS defined as '02' 2024-04-08 21:39:05.422548 [info] Starting Supervisor... 2024-04-08 21:39:05,735 INFO Included extra file "/etc/supervisor/conf.d/minidlna.conf" during parsing 2024-04-08 21:39:05,735 INFO Set uid to user 0 succeeded 2024-04-08 21:39:05,738 INFO supervisord started with pid 7 2024-04-08 21:39:06,742 INFO spawned: 'crond' with pid 62 2024-04-08 21:39:06,744 INFO spawned: 'start' with pid 63 2024-04-08 21:39:06,745 INFO reaped unknown pid 8 (exit status 0) 2024-04-08 21:39:06,902 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 22398605550800 for <Subprocess at 22398605392464 with name start in state STARTING> (stdout)> 2024-04-08 21:39:06,903 DEBG fd 15 closed, stopped monitoring <POutputDispatcher at 22398603333648 for <Subprocess at 22398605392464 with name start in state STARTING> (stderr)> 2024-04-08 21:39:06,903 INFO success: start entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2024-04-08 21:39:06,903 INFO exited: start (exit status 0; expected) 2024-04-08 21:39:06,903 DEBG received SIGCHLD indicating a child quit 2024-04-08 21:39:07,904 INFO success: crond entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
April 8, 20242 yr Author 3 minutes ago, Kees Fluitman said: Simply ran the container, cant get to 8200, nor can i get vlc or my denon heos app to find it. I tried adding port 8200 manually, but to no avail. the 'network type' should be set to 'bridge' is this the case? the reason i ask is that in bridge mode you do not specify ports.
April 8, 20242 yr it was set to host. Doesn't work both ways. either bridge or host... Also, nothing is listening on port 8200 on my unraid server when the container is running... [2024/04/08 21:59:54] scanner.c:820: warn: Scanning /media finished (6871 files)! [2024/04/08 21:59:54] playlist.c:135: warn: Parsing playlists... [2024/04/08 21:59:54] playlist.c:269: warn: Finished parsing playlists. [2024/04/08 22:01:37] minidlna.c:1134: warn: Starting MiniDLNA version 1.3.3. [2024/04/08 22:01:37] minidlna.c:394: warn: Creating new database at /config/files.db [2024/04/08 22:01:37] minissdp.c:132: error: bind(udp): Address already in use [2024/04/08 22:01:37] getifaddr.c:110: error: Network interface eth0 not found [2024/04/08 22:01:37] minissdp.c:848: error: connect("/var/run/minissdpd.sock"): No such file or directory[2024/04/08 22:01:37] minidlna.c:1170: fatal: Failed to connect to MiniSSDPd. EXITING[2024/04/08 22:01:37] scanner.c:731: warn: Scanning /media [2024/04/08 22:03:10] minidlna.c:1134: warn: Starting MiniDLNA version 1.3.3. [2024/04/08 22:03:10] minidlna.c:394: warn: Creating new database at /config/files.db [2024/04/08 22:03:10] minissdp.c:132: error: bind(udp): Address already in use [2024/04/08 22:03:10] minissdp.c:84: error: setsockopt(udp, IP_ADD_MEMBERSHIP): Bad file descriptor [2024/04/08 22:03:10] minissdp.c:198: warn: Failed to add multicast membership for address 192.168.1.165 [2024/04/08 22:03:10] minissdp.c:84: error: setsockopt(udp, IP_ADD_MEMBERSHIP): Bad file descriptor [2024/04/08 22:03:10] minissdp.c:198: warn: Failed to add multicast membership for address 10.253.0.1 [2024/04/08 22:03:10] minissdp.c:84: error: setsockopt(udp, IP_ADD_MEMBERSHIP): Bad file descriptor [2024/04/08 22:03:10] minissdp.c:198: warn: Failed to add multicast membership for address 192.168.1.223 [2024/04/08 22:03:10] minissdp.c:84: error: setsockopt(udp, IP_ADD_MEMBERSHIP): Bad file descriptor [2024/04/08 22:03:10] minissdp.c:198: warn: Failed to add multicast membership for address 192.168.122.1 [2024/04/08 22:03:10] minissdp.c:84: error: setsockopt(udp, IP_ADD_MEMBERSHIP): Bad file descriptor [2024/04/08 22:03:10] minissdp.c:198: warn: Failed to add multicast membership for address 100.91.251.7 [2024/04/08 22:03:10] minissdp.c:84: error: setsockopt(udp, IP_ADD_MEMBERSHIP): Bad file descriptor [2024/04/08 22:03:10] minissdp.c:198: warn: Failed to add multicast membership for address 172.23.0.1 [2024/04/08 22:03:10] minissdp.c:84: error: setsockopt(udp, IP_ADD_MEMBERSHIP): Bad file descriptor [2024/04/08 22:03:10] minissdp.c:198: warn: Failed to add multicast membership for address 172.22.0.1 [2024/04/08 22:03:10] minissdp.c:84: error: setsockopt(udp, IP_ADD_MEMBERSHIP): Bad file descriptor [2024/04/08 22:03:10] minissdp.c:198: warn: Failed to add multicast membership for address 172.18.0.1 [2024/04/08 22:03:10] scanner.c:731: warn: Scanning /media [2024/04/08 22:03:11] minissdp.c:816: error: sendto(udp_shutdown=7): Required key not available [2024/04/08 22:03:11] minissdp.c:816: error: sendto(udp_shutdown=7): Required key not available [2024/04/08 22:03:11] minissdp.c:324: error: sendto(udp_notify=7, 10.253.0.1): Required key not available [2024/04/08 22:03:11] minissdp.c:324: error: sendto(udp_notify=7, 10.253.0.1): Required key not available [2024/04/08 22:03:11] minissdp.c:324: error: sendto(udp_notify=7, 10.253.0.1): Required key not available [2024/04/08 22:03:11] minissdp.c:324: error: sendto(udp_notify=7, 10.253.0.1): Required key not available [2024/04/08 22:03:11] minissdp.c:324: error: sendto(udp_notify=7, 10.253.0.1): Required key not available [2024/04/08 22:03:11] minissdp.c:324: error: sendto(udp_notify=7, 10.253.0.1): Required key not available [2024/04/08 22:03:11] minissdp.c:324: error: sendto(udp_notify=7, 10.253.0.1): Required key not available [2024/04/08 22:03:11] minissdp.c:324: error: sendto(udp_notify=7, 10.253.0.1): Required key not available [2024/04/08 22:03:11] minissdp.c:324: error: sendto(udp_notify=7, 10.253.0.1): Required key not available [2024/04/08 22:03:11] minissdp.c:324: error: sendto(udp_notify=7, 10.253.0.1): Required key not available [2024/04/08 22:03:11] minissdp.c:324: error: sendto(udp_notify=7, 10.253.0.1): Required key not available [2024/04/08 22:03:11] minissdp.c:324: error: sendto(udp_notify=7, 10.253.0.1): Required key not available [2024/04/08 22:03:12] minissdp.c:848: error: connect("/var/run/minissdpd.sock"): No such file or directory[2024/04/08 22:03:12] minidlna.c:1170: fatal: Failed to connect to MiniSSDPd. When i set network interface to br0. I dont get that error anymore, but still get this [2024/04/08 22:09:18] minissdp.c:132: error: bind(udp): Address already in use Ah ic. I think it's because jellyfin is already using port 1900. Ill check. Edited April 8, 20242 yr by Kees Fluitman
August 22, 20241 yr UPDATE: SOLVED (see below): Greetings... I've been using MiniDLNA for a few years now, and specifically in UNRAID since installing in Feb. of 2023 when I first started using UNRAID. It seems to be the only DLNA server that just shows up in everything that I use, Roku Media Player, LG Smart TV's, VLC under Shield, and Linux, etc., without needing configuration. However, something has changed recently and the only thing that I have done is upgrade to the newest version of UNRAID. The MiniDLNA server still shows up on all devices however it is no longer seeing any of my media. The Roku Media Server states that it did not find any compatible media, here is what VLC shows, just no media: I've tried stopping the container and modified the config file; both by changing the `/media` path to `/mnt/user/media` and just setting the paths in the Docker GUI to `/Movies` for example and actually specifying the folder paths in the config file. No matter what I change it to, the Docker Logs give the following error in all cases: >>>>> [2024/08/22 09:02:38] minidlna.c:669: error: Media directory "/media" not accessible [No such file or directory] <<<<< >>>>> [2024/08/22 09:09:20] minidlna.c:669: error: Media directory "V,/mnt/user/media/Movies" not accessible [No such file or directory] [2024/08/22 09:09:20] minidlna.c:669: error: Media directory "V,/mnt/user/media/Videos" not accessible [No such file or directory] [2024/08/22 09:09:20] minidlna.c:669: error: Media directory "A,/mnt/user/media/Music" not accessible [No such file or directory] [2024/08/22 09:09:20] minidlna.c:669: error: Media directory "A,/mnt/user/media/Podcast" not accessible [No such file or directory] [2024/08/22 09:09:20] minidlna.c:669: error: Media directory "P,/mnt/user/media/Pictures" not accessible [No such file or directory] <<<<< >>>>> [2024/08/22 10:17:39] minidlna.c:669: error: Media directory "/mnt/user/media" not accessible [No such file or directory] <<<<< ...see attached file: 2024-08-22_MiniDLNA-Data.txt The location of the share is correct and set to public, so there should not be any permission issues: Any advise appreciated. Also... From the initial install, MiniDLNA has always been set as a `Host` if set to `Bridge` it does not show up in any devices. UPDATE: It seems that I did make a slight change to my system after all. My cache drives were separate, and I had pooled them together for redundancy. I had set the `appdata` folder to be moved/stored on the cache drive pool. While it didn't seem to affect any other containers, MiniDLNA didn't seem to care for it. Once I reversed that and had the `appdata` folder go back to the array, MiniDLNA once again was able to find the media folder and is working just fine now. Edited August 29, 20241 yr by AgentEccks adding info RE `Host` and `Bridge`
November 3, 20241 yr On 10/24/2017 at 12:48 PM, binhex said: you can define a scan day and hour using the SCHEDULE_SCAN_DAYS and SCHEDULE_SCAN_HOURS values respectively, if you want it to scan for multiple days/hours then use a comma to separate the values, e.g.:- SCHEDULE_SCAN_DAYS = 03,05,06 note monday = 00 and sunday = 06 Shouldn't Sunday be 07? I'm just trying to setup my minidlna to feed my yamaha-AV-amp via local network. But independent from the way I look at the music provided by minidlna-Server (foobar2000, Windows-Explorer, Yamaha-Amp.) there are some folders that refuse showing the *.jpg-file which is inside the folder as a folder picture. Why? Is there an issue concerning certain characters or filename-lenghts? EDIT: Alternatively trying plex as a DLNA-Server, I just saw that exactly these folders that are missing their photos, were not provided via DLNA. Checking owners and rights, I recognized that these folders including the containing files had another owner. Not nobody, but a certain user - probably caused by some copy-actions during completing the nas-file-structure. I changed the owner and reloaded plex' media-content via plex' GUI. Subsequently the missing folders are shown via DLNA. Stopping plex and restarting minidlna (Variable: SCAN_ON_BOOT: Yes) I hoped having solved the issue, but pictures of the owner-corrected folders are still missing... 😒 Why? What else can I do to complete the folders' missing photos inside the datastream provided via DLNA? EDIT2: I just saw that some piece of software wrote hidden secure system-jpg-files (AlbumArt_(cryptic-characters)_small.jpg, AlbumArt_(cryptic-characters)_large.jpg, AlbumArtsmall.jpg) into my CD-folders. If I exclude these hidden files from copying from my PC to my unraid-Server, none of the folders has got a picture anymore. So I recognized that only the newest folders, where there are no hidden jpg-files have no pictures. Which software does interfere with my folder- and data-structure and writes these hidden files? Windows Media Player? Edited November 3, 20241 yr by doc_jochim
January 1, 20251 yr Hello everyone, first of all, thank you very much for this great container, it works perfectly. However, I have a small challenge. My Unraid host operates in the 10.10.10.X address range, while my "consumer" network devices are in the 10.10.1.X range. Unfortunately, they cannot access the DLNA. If they are in the same range, it works. I have therefore set the Docker network type to "Custom: br0" and assigned a specific IP address. Unfortunately, the Docker container does not receive its own IP and is not separately visible in my network. What am I doing wrong? Thank you very much for any tips!
May 18, 20251 yr I am running minidlna on my unraid 7.01. As i see an earlier post worked fine until very recently. Not made any changes i am aware of. Been running in host mode earlier but tried changing to bridge mode as hinted in an earlier post but still not working again. Anyone that understands what may be wrong? Including my minidlna log. 2025-05-18 12:46:30.834555 [info] Host is running unRAID 2025-05-18 12:46:30.852257 [info] System information: Linux bae8dbca5769 6.6.78-Unraid #2 SMP PREEMPT_DYNAMIC Thu Feb 20 13:33:15 PST 2025 x86_64 GNU/Linux 2025-05-18 12:46:30.869504 [info] Image tags: BASE_RELEASE_TAG=2025012801,IMAGE_RELEASE_TAG=1.3.3-5-01 2025-05-18 12:46:30.890855 [info] PUID defined as '99' 2025-05-18 12:46:30.922372 [info] PGID defined as '100' 2025-05-18 12:46:30.956102 [info] UMASK defined as '000' 2025-05-18 12:46:30.975900 [info] Permissions already set for '/config' 2025-05-18 12:46:31.003553 [info] Deleting files in /tmp (non recursive)... 2025-05-18 12:46:31.027591 [info] SCAN_ON_BOOT defined as 'yes' 2025-05-18 12:46:31.048802 [info] SCHEDULE_SCAN_DAYS defined as '06' 2025-05-18 12:46:31.068947 [info] SCHEDULE_SCAN_HOURS defined as '02' 2025-05-18 12:46:31.098194 [info] SHARED_NETWORK defined as 'no' 2025-05-18 12:46:31.117490 [info] Starting Supervisor... 2025-05-18 12:46:31,351 INFO Included extra file "/etc/supervisor/conf.d/minidlna.conf" during parsing 2025-05-18 12:46:31,351 INFO Set uid to user 0 succeeded 2025-05-18 12:46:31,353 INFO supervisord started with pid 7 2025-05-18 12:46:32,357 INFO spawned: 'crond' with pid 74 2025-05-18 12:46:32,360 INFO spawned: 'start' with pid 75 2025-05-18 12:46:32,361 INFO reaped unknown pid 8 (exit status 0) 2025-05-18 12:46:33,362 INFO success: crond entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2025-05-18 12:46:33,362 INFO success: start entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2025-05-18 12:46:48,415 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 22679913647632 for <Subprocess at 22679913645712 with name start in state RUNNING> (stdout)> 2025-05-18 12:46:48,415 DEBG fd 15 closed, stopped monitoring <POutputDispatcher at 22679915501584 for <Subprocess at 22679913645712 with name start in state RUNNING> (stderr)> 2025-05-18 12:46:48,416 INFO exited: start (exit status 0; expected) 2025-05-18 12:46:48,416 DEBG received SIGCHLD indicating a child quit
July 19, 2025Jul 19 Author 2 hours ago, Bob@unraid said:Any news? I got the exact same log file like @suxIm unable to replicate this issue, i just tried from a clean configuration from CA and i can see from the log i get a start and if i go to the console of the container i can see the minidlna process is running, what am i missing here?
July 19, 2025Jul 19 Thanks for the fast reply. To be sure I also delete the minidlna folder in the the appdata share, but I am still getting the same error. Can I provide you log files or something to help?
July 21, 2025Jul 21 Author On 7/20/2025 at 12:17 AM, Bob@unraid said:Thanks for the fast reply.To be sure I also delete the minidlna folder in the the appdata share, but I am still getting the same error.Can I provide you log files or something to help?you can but i dont think its going to tell me much, i got a sneaky feeling this is unraid related, im on v6, i assume you are on v7, right?.
July 27, 2025Jul 27 Author 16 hours ago, Bob@unraid said:ok, yes v7 latest releaseWhich version are you running?, if it's not the latest 7.1.4 then i would advise as a first step to get you up to the latest stable version, then try it again.
April 11Apr 11 On 8/22/2024 at 8:10 PM, AgentEccks said:UPDATE: SOLVED (see below):Greetings... I've been using MiniDLNA for a few years now, and specifically in UNRAID since installing in Feb. of 2023 when I first started using UNRAID. It seems to be the only DLNA server that just shows up in everything that I use, Roku Media Player, LG Smart TV's, VLC under Shield, and Linux, etc., without needing configuration. However, something has changed recently and the only thing that I have done is upgrade to the newest version of UNRAID. The MiniDLNA server still shows up on all devices however it is no longer seeing any of my media. The Roku Media Server states that it did not find any compatible media, here is what VLC shows, just no media: I've tried stopping the container and modified the config file; both by changing the `/media` path to `/mnt/user/media` and just setting the paths in the Docker GUI to `/Movies` for example and actually specifying the folder paths in the config file. No matter what I change it to, the Docker Logs give the following error in all cases: >>>>> [2024/08/22 09:02:38] minidlna.c:669: error: Media directory "/media" not accessible [No such file or directory]<<<<<>>>>> [2024/08/22 09:09:20] minidlna.c:669: error: Media directory "V,/mnt/user/media/Movies" not accessible [No such file or directory] [2024/08/22 09:09:20] minidlna.c:669: error: Media directory "V,/mnt/user/media/Videos" not accessible [No such file or directory] [2024/08/22 09:09:20] minidlna.c:669: error: Media directory "A,/mnt/user/media/Music" not accessible [No such file or directory] [2024/08/22 09:09:20] minidlna.c:669: error: Media directory "A,/mnt/user/media/Podcast" not accessible [No such file or directory] [2024/08/22 09:09:20] minidlna.c:669: error: Media directory "P,/mnt/user/media/Pictures" not accessible [No such file or directory]<<<<<>>>>> [2024/08/22 10:17:39] minidlna.c:669: error: Media directory "/mnt/user/media" not accessible [No such file or directory]<<<<<...see attached file:2024-08-22_MiniDLNA-Data.txt The location of the share is correct and set to public, so there should not be any permission issues: Any advise appreciated. Also...From the initial install, MiniDLNA has always been set as a `Host` if set to `Bridge` it does not show up in any devices. UPDATE:It seems that I did make a slight change to my system after all.My cache drives were separate, and I had pooled them together for redundancy. I had set the `appdata` folder to be moved/stored on the cache drive pool. While it didn't seem to affect any other containers, MiniDLNA didn't seem to care for it. Once I reversed that and had the `appdata` folder go back to the array, MiniDLNA once again was able to find the media folder and is working just fine now.Did you ever get your appdata to run on your cache again ?
April 13Apr 13 Yes, it's been working fine per my update, but I just updated again today.I will post is I have any issues.
May 10May 10 @binhex Would it be possible to change the minidlna.conf on Container startup based on the number of media dirs added (like with an additional var "MINIDLNA_MEDIA_DIR_x"), so that we dont have to edit the conf file manually if we want to use more then one media dir? And can someone please explain me why i should use the SCHEDULE_SCAN settings (frequently and at startup) if minidlna as inotify support anyway?
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.