Plugin Update breaks GUI support

Joshua Parker Ruehlig · May 13, 2015

Feuermandel said:
Ok. As the plex jalis runs (more or less but without staring the plex server). How Do I manually start plex?

Thanx

Code:

sysrc plexmediaserver_enable=YES
service plexmediaserver start

Joshua Parker Ruehlig · May 13, 2015

Validar said:
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.

strange, so for you certain plugin work but others don't?
for the most part, the code that freenas interacts with for these plugins are identical.

Validar · May 13, 2015

Before update, I had installed emby and transmission plugins. All works fine, but after update Freenas, I wanted to try plex plugin. I deleted embi and tried to install plex. As a result, the same error as that of the author.
I tried to set back emby - no success, the same error. I deleted all the plugins and tried to install them again - no success, the same error. After that, I deleted all the plugins, all the jail sets, all the storage mounts, change ip range for jails and restart NAS. And after these operations, I was able to install transmission plugin - success, it works. But plugins emby and plex do not want to install.

mpfusion · May 14, 2015

There are a couple of threads at the moment regarding the plugin update issues. Feel free to point me to a better suited one. I'm also affected and will present some information just in case it helps debugging.

The syncthing plugin wonn't start any longer. When the button “OFF” is clicked it stays “OFF” instead of turning “ON”. And the error “https://10.0.10.15/plugins/syncthing/3/_s/treemenu: No JSON object could be decoded” shows up in the logs. The transmission plugin works, however.

Then I set up a new FreeNAS VM, configured the network and syncthing installed without issues. So it's not that easy to reproduce. On the new VM the “jls” output also doesn't show an IP address for syncthing. So that's apparently not required for it to work. I compared the processes running inside the jail and found that the syncthing daemon is not running on the updated machine, but it does run on the new VM.

updated system (fails):

Code:

# ps aux
USER   PID %CPU %MEM    VSZ   RSS TT  STAT STARTED    TIME COMMAND
root 74642  0.0  0.0  12080  1868 ??  SsJ   3:05PM 0:00.00 /usr/sbin/syslogd -s
root 74695  0.0  0.0  14184  1844 ??  IsJ   3:05PM 0:00.00 /usr/sbin/cron -s
root 76774  0.0  0.2 171972 54580 ??  IJ    3:06PM 0:04.02 /usr/pbi/syncthing-amd64/bin/python2.7 /usr/pbi/syncthing-amd64/control.py start 10.0.10.100 12348
root 86784  0.0  0.0  14540  2280  1  SJ    3:13PM 0:00.00 sh
root 86789  0.0  0.0  16296  1828  1  R+J   3:13PM 0:00.00 ps aux

new VM (working):

Code:

# ps aux
USER       PID %CPU %MEM    VSZ   RSS TT  STAT STARTED    TIME COMMAND
root      4023  0.0  0.0  12080  1868 ??  SsJ   6:13AM 0:00.01 /usr/sbin/syslogd -s
syncthing 4074  0.0  0.0  12088  1624 ??  IsJ   6:13AM 0:00.00 daemon: /usr/pbi/syncthing-amd64/bin/syncthing[4076] (daemon)
syncthing 4076  0.0  0.2  25124  9240 ??  SJ    6:13AM 0:00.05 /usr/pbi/syncthing-amd64/bin/syncthing -home=/var/db/syncthing -no-browser
root      4083  0.0  0.0  14184  1860 ??  SsJ   6:13AM 0:00.00 /usr/sbin/cron -s
syncthing 4197  0.0  0.5  35436 22188 ??  SJ    6:13AM 0:00.75 /usr/pbi/syncthing-amd64/bin/syncthing -home=/var/db/syncthing -no-browser
root      4325  0.0  0.7 129988 28300 ??  IJ    6:13AM 0:00.69 /usr/pbi/syncthing-amd64/bin/python2.7 /usr/pbi/syncthing-amd64/control.py start 10.0.10.100 12346
root      6346  0.0  0.1  14540  2336  0  SJ    6:15AM 0:00.01 sh
root      6486  0.0  0.0  16296  1840  0  R+J   6:15AM 0:00.00 ps aux

I use the default settings and static IPs for the jails on both systems. I also tried fiddling with VIMAGE, to no avail. The working system uses the same jail configuration as the non-working one.

Let me know if I shall provide more information or assist in further debugging.

System specs:
FreeNAS-9.3-STABLE-201505130355
32GiB RAM (main rig)
4GiB RAM (test VM)

InQuize · May 14, 2015

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

Any ETA?

StyxX · May 15, 2015

I have updated my Plex jail, and was unable to start it from the GUI with HTTPS enabled getting the
message "An error occurred while unserializing from https://10.0.1.3/plugins/plexmediaserver/12/_s/treemenu: No JSON object could be decoded"
The IP on the jail is static and VIMAGE enabled, same as my other jails. I tried reinstalling Plex, changing IP and disabling VIMAGE without much succes.
But after changing the protocol to HTTP+HTTPS and logging in with HTTP instead of HTTPS everything is apparently working working.
Not exactly a long term solution, but at least it's up and running again.
Let me know if i can provide more information or assist in any way.

System:
FreeNAS-9.3-STABLE-201505130355

InQuize · May 15, 2015

StyxX said:
I have updated my Plex jail, and was unable to start it from the GUI with HTTPS enabled getting the
message "An error occurred while unserializing from https://10.0.1.3/plugins/plexmediaserver/12/_s/treemenu: No JSON object could be decoded"
The IP on the jail is static and VIMAGE enabled, same as my other jails. I tried reinstalling Plex, changing IP and disabling VIMAGE without much succes.
But after changing the protocol to HTTP+HTTPS and logging in with HTTP instead of HTTPS everything is apparently working working.
Not exactly a long term solution, but at least it's up and running again.
Let me know if i can provide more information or assist in any way.

Confirming. Great job! Networking has zero deal with the problem..
Do you get any of these as well?

InQuize said:

Do you also had SSL certificate signed by imported CA? or just FreeNAS internal?

StyxX · May 15, 2015

I get the exact same notifications.

And using Self-signed FreeNAS certificate.

InQuize · May 15, 2015

Thanks for help, StyxX. Just in time

Joshua Parker Ruehlig · May 15, 2015

mpfusion said:
There are a couple of threads at the moment regarding the plugin update issues. Feel free to point me to a better suited one. I'm also affected and will present some information just in case it helps debugging.

The syncthing plugin wonn't start any longer. When the button “OFF” is clicked it stays “OFF” instead of turning “ON”. And the error “https://10.0.10.15/plugins/syncthing/3/_s/treemenu: No JSON object could be decoded” shows up in the logs. The transmission plugin works, however.

Then I set up a new FreeNAS VM, configured the network and syncthing installed without issues. So it's not that easy to reproduce. On the new VM the “jls” output also doesn't show an IP address for syncthing. So that's apparently not required for it to work. I compared the processes running inside the jail and found that the syncthing daemon is not running on the updated machine, but it does run on the new VM.

updated system (fails):

Code:
# ps aux USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND root 74642 0.0 0.0 12080 1868 ?? SsJ 3:05PM 0:00.00 /usr/sbin/syslogd -s root 74695 0.0 0.0 14184 1844 ?? IsJ 3:05PM 0:00.00 /usr/sbin/cron -s root 76774 0.0 0.2 171972 54580 ?? IJ 3:06PM 0:04.02 /usr/pbi/syncthing-amd64/bin/python2.7 /usr/pbi/syncthing-amd64/control.py start 10.0.10.100 12348 root 86784 0.0 0.0 14540 2280 1 SJ 3:13PM 0:00.00 sh root 86789 0.0 0.0 16296 1828 1 R+J 3:13PM 0:00.00 ps aux

new VM (working):

Code:
# ps aux USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND root 4023 0.0 0.0 12080 1868 ?? SsJ 6:13AM 0:00.01 /usr/sbin/syslogd -s syncthing 4074 0.0 0.0 12088 1624 ?? IsJ 6:13AM 0:00.00 daemon: /usr/pbi/syncthing-amd64/bin/syncthing[4076] (daemon) syncthing 4076 0.0 0.2 25124 9240 ?? SJ 6:13AM 0:00.05 /usr/pbi/syncthing-amd64/bin/syncthing -home=/var/db/syncthing -no-browser root 4083 0.0 0.0 14184 1860 ?? SsJ 6:13AM 0:00.00 /usr/sbin/cron -s syncthing 4197 0.0 0.5 35436 22188 ?? SJ 6:13AM 0:00.75 /usr/pbi/syncthing-amd64/bin/syncthing -home=/var/db/syncthing -no-browser root 4325 0.0 0.7 129988 28300 ?? IJ 6:13AM 0:00.69 /usr/pbi/syncthing-amd64/bin/python2.7 /usr/pbi/syncthing-amd64/control.py start 10.0.10.100 12346 root 6346 0.0 0.1 14540 2336 0 SJ 6:15AM 0:00.01 sh root 6486 0.0 0.0 16296 1840 0 R+J 6:15AM 0:00.00 ps aux

I use the default settings and static IPs for the jails on both systems. I also tried fiddling with VIMAGE, to no avail. The working system uses the same jail configuration as the non-working one.

Let me know if I shall provide more information or assist in further debugging.

System specs:
FreeNAS-9.3-STABLE-201505130355
32GiB RAM (main rig)
4GiB RAM (test VM)

Thanks for sharing your results. It seems like this is caused by a recent FreeNAS update. And possibly only affects certain network configurations.

Joshua Parker Ruehlig · May 15, 2015

InQuize said:
Any ETA?

Well what I am planning to do probably wouldn't be implemented till FreeNAS10, so end of 2015...
But, I'm hoping we can find a mitigation for now.

Joshua Parker Ruehlig · May 15, 2015

InQuize said:
Confirming. Great job! Networking has zero deal with the problem..
Do you get any of these as well?

Do you also had SSL certificate signed by imported CA? or just FreeNAS internal?

Those logs from NGINX are normal. Just means NGINX was restarted.

Joshua Parker Ruehlig · May 15, 2015

StyxX said:
I have updated my Plex jail, and was unable to start it from the GUI with HTTPS enabled getting the
message "An error occurred while unserializing from https://10.0.1.3/plugins/plexmediaserver/12/_s/treemenu: No JSON object could be decoded"
The IP on the jail is static and VIMAGE enabled, same as my other jails. I tried reinstalling Plex, changing IP and disabling VIMAGE without much succes.
But after changing the protocol to HTTP+HTTPS and logging in with HTTP instead of HTTPS everything is apparently working working.
Not exactly a long term solution, but at least it's up and running again.
Let me know if i can provide more information or assist in any way.

System:
FreeNAS-9.3-STABLE-201505130355

Ahh great! so this might have to do with HTTPS in the FreeNAS GUI?

I don't use HTTPS (have my freenas on its own isolated subnet) so I haven't experienced this yet.

I'll try confirming your findings.

Feuermandel · May 15, 2015

StyxX said:
But after changing the protocol to HTTP+HTTPS and logging in with HTTP instead of HTTPS everything is apparently working.

Confirmed. Plex is displayed even after changing to http. Emby needs to be installed again, but them working as well.

When using the HTTPS port, both plugins (emby and flex) are throwing JSON errors.

Thank you very much.

Validar · May 16, 2015

Yep, worked. Thank you for research.

avalon60 · May 17, 2015

I installed the Plexmediaserver onto my FreeNAS 9.3 stable box yesterday, and even though it is running, and shows up on my android tablet, there are 2 problems.
The 1st one is that this 192.168.0.2/32400 in my web browser gives this:
Unable to connect

Firefox can't establish a connection to the server at 192.168.0.2:32400.
I also get the same error message when I try localhost/32400

Now I don't know what version of plexmedia server I have as I just installed the plugin which was available onto my FreeNAS box

Due to the error message above , would plex be the updated version to which this thread is about.

The 2nd problem is that even though plexmediaserver_1 shows up on my android tablet, there are no media files showing or available, even though I have added the media folder to the plexmediaserver, and are showing up in windows explorer.

When I open or select the plexmediaserver on my tablet, I get this message: 'Open the Navigation Menu and select a library to view content on this server'.

avalon60 · May 17, 2015

I have just tried pinging my router's IP address from with in the plexmediaserver_1

root@plexmediaserver_1:/ # ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1): 56 data bytes

It just hangs at that, so I guess that plexmediaserver cannot see my router.

But pinging the same from outside of the plugin there is no problem.

Also pinging the plexmediaserver from windows is no problem:

C:\Windows\System32>ping 192.168.0.2
Pinging 192.168.0.2 with 32 bytes of data:
Reply from 192.168.0.2: bytes=32 time<1ms TTL=64
Reply from 192.168.0.2: bytes=32 time=4ms TTL=255
Reply from 192.168.0.2: bytes=32 time=4ms TTL=255
Reply from 192.168.0.2: bytes=32 time=4ms TTL=255

Joshua Parker Ruehlig · May 17, 2015

avalon60 said:
I have just tried pinging my router's IP address from with in the plexmediaserver_1

root@plexmediaserver_1:/ # ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1): 56 data bytes

It just hangs at that, so I guess that plexmediaserver cannot see my router.

But pinging the same from outside of the plugin there is no problem.

Also pinging the plexmediaserver from windows is no problem:

C:\Windows\System32>ping 192.168.0.2
Pinging 192.168.0.2 with 32 bytes of data:
Reply from 192.168.0.2: bytes=32 time<1ms TTL=64
Reply from 192.168.0.2: bytes=32 time=4ms TTL=255
Reply from 192.168.0.2: bytes=32 time=4ms TTL=255
Reply from 192.168.0.2: bytes=32 time=4ms TTL=255

There is something wrong with your plex jail's network setup. You need it to be able to connect to your router.
You third test (pinging the jails IP) doesn't show anything except that the 192.168.0.2 IP was created by freenas but the freenas host will gladly bind to it if your jail isn't using it (which is shown from your first test).

avalon60 · May 17, 2015

I don't know what I did but after changing the PMS IP address to 192.168.0.6, and then setup port forwarding in my routers config page, I can now access the plexmediaserver_1 in a web browser: http://192.168.0.6:32400/web/index.html.

The only thing now is that the PMS app on my android tablet cannot see the media folder or files, which can be seen in a web browser.

avalon60 · May 17, 2015

Ok, I think I may have cracked it now.
I selected the plexmediaserver_1 on my tablet, and then selected the music menu, then the relevant folder, and viola! The music files are now being added from my FreeNAS box to the plexmediaserver_1.

I have no idea why it didn't happen before, but I got there in the end.

The only thing now I have noticed is that when I select a music cd sometimes nit says there is no media, but when I check there is media.

For example: 10cc greatest hits/ CD1 and CD2; plexmediaservers deems there are no mp3 files in each folder, but there is.

Important Announcement for the TrueNAS Community.

Plugin Update breaks GUI support

Hall of Famer

Hall of Famer

Cadet

Contributor

Explorer

Cadet

Explorer

Cadet

Explorer

Hall of Famer

Hall of Famer

Hall of Famer

Hall of Famer

Dabbler

Cadet

Guru

Guru

Hall of Famer

Guru

Guru

Similar threads