Can start plugin service but not minidnla

Status
Not open for further replies.

tabs

Dabbler
Joined
Oct 31, 2012
Messages
11
I have freenas 8.3 installed. I have installed the 8.3 Jail release and can turn on the plugin services although the ip I gave it can't be pinged and is not listed in my routers dhcp list.. I have also installed the minidnla plugin but cannot turn this on it just says "some error occured"

This is the listing

Nov 10 21:38:55 freenas notifier: Starting minidlna.
Nov 10 21:38:55 freenas notifier: [2012/11/10 21:38:55] minidlna.c:500: error: Media directory entry not understood! []
Nov 10 21:38:55 freenas notifier: Starting cron.
Nov 10 21:38:55 freenas notifier:
Nov 10 21:38:55 freenas notifier: Sat Nov 10 21:38:55 GMT 2012
Nov 10 21:38:57 freenas manage.py: [freeadmin.navtree:416] Couldn't retrieve http://192.168.1.4/plugins/minidlna/_s/treemenu: HTTP Error 502: Bad Gateway

I am running Freenas in a VM and 192.168.1.4 is the freenas ip which I can ping.

Any hlep or pointers to where I can look much appreciated:)
 

mctt

Dabbler
Joined
Jun 16, 2013
Messages
13
Hey. Thanks for the reply. I have tried and read everything I possibly could on this subject. Only thing I have not done is try on 9.x to see if that works.
I get the IP address unreachable error, a 502 Bad Gateway if I remember correctly and have even tried the admin in different browsers to avoid tw Firefox cache issue mentionedin another post.
Just can't seem to figure it out.

Now I have a microserver running with ZFS and 4x2TB HDDs I'm not going to switch to Ubuntu 10.04 but knowing I could just have PS3mediaserver running in seconds it's tough to justify the jail approach.
 

mctt

Dabbler
Joined
Jun 16, 2013
Messages
13
Hi Again, I wanted to share some success in figuring this out. What was missing from my configuration steps was looking at the tree on the left Services > Plugins > MiniDLNA.
Once that was configured it worked. It turns out I had missed that step.

A bit embarrassing to admit missing something so obvious in retrospect. I may say to do this in the youtube tutorials but as far as I read it was not in the wiki steps (a few images are missing anyhow).
I figured out what was wrong when I tried the Firefly plugin that has a message prompting you to do the extra step.

Not sure about the IP needing to be outside the hub range DHCP. I did restrict the router to 192.169.0.3 to 192.168.0.254 and then made the jail IP 192.168.0.2. But this was more to do with the Netgear Virgin Superhub tends to be a bit hit and miss with fixing IP addresses.

Thanks, hope this helps anyone gets stumped on this even if it's easy once you know how.
 
Status
Not open for further replies.
Top