Plugin Update breaks GUI support

cyberjock · May 18, 2015

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

That's something you'd have to go to the plex forums to answer.

mpfusion · May 19, 2015

@Joshua Parker Ruehlig: I can reproduce the issue now. It really seems to be related to HTTPS. A clean FreeNAS VM with default HTTP works. But switching to HTTPS and the errors appear and the plugin won't start. Maybe you can reproduce it as well.

Syncthing works:

only when HTTP is used
with VIMAGE enabled (=default)
no IP address is displayed in jls | grep syncthing
direct installation of recent version without installing 0.10.30 first

Joshua Parker Ruehlig · May 19, 2015

mpfusion said:
@Joshua Parker Ruehlig: I can reproduce the issue now. It really seems to be related to HTTPS. A clean FreeNAS VM with default HTTP works. But switching to HTTPS and the errors appear and the plugin won't start. Maybe you can reproduce it as well.

Syncthing works:

only when HTTP is used

with VIMAGE enabled (=default)

no IP address is displayed in jls | grep syncthing

direct installation of recent version without installing 0.10.30 first

thanks, looks like you got the issue isolated.
but.. some others experiencing problems have it with HTTP, so there may be another issue you and I aren't experiencing.

Joshua Parker Ruehlig · May 23, 2015

Olav figured out the issue and presented a fix https://bugs.freenas.org/issues/9706#change-47260

I'm updating all affected plugins so they work with HTTPS again. https://github.com/josh4trunks/freenas-plugins/commit/90d485148e0d0997fd473a1e5ba2473bdedbf4df

Not bumping the version number for btsync, syncthing, owncloud, plex, or emby. These update regularly enough so they'll get fixed on their own.

depasseg · Jun 4, 2015

Plex just announced a new update (0.9.12.3) which adds DigiCert SSL certificates to the media server. Given some of the https related issues above, I'm hesitant to try an upgrade. Has the OP confirmed that JPR's mentioned fix is working? Especially since the github link above is titled: "Don't verify SSL connections to FreeNAS". Which seems to negate what Plex just released. I may be wrong though.

Joshua Parker Ruehlig · Jun 4, 2015

depasseg said:
Plex just announced a new update (0.9.12.3) which adds DigiCert SSL certificates to the media server. Given some of the https related issues above, I'm hesitant to try an upgrade. Has the OP confirmed that JPR's mentioned fix is working? Especially since the github link above is titled: "Don't verify SSL connections to FreeNAS". Which seems to negate what Plex just released. I may be wrong though.

not sure what this Plex update does but it won't be affected by my change.

my change only relates to the connection between the plugin Python API and the freenas GUI. it doesn't touch the actually program at all.

as for being scared to update, you could always try installing a second instance of plex to test things first.

depasseg · Jun 4, 2015

Woo-hoo - testing looks good!

Code:

root@plexmediaserver_2:/ # fetch --no-verify-peer -o PMS_Updater.sh https://raw.githubusercontent.com/mstinaff/PMS_Updater/master/PMS_Updater.sh
PMS_Updater.sh                                100% of 8482  B  119 MBps 00m00s
root@plexmediaserver_2:/ # chmod 755 PMS_Updater.sh
root@plexmediaserver_2:/ # ./PMS_Updater.sh -u USERNAME -p PASSWORD -a

The bottom (3rd) server is the test PMS using SSL.

InQuize · Jun 4, 2015

depasseg said:

Thank you, sir.
Apparently Samsung Smart TV doesnt't support SSL yet. But web and android app work just fine.

depasseg · Aug 13, 2015

Just another datapoint. I just ran the following to update from 0.9.12.3 to 0.9.12.8 to take advantage of the new IOS client:

Code:

root@plexmediaserver_1:/ # fetch --no-verify-peer -o PMS_Updater.sh https://raw.githubusercontent.com/mstinaff/PMS_Updater/master/PMS_Updater.sh
root@plexmediaserver_1:/ # chmod 755 PMS_Updater.sh
root@plexmediaserver_1:/ # ./PMS_Updater.sh  -a

ovizii · Sep 16, 2015

@Joshua Parker Ruehlig : I'm having a problem that looks very similar to this https issue here with the emby plugin.

My logs are saying:

Code:

Sep 15 22:06:15 freenas manage.py: [freeadmin.navtree:573] Couldn't retrieve https://192.168.178.41/plugins/couchpotato/1/_s/treemenu: timed out
Sep 15 22:06:15 freenas manage.py: [freeadmin.navtree:573] Couldn't retrieve https://192.168.178.41/plugins/transmission/2/_s/treemenu: timed out
Sep 15 22:06:15 freenas manage.py: [freeadmin.navtree:573] Couldn't retrieve https://192.168.178.41/plugins/plexmediaserver/3/_s/treemenu: timed out
Sep 15 22:06:15 freenas manage.py: [freeadmin.navtree:573] Couldn't retrieve https://192.168.178.41/plugins/sickrage/4/_s/treemenu: timed out
Sep 15 22:06:15 freenas manage.py: [freeadmin.navtree:573] Couldn't retrieve https://192.168.178.41/plugins/syncthing/5/_s/treemenu: timed out
Sep 15 22:06:15 freenas manage.py: [freeadmin.navtree:573] Couldn't retrieve https://192.168.178.41/plugins/emby/6/_s/treemenu: timed out
Sep 15 22:08:30 freenas manage.py: [plugins.utils:92] Couldn't retrieve https://192.168.178.41/plugins/couchpotato/1/_s/status: <urlopen error [Errno 8] _ssl.c:510: EOF occurred in violation of protocol>

If you think its related, here is the full post: https://forums.freenas.org/index.php?threads/emby-plugin-seems-to-break-freennas-gui.38133/

webpilot · Nov 18, 2015

Does this inability to check for system updates or update the GUI related?

Nov 18 04:12:10 carrier update_check.py: [freenasOS.Configuration:567] Unable to load https://web.ixsystems.com/updates/ix_crl.pem: <urlopen error [Errno 8] _ssl.c:510: EOF occurred in violation of protocol>
Nov 18 04:12:10 carrier update_check.py: [freenasOS.Manifest:386] Could not get CRL file https://web.ixsystems.com/updates/ix_crl.pem

STREBLO · Apr 13, 2016

I seem to be having a similar issue. Not sure if same thing. Plugins are being buggy, just updated to 9.10.

Keep seeing stuff like this:

Code:

Apr 13 18:14:54 Lilan manage.py: [freeadmin.navtree:575] Couldn't retrieve http://192.168.0.142/plugins/couchpotato/9/_s/treemenu: timed out
Apr 13 18:14:54 Lilan manage.py: [freeadmin.navtree:629] An error occurred while unserializing from http://192.168.0.142/plugins/sabnzbd/10/_s/treemenu: No JSON object could be decoded
Apr 13 18:15:50 Lilan manage.py: [plugins.utils:91] Couldn't retrieve http://192.168.0.142/plugins/couchpotato/9/_s/status: No JSON object could be decoded

InQuize · Apr 13, 2016

STREBLO said:

https://forums.freenas.org/index.ph...e-vmware-interface-problem.42569/#post-278394

If I'm right, set static IPs on all jails, reboot, and it should work

Also, may be https://bugs.freenas.org/issues/14638

STREBLO · Apr 13, 2016

InQuize said:
https://forums.freenas.org/index.ph...e-vmware-interface-problem.42569/#post-278394

If I'm right, set static IPs on all jails, reboot, and it should work

Also, may be https://bugs.freenas.org/issues/14638

They are static already :S

InQuize · Apr 13, 2016

STREBLO said:
They are static already :S

Then check if Network -> Network Summary page of the GUI, the "Default route" configured right.

You are not using virtualization, right?

Anyway, I believe issue described in this particular thread is fixed prior to 9.10

STREBLO · Apr 13, 2016

InQuize said:
Then check if Network -> Network Summary page of the GUI, the "Default route" configured right.

You are not using virtualization, right?

Anyway, I believe issue described in this particular thread is fixed prior to 9.10

Nope. Looked similar thats all, thanks.

STREBLO · Apr 16, 2016

This problem seems to be occuring, or something similar. Couchpotato isnt appearing on the tree and im getting:

Code:

Apr 16 16:14:09 Lilan manage.py: [freeadmin.navtree:575] Couldn't retrieve http://192.168.0.142/plugins/couchpotato/4/_s/treemenu: timed out

but it appears to be functioning fine. Similar bug maybe?

AndrewWOz · Sep 10, 2016

Thought this was probably the best place to add my 2c. I've been using 9.3.1 since it came out without a problem, I am in the process of setting up a brand new N54L for my dad and thought I might as well go with 9.10

Unfortunately both the sabd and sonarr plugins suffered the same 'No JSON object could be decoded' error, the plugins would not autostart on boot and the GUI status for the plugins was incorrect (showing off even after clicking the button to turn them on, which actually worked). Dad needs a 'set and forget' solution so unfortunately it is back to 9.3.1 for me.

But I thought you'd like another datapoint from a brand new 9.10 install without the potential of confusion from a 9.3 upgrade.

Joshua Parker Ruehlig · Sep 10, 2016

AndrewWOz said:
Thought this was probably the best place to add my 2c. I've been using 9.3.1 since it came out without a problem, I am in the process of setting up a brand new N54L for my dad and thought I might as well go with 9.10

Unfortunately both the sabd and sonarr plugins suffered the same 'No JSON object could be decoded' error, the plugins would not autostart on boot and the GUI status for the plugins was incorrect (showing off even after clicking the button to turn them on, which actually worked). Dad needs a 'set and forget' solution so unfortunately it is back to 9.3.1 for me.

But I thought you'd like another datapoint from a brand new 9.10 install without the potential of confusion from a 9.3 upgrade.

Have you ever tried disabling VIMAGE for your jails? That fixes all jail networking problems for me.

LudoB · Dec 4, 2016

Thank you Joshua for sharing this tip! It worked for me! :)

Important Announcement for the TrueNAS Community.

Plugin Update breaks GUI support

Inactive Account

Contributor

Hall of Famer

Hall of Famer

FreeNAS Replicant

Hall of Famer

FreeNAS Replicant

Explorer

FreeNAS Replicant

Patron

Dabbler

Patron

Explorer

Patron

Explorer

Patron

Patron

Cadet

Hall of Famer

Dabbler

Similar threads