Plugin Update breaks GUI support

Status
Not open for further replies.
Joshua Parker Ruehlig

Joshua Parker Ruehlig

Hall of Famer
Joined
Dec 5, 2011
Messages
5,949
InQuize said:
strange, but freenas does't know it has plex :D
Code:
[root@NAS ~]# jls
JID IP Address Hostname Path
6 - virtualbox /mnt/triplet/jails/virtualbox

Plus

Uncheking DHCP helps, I'm able to uncheck VIMAGE, BUT when I save jail settings and go back to check it, nothing actually applied, DHCP and VIMAGE still checked and from now on I am able to uncheck VIMAGE w/o doing so for DHCP.
Btw I think,your theory is already wrong for me, as I reinstalled plex jail, and attemped to start it immediately, w/o even assigning static IP
Click to expand...
when you disabled DHCP did you set an IP?
 
InQuize

InQuize

Explorer
Joined
May 9, 2015
Messages
81
Joshua Parker Ruehlig said:
when you disabled DHCP did you set an IP?
Click to expand...
Right, totally forgot I should, and it allowed me..
Edited IP, but after saving checkboxes revert back although mask and IP are still there and greyed. GUI is really messy right now.

70xOlyv.jpg
In previous post, by assigning IP I meant static DHCP mapping in pfSense
 
Last edited:
InQuize

InQuize

Explorer
Joined
May 9, 2015
Messages
81
Joshua Parker Ruehlig said:
when you disabled DHCP did you set an IP?
Click to expand...
Managed to assing random IP via GUI, although DHCP checkbox still shows as marked. Now jail refuses to start:
Code:
May 11 07:32:12 NAS notifier: WARNING: can't open config file: /usr/local/openssl/openssl.cnf
May 11 07:32:12 NAS notifier: Performing sanity check on nginx configuration:
May 11 07:32:12 NAS notifier: nginx: the configuration file /usr/local/etc/nginx/nginx.conf syntax is ok
May 11 07:32:12 NAS notifier: nginx: configuration file /usr/local/etc/nginx/nginx.conf test is successful

feels like I'm doing real bad thing under the hood by pressing any button in UI
 
Last edited:
Joshua Parker Ruehlig

Joshua Parker Ruehlig

Hall of Famer
Joined
Dec 5, 2011
Messages
5,949
InQuize said:
Managed to assing random IP via GUI, although DHCP checkbox still shows as marked. Now jail refuses to start:
Code:
May 11 07:32:12 NAS notifier: WARNING: can't open config file: /usr/local/openssl/openssl.cnf
May 11 07:32:12 NAS notifier: Performing sanity check on nginx configuration:
May 11 07:32:12 NAS notifier: nginx: the configuration file /usr/local/etc/nginx/nginx.conf syntax is ok
May 11 07:32:12 NAS notifier: nginx: configuration file /usr/local/etc/nginx/nginx.conf test is successful

feels like I'm doing real bad thing under the hood by pressing any button in UI
Click to expand...
those errors have nothing to do with the jail or the changes you made.
 
Joshua Parker Ruehlig

Joshua Parker Ruehlig

Hall of Famer
Joined
Dec 5, 2011
Messages
5,949
InQuize said:
Right, totally forgot I should, and it allowed me..
Edited IP, but after saving checkboxes revert back although mask and IP are still there and greyed. GUI is really messy right now.

70xOlyv.jpg
In previous post, by assigning IP I meant static DHCP mapping in pfSense
Click to expand...
Ahh, so the jail shouldn't get a different IP after updates. Got it.

Can you try installing a fresh jail again as usual, then showing the output of 'jls'
I have a feeling FreeNAS might not know the IP to talk to the plugin too (which is what is happening to me).

Sorry for the all random tests. It's tough to debug this over a forum, lol
 
Feuermandel

Feuermandel

Dabbler
Joined
May 7, 2015
Messages
11
Hi there,

I installed plex Plugin on my freenas again. Like themlast times, plex plugin does not show up in the left panel. The State is stopped in the plugin view. The Plex jail ist startet in the jail view.

Stopping the plex jail and reconfiguring the jails without vimage and dhcp does not change anything.

Sorry for that.
 
Joshua Parker Ruehlig

Joshua Parker Ruehlig

Hall of Famer
Joined
Dec 5, 2011
Messages
5,949
Feuermandel said:
I can offer a teamviewer session if we can synchronize our different timezones...
Click to expand...
maybe if we can't figure out your issue, though I haven't used team viewer before...

can you please show the output of jls?
 
Feuermandel

Feuermandel

Dabbler
Joined
May 7, 2015
Messages
11
JID IP Address Hostname Path
1 - Worker /mnt/data/jails/Worker
2 - emby_1 /mnt/data/jails/emby_1
7 - Streamer /mnt/data/jails/Streamer
10 - plexmediaserver_1 /mnt/data/jails/plexmediaserver_1
 
Joshua Parker Ruehlig

Joshua Parker Ruehlig

Hall of Famer
Joined
Dec 5, 2011
Messages
5,949
Feuermandel said:
JID IP Address Hostname Path
1 - Worker /mnt/data/jails/Worker
2 - emby_1 /mnt/data/jails/emby_1
7 - Streamer /mnt/data/jails/Streamer
10 - plexmediaserver_1 /mnt/data/jails/plexmediaserver_1
Click to expand...
no IPs might be the problem =\
Im trying to find a solution that works for everyone.

earlier when you disabled VIMAGE, did you also set an interface & IP for the jail?
 
Feuermandel

Feuermandel

Dabbler
Joined
May 7, 2015
Messages
11
no ip within the jls output.

but all jails have their own ip up and running.
Interface drop down is not selectable.

I did not mention this before. My NAS has two different network cards. attached to two different networks.
 
InQuize

InQuize

Explorer
Joined
May 9, 2015
Messages
81
Joshua Parker Ruehlig said:
Ahh, so the jail shouldn't get a different IP after updates. Got it.

Can you try installing a fresh jail again as usual, then showing the output of 'jls'
I have a feeling FreeNAS might not know the IP to talk to the plugin too (which is what is happening to me).
Click to expand...
Actually, I did earlier. After installing 2nd plex jail, 'jls' recogizes it, but then it dissapear after messing with jail settings (dhcp, vimage, etc). Or may also be after attemp to start the jail, I'm not sure, but belive that jails setting is the place to dig. If you need to know, I may recreate exact situation bit later..
 
InQuize

InQuize

Explorer
Joined
May 9, 2015
Messages
81
Removed all previous broken jails, made new one.
New Plex version 0.9.12.1.1079. Old one tested was 0.9.12.0.****
Now '-jls' is ok at all times. Google dns pings from jail as well.
Attempt to start plugin gives same error. After disabling DHCP, VIMAGE, assigning static ipv4 - GUI jails table says that IP changed, and it actually ping from Win, but GUI jail settings still show DHCP and VIMAGE enabled (so it's a Freenas stable release problem now?)

Code:
May 12 01:51:21 NAS warden: Building new Jail... Please wait...
May 12 01:51:21 NAS warden: zfs clone triplet/jails/.warden-template-pluginjail@clean triplet/jails/plexmediaserver_1
May 12 01:51:21 NAS warden: Success!
May 12 01:51:21 NAS warden: Jail created at /mnt/triplet/jails/plexmediaserver_1
May 12 01:51:22 NAS rtsold[1569]: <rtsock_input_ifannounce> interface epair2b removed
May 12 01:51:22 NAS epair2a: Ethernet address: 02:54:78:00:0c:0a
May 12 01:51:22 NAS epair2b: Ethernet address: 02:54:78:00:0d:0b
May 12 01:51:22 NAS kernel: epair2a: link state changed to UP
May 12 01:51:22 NAS kernel: epair2a: link state changed to UP
May 12 01:51:22 NAS kernel: epair2b: link state changed to UP
May 12 01:51:22 NAS kernel: epair2b: link state changed to UP
May 12 01:51:22 NAS kernel: epair2a: promiscuous mode enabled
May 12 01:51:22 NAS kernel: ng_ether_ifnet_arrival_event: can't re-name node epair2b
May 12 01:51:22 NAS kernel: ng_ether_ifnet_arrival_event: can't re-name node epair2b
May 12 01:51:42 NAS notifier: WARNING: can't open config file: /usr/local/openssl/openssl.cnf
May 12 01:51:42 NAS notifier: Performing sanity check on nginx configuration:
May 12 01:51:42 NAS notifier: nginx: the configuration file /usr/local/etc/nginx/nginx.conf syntax is ok
May 12 01:51:42 NAS notifier: nginx: configuration file /usr/local/etc/nginx/nginx.conf test is successful
May 12 01:51:44 NAS manage.py: [freeadmin.navtree:625] An error occurred while unserializing from https://10.0.0.4/plugins/plexmediaserver/1/_s/treemenu: No JSON object could be decoded
May 12 01:54:44 NAS manage.py: [common.pipesubr:59] Popen()ing: /sbin/zfs list -H -o name '/mnt/triplet/jails/.warden-template-pluginjail'
May 12 01:54:44 NAS manage.py: [common.pipesubr:59] Popen()ing: /sbin/zfs get -H origin '/mnt/triplet/jails/plexmediaserver_1'
May 12 01:54:44 NAS manage.py: [common.pipesubr:59] Popen()ing: /sbin/zfs get -H origin '/mnt/triplet/jails/virtualbox'
May 12 01:54:44 NAS manage.py: [common.pipesubr:59] Popen()ing: /sbin/zfs list -H -o name '/mnt/triplet/jails/.warden-template-pluginjail'
May 12 01:54:45 NAS manage.py: [common.pipesubr:59] Popen()ing: /sbin/zfs get -H origin '/mnt/triplet/jails/plexmediaserver_1'
May 12 01:54:45 NAS manage.py: [common.pipesubr:59] Popen()ing: /sbin/zfs get -H origin '/mnt/triplet/jails/virtualbox'
May 12 01:54:53 NAS manage.py: [common.pipesubr:59] Popen()ing: /sbin/zfs list -H -o name '/mnt/triplet/jails/.warden-template-pluginjail'
May 12 01:54:53 NAS manage.py: [common.pipesubr:59] Popen()ing: /sbin/zfs get -H origin '/mnt/triplet/jails/plexmediaserver_1'
May 12 01:54:53 NAS manage.py: [common.pipesubr:59] Popen()ing: /sbin/zfs get -H origin '/mnt/triplet/jails/virtualbox'
May 12 01:54:53 NAS manage.py: [common.pipesubr:59] Popen()ing: /sbin/zfs list -H -o name '/mnt/triplet/jails/.warden-template-pluginjail'
May 12 01:54:53 NAS manage.py: [common.pipesubr:59] Popen()ing: /sbin/zfs get -H origin '/mnt/triplet/jails/plexmediaserver_1'
May 12 01:54:54 NAS manage.py: [common.pipesubr:59] Popen()ing: /sbin/zfs get -H origin '/mnt/triplet/jails/virtualbox'
May 12 01:55:24 NAS manage.py: [common.pipesubr:59] Popen()ing: /sbin/zfs list -H -o name '/mnt/triplet/jails/.warden-template-pluginjail'
May 12 01:55:24 NAS manage.py: [common.pipesubr:59] Popen()ing: /sbin/zfs get -H origin '/mnt/triplet/jails/plexmediaserver_1'
May 12 01:55:24 NAS manage.py: [common.pipesubr:59] Popen()ing: /sbin/zfs get -H origin '/mnt/triplet/jails/virtualbox'
May 12 01:55:24 NAS manage.py: [common.pipesubr:59] Popen()ing: /sbin/zfs list -H -o name '/mnt/triplet/jails/.warden-template-pluginjail'
May 12 01:55:24 NAS manage.py: [common.pipesubr:59] Popen()ing: /sbin/zfs get -H origin '/mnt/triplet/jails/plexmediaserver_1'
May 12 01:55:24 NAS manage.py: [common.pipesubr:59] Popen()ing: /sbin/zfs get -H origin '/mnt/triplet/jails/virtualbox'
May 12 01:55:37 NAS kernel: arp: 10.0.0.4 moved from 02:54:78:00:0c:0a to 60:a4:4c:ea:24:66 on epair2b
May 12 01:55:43 NAS manage.py: [freeadmin.navtree:571] Couldn't retrieve https://10.0.0.4/plugins/plexmediaserver/1/_s/treemenu: timed out
May 12 01:56:15 NAS rtsold[1569]: <rtsock_input_ifannounce> interface epair2a removed
May 12 01:56:16 NAS kernel: epair2a: link state changed to DOWN
May 12 01:56:16 NAS kernel: epair2a: link state changed to DOWN
May 12 01:56:16 NAS kernel: epair2b: link state changed to DOWN
May 12 01:56:16 NAS kernel: epair2b: link state changed to DOWN
May 12 01:56:19 NAS kernel: ifa_del_loopback_route: deletion failed
May 12 01:56:19 NAS Freed UMA keg (udp_inpcb) was not empty (40 items).  Lost 4 pages of memory.
May 12 01:56:19 NAS Freed UMA keg (udpcb) was not empty (504 items).  Lost 3 pages of memory.
May 12 01:56:19 NAS Freed UMA keg (tcptw) was not empty (200 items).  Lost 4 pages of memory.
May 12 01:56:19 NAS Freed UMA keg (tcp_inpcb) was not empty (40 items).  Lost 4 pages of memory.
May 12 01:56:19 NAS Freed UMA keg (tcpcb) was not empty (20 items).  Lost 5 pages of memory.
May 12 01:56:19 NAS Freed UMA keg (ripcb) was not empty (20 items).  Lost 2 pages of memory.
May 12 01:56:19 NAS hhook_vnet_uninit: hhook_head type=1, id=1 cleanup required
May 12 01:56:19 NAS hhook_vnet_uninit: hhook_head type=1, id=0 cleanup required
May 12 01:56:19 NAS epair2a: Ethernet address: 02:35:67:00:0c:0a
May 12 01:56:19 NAS epair2b: Ethernet address: 02:35:67:00:0d:0b
May 12 01:56:19 NAS kernel: epair2a: link state changed to UP
May 12 01:56:19 NAS kernel: epair2a: link state changed to UP
May 12 01:56:19 NAS kernel: epair2b: link state changed to UP
May 12 01:56:19 NAS kernel: epair2b: link state changed to UP
May 12 01:56:19 NAS kernel: epair2a: promiscuous mode enabled
May 12 01:56:19 NAS rtsold[1569]: <rtsock_input_ifannounce> interface epair2b removed
May 12 01:56:19 NAS kernel: ng_ether_ifnet_arrival_event: can't re-name node epair2b
May 12 01:56:19 NAS kernel: ng_ether_ifnet_arrival_event: can't re-name node epair2b
May 12 01:56:27 NAS manage.py: [freeadmin.navtree:625] An error occurred while unserializing from https://10.0.0.4/plugins/plexmediaserver/1/_s/treemenu: No JSON object could be decoded
 
Last edited:
Joshua Parker Ruehlig

Joshua Parker Ruehlig

Hall of Famer
Joined
Dec 5, 2011
Messages
5,949
InQuize said:
Removed all previous broken jails, made new one.
New Plex version 0.9.12.1.1079. Old one tested was 0.9.12.0.****
Now '-jls' is ok at all times. Google dns pings from jail as well.
Attempt to start plugin gives same error. After disabling DHCP, VIMAGE, assigning static ipv4 - GUI jails table says that IP changed, and it actually ping from Win, but GUI jail settings still show DHCP and VIMAGE enabled (so it's a Freenas stable release problem now?)

Code:
May 12 01:51:21 NAS warden: Building new Jail... Please wait...
May 12 01:51:21 NAS warden: zfs clone triplet/jails/.warden-template-pluginjail@clean triplet/jails/plexmediaserver_1
May 12 01:51:21 NAS warden: Success!
May 12 01:51:21 NAS warden: Jail created at /mnt/triplet/jails/plexmediaserver_1
May 12 01:51:22 NAS rtsold[1569]: <rtsock_input_ifannounce> interface epair2b removed
May 12 01:51:22 NAS epair2a: Ethernet address: 02:54:78:00:0c:0a
May 12 01:51:22 NAS epair2b: Ethernet address: 02:54:78:00:0d:0b
May 12 01:51:22 NAS kernel: epair2a: link state changed to UP
May 12 01:51:22 NAS kernel: epair2a: link state changed to UP
May 12 01:51:22 NAS kernel: epair2b: link state changed to UP
May 12 01:51:22 NAS kernel: epair2b: link state changed to UP
May 12 01:51:22 NAS kernel: epair2a: promiscuous mode enabled
May 12 01:51:22 NAS kernel: ng_ether_ifnet_arrival_event: can't re-name node epair2b
May 12 01:51:22 NAS kernel: ng_ether_ifnet_arrival_event: can't re-name node epair2b
May 12 01:51:42 NAS notifier: WARNING: can't open config file: /usr/local/openssl/openssl.cnf
May 12 01:51:42 NAS notifier: Performing sanity check on nginx configuration:
May 12 01:51:42 NAS notifier: nginx: the configuration file /usr/local/etc/nginx/nginx.conf syntax is ok
May 12 01:51:42 NAS notifier: nginx: configuration file /usr/local/etc/nginx/nginx.conf test is successful
May 12 01:51:44 NAS manage.py: [freeadmin.navtree:625] An error occurred while unserializing from https://10.0.0.4/plugins/plexmediaserver/1/_s/treemenu: No JSON object could be decoded
May 12 01:54:44 NAS manage.py: [common.pipesubr:59] Popen()ing: /sbin/zfs list -H -o name '/mnt/triplet/jails/.warden-template-pluginjail'
May 12 01:54:44 NAS manage.py: [common.pipesubr:59] Popen()ing: /sbin/zfs get -H origin '/mnt/triplet/jails/plexmediaserver_1'
May 12 01:54:44 NAS manage.py: [common.pipesubr:59] Popen()ing: /sbin/zfs get -H origin '/mnt/triplet/jails/virtualbox'
May 12 01:54:44 NAS manage.py: [common.pipesubr:59] Popen()ing: /sbin/zfs list -H -o name '/mnt/triplet/jails/.warden-template-pluginjail'
May 12 01:54:45 NAS manage.py: [common.pipesubr:59] Popen()ing: /sbin/zfs get -H origin '/mnt/triplet/jails/plexmediaserver_1'
May 12 01:54:45 NAS manage.py: [common.pipesubr:59] Popen()ing: /sbin/zfs get -H origin '/mnt/triplet/jails/virtualbox'
May 12 01:54:53 NAS manage.py: [common.pipesubr:59] Popen()ing: /sbin/zfs list -H -o name '/mnt/triplet/jails/.warden-template-pluginjail'
May 12 01:54:53 NAS manage.py: [common.pipesubr:59] Popen()ing: /sbin/zfs get -H origin '/mnt/triplet/jails/plexmediaserver_1'
May 12 01:54:53 NAS manage.py: [common.pipesubr:59] Popen()ing: /sbin/zfs get -H origin '/mnt/triplet/jails/virtualbox'
May 12 01:54:53 NAS manage.py: [common.pipesubr:59] Popen()ing: /sbin/zfs list -H -o name '/mnt/triplet/jails/.warden-template-pluginjail'
May 12 01:54:53 NAS manage.py: [common.pipesubr:59] Popen()ing: /sbin/zfs get -H origin '/mnt/triplet/jails/plexmediaserver_1'
May 12 01:54:54 NAS manage.py: [common.pipesubr:59] Popen()ing: /sbin/zfs get -H origin '/mnt/triplet/jails/virtualbox'
May 12 01:55:24 NAS manage.py: [common.pipesubr:59] Popen()ing: /sbin/zfs list -H -o name '/mnt/triplet/jails/.warden-template-pluginjail'
May 12 01:55:24 NAS manage.py: [common.pipesubr:59] Popen()ing: /sbin/zfs get -H origin '/mnt/triplet/jails/plexmediaserver_1'
May 12 01:55:24 NAS manage.py: [common.pipesubr:59] Popen()ing: /sbin/zfs get -H origin '/mnt/triplet/jails/virtualbox'
May 12 01:55:24 NAS manage.py: [common.pipesubr:59] Popen()ing: /sbin/zfs list -H -o name '/mnt/triplet/jails/.warden-template-pluginjail'
May 12 01:55:24 NAS manage.py: [common.pipesubr:59] Popen()ing: /sbin/zfs get -H origin '/mnt/triplet/jails/plexmediaserver_1'
May 12 01:55:24 NAS manage.py: [common.pipesubr:59] Popen()ing: /sbin/zfs get -H origin '/mnt/triplet/jails/virtualbox'
May 12 01:55:37 NAS kernel: arp: 10.0.0.4 moved from 02:54:78:00:0c:0a to 60:a4:4c:ea:24:66 on epair2b
May 12 01:55:43 NAS manage.py: [freeadmin.navtree:571] Couldn't retrieve https://10.0.0.4/plugins/plexmediaserver/1/_s/treemenu: timed out
May 12 01:56:15 NAS rtsold[1569]: <rtsock_input_ifannounce> interface epair2a removed
May 12 01:56:16 NAS kernel: epair2a: link state changed to DOWN
May 12 01:56:16 NAS kernel: epair2a: link state changed to DOWN
May 12 01:56:16 NAS kernel: epair2b: link state changed to DOWN
May 12 01:56:16 NAS kernel: epair2b: link state changed to DOWN
May 12 01:56:19 NAS kernel: ifa_del_loopback_route: deletion failed
May 12 01:56:19 NAS Freed UMA keg (udp_inpcb) was not empty (40 items).  Lost 4 pages of memory.
May 12 01:56:19 NAS Freed UMA keg (udpcb) was not empty (504 items).  Lost 3 pages of memory.
May 12 01:56:19 NAS Freed UMA keg (tcptw) was not empty (200 items).  Lost 4 pages of memory.
May 12 01:56:19 NAS Freed UMA keg (tcp_inpcb) was not empty (40 items).  Lost 4 pages of memory.
May 12 01:56:19 NAS Freed UMA keg (tcpcb) was not empty (20 items).  Lost 5 pages of memory.
May 12 01:56:19 NAS Freed UMA keg (ripcb) was not empty (20 items).  Lost 2 pages of memory.
May 12 01:56:19 NAS hhook_vnet_uninit: hhook_head type=1, id=1 cleanup required
May 12 01:56:19 NAS hhook_vnet_uninit: hhook_head type=1, id=0 cleanup required
May 12 01:56:19 NAS epair2a: Ethernet address: 02:35:67:00:0c:0a
May 12 01:56:19 NAS epair2b: Ethernet address: 02:35:67:00:0d:0b
May 12 01:56:19 NAS kernel: epair2a: link state changed to UP
May 12 01:56:19 NAS kernel: epair2a: link state changed to UP
May 12 01:56:19 NAS kernel: epair2b: link state changed to UP
May 12 01:56:19 NAS kernel: epair2b: link state changed to UP
May 12 01:56:19 NAS kernel: epair2a: promiscuous mode enabled
May 12 01:56:19 NAS rtsold[1569]: <rtsock_input_ifannounce> interface epair2b removed
May 12 01:56:19 NAS kernel: ng_ether_ifnet_arrival_event: can't re-name node epair2b
May 12 01:56:19 NAS kernel: ng_ether_ifnet_arrival_event: can't re-name node epair2b
May 12 01:56:27 NAS manage.py: [freeadmin.navtree:625] An error occurred while unserializing from https://10.0.0.4/plugins/plexmediaserver/1/_s/treemenu: No JSON object could be decoded
Click to expand...
Maybe you should also set Jails > Configuration to disable DHCP by default for jails.
I noticed I had this setup, also anytime I create a new plugin jail I disable VIMAGE, set an interface, and restart the jail

I have a similar setup as you, which might be why I have to disable DHCP & VIMAGE. I have 2 interfaces, one is a lagg of 3 NICs and the other is a direct route to another server.
 
InQuize

InQuize

Explorer
Joined
May 9, 2015
Messages
81
Joshua Parker Ruehlig said:
Maybe you should also set Jails > Configuration to disable DHCP by default for jails.
I noticed I had this setup, also anytime I create a new plugin jail I disable VIMAGE, set an interface, and restart the jail
Click to expand...
Ok, I followed your lead, and finally managed FreeNAS to see jail IP (btw, that is not the case with virtualbox and it works just fine)
Code:
[root@NAS ~]# jls                                                                                                                 
   JID  IP Address      Hostname                      Path                                                                        
     6  -               virtualbox                    /mnt/triplet/jails/virtualbox                                               
    15  10.0.0.66       plexmediaserver_1             /mnt/triplet/jails/plexmediaserver_1

But when I start plugin, nothing happens..
I aslo killed the lagg, leaving only one working interface, using dhcp, and it had no affect too.
These two errors still persist somewhere in log:
Code:
May 12 16:08:58 NAS manage.py: [freeadmin.navtree:571] Couldn't retrieve https://10.0.0.116/plugins/plexmediaserver/1/_s/treemenu: timed out
May 12 16:09:16 NAS manage.py: [freeadmin.navtree:625] An error occurred while unserializing from https://10.0.0.116/plugins/plexmediaserver/1/_s/treemenu: No JSON object could be decoded
 
Last edited:
Joshua Parker Ruehlig

Joshua Parker Ruehlig

Hall of Famer
Joined
Dec 5, 2011
Messages
5,949
InQuize said:
Ok, I followed your lead, and finally managed FreeNAS to see jail IP (btw, that is not the case with virtualbox and it works just fine)
Code:
[root@NAS ~]# jls                                                                                                                
   JID  IP Address      Hostname                      Path                                                                       
     6  -               virtualbox                    /mnt/triplet/jails/virtualbox                                              
    15  10.0.0.66       plexmediaserver_1             /mnt/triplet/jails/plexmediaserver_1

But when I start plugin, nothing happens..
I aslo killed the lagg, leaving only one working interface, using dhcp, and it had no affect too.
These two errors still persist somewhere in log:
Code:
May 12 16:08:58 NAS manage.py: [freeadmin.navtree:571] Couldn't retrieve https://10.0.0.116/plugins/plexmediaserver/1/_s/treemenu: timed out
May 12 16:09:16 NAS manage.py: [freeadmin.navtree:625] An error occurred while unserializing from https://10.0.0.116/plugins/plexmediaserver/1/_s/treemenu: No JSON object could be decoded
Click to expand...
maybe, the issue is since freenas didn't know about the IP during creation, freenas didn't know to store it in it's database about the plugin. Maybe changing IPs for the jail would make freenas re-store the IP for the plugin middleware interface?

Sorry, this has been such a mess for people lately. It works well for me, but I just have DHCP disabled by default for all jails. Not sure if this actually would solve the issue for others, but this really should be working with the default configuration. =/
 
Feuermandel

Feuermandel

Dabbler
Joined
May 7, 2015
Messages
11
Joshua Parker Ruehlig said:
maybe, the issue is since freenas didn't know about the IP during creation, freenas didn't know to store it in it's database about the plugin. Maybe changing IPs for the jail would make freenas re-store the IP for the plugin middleware interface?
=/
Click to expand...

Hi there,

within my configuration, the IP-adresses are selected by FreeNAS. I defined a range (x.x.x.191-199) for jail IPs. These IP-Adresses are free in my network. So DHCP should not be the trap.

Additionally I changed the IP address of my plex jail. error message about missing JSON ojbect is still present :-(
 
Joshua Parker Ruehlig

Joshua Parker Ruehlig

Hall of Famer
Joined
Dec 5, 2011
Messages
5,949
Feuermandel said:
Hi there,

within my configuration, the IP-adresses are selected by FreeNAS. I defined a range (x.x.x.191-199) for jail IPs. These IP-Adresses are free in my network. So DHCP should not be the trap.

Additionally I changed the IP address of my plex jail. error message about missing JSON ojbect is still present :-(
Click to expand...
I'm out of ideas then. sounds like you've tried what you can to get this to work.

basically what is needed is the plugins control interface to be available at a certain IP:port and freenas to record this IP:port in it's database.

For freenas 10 I want to modify this so it networking isn't even an issue and everything is done though Unix file sockets.
 
V

Validar

Cadet
Joined
May 13, 2015
Messages
7
Hi, similar problems here. After the next update, I was unable to install emby or plex plugin, when I removed the broken plugins and delete all jail sets, I am successfully install transmission plugin. It is work fine, but then I could not install emby or plex.
 
Status
Not open for further replies.

Similar threads

Biggeek
  • Locked
[SOLVED] PlexServer upgrade fail
Replies
7
Views
6K
Joshua Parker Ruehlig
Joshua Parker Ruehlig
shawly
  • Locked
Plugins won't start with DHCP (No JSON object could be decoded)
Replies
1
Views
2K
NigelNoFriends
N
H
  • Locked
Plugins (Plex) no longer working
Replies
10
Views
3K
havok2022
H
B
  • Locked
Can't update Plex
Replies
2
Views
1K
dlavigne
D
J
  • Locked
Plex Plugin Stop/Update Issue
Replies
5
Views
1K
Jath
J
Top