Amahi Forums

Hoping for some direction here please.

I had Amahi 7 with Fedora 24 working well for many years. Could see my pics, music, and video on my recently purchased LG Smart TV. Decided to update my server and installed Fedora 27 server and Amahi 11. I'm not really a linux person (more PC), but things went OK and was able to view my shares, install extra disks, and partition for my media and backups. Installed minidlna and followed the wiki to set up the config file to point to my media.

I can see the media folders and the files on my TV, but cannot access them. Changed permissions to 777 thinking it might be that, no luck. Saw one of the posts suggesting using command line to update, tried that, reinstalled minidlna, and still no luck. I have uninstalled minidlna, refreshed, rebooted and reinstalled. Tried making different shares for media, all to no avail. The minidlna server is running according to both the HDA GUI ans well as when I query with systemctl. Unfortunately, I cannot seem to access the log file; I'm not sure if it exists in the folder specified.

My HDA is set to be the DNS for my PC, but I let the router do DHCP. This was never a problem in the past with Amahi 7 install for me.

Many thanks in advance for any thoughts or directions.

Tom

Have you checked DLNA page in the wiki?

There is no mini dlna log for this version of Fedora.

Yes, I've run through each of the configuration and troubleshooting steps to change ownership/permissions. On my PC, I can see the media server, and when opening a client like WMP, I can see the media server listed and can view the files and their properties. They don't seem to be able to be opened on the client.

Thank you in advance.

I am unsure what else to suggest.

Might try submitting a bug report.

If you do, please post the bug number here.

Otherwise, might try searching the forums here. Might be a solution out there.

I tried a fresh install of Fedora 27 Server and Amahi, no real change. I installed Subsonic and am able to stream my music to the clients without difficulty. I noticed that when opening MediaMonkey the path for minidlna is 172.17.0.1:8200, whereas the Subsonic path is correctly configured at 192.168.0.10:4040. Do you know of any way to change this parameter in Minidlna?

Thank you again for your insight. If not, I can post a bug report. I noticed this post seemed similar: viewtopic.php?f=19&p=41692

Tom

There may be a configuration file somewhere that has the IP address hard coded. I would look for that and see if you can change it.

Really odd as I have never seen this sort of behavior in the past.

Figured it out. Had installed Mediatomb and my clients were unable to see this either. I should mention that I was initially having some success with Subsonic, but not minidlna. Then this morning Subsonic stopped working, and the path in MediaMonkey was shown as 127.0.0.1.

In searching for an answer came across this link: https://ubuntuforums.org/showthread.php?t=2379655

When I used ifconfig on my server found out that docker0 was set up for an IP 172.17.0.1, lo was set to IP 127.0.0.1, and that enp2s0 was the configuration set to my HDA (192.168.1.10). Went into the minidlna.conf file and changed the network interface from docker0 to enp2s0 and voila!

Seems to be working...

Should also mention I restarted my router, HDA, and PC.

Forgot about docker. I removed it from my HDA.

Glad you sorted it out.

Marking as resolved.