Plugin server issue?

[photon]

I've setup a new client and went to plugins to choose my desired Full UI.

I'm getting this error when I choose SageMC:

Plugin Install Progress: Done - FAILED - Resource Download
http://bintray.com/jrekiwi/SageTV/do...file_path=Sage
MC%2Fsagemc-stv-7011.zip

To rule out a client issue I uninstalled this plugin from a different working client. Tried to reinstall and got the same error message. Now I have two nonworking clients.

I hope this can be fixed.

[JREkiwi]

Bintray have made a change to redirect HTTP requests to HTTPS which is not supported on all Java versions.

I'll change the plugin repository to the HTTPS address

https://bintray.com/jrekiwi/SageTV/d...stv-7.0.11.zip

John

[photon]

Thank you. I look forward to the server side fix. This client is on Android. I don't know how to manually install a plugin so I'm not sure how to use your linked zip file. My sage server is on v9.1.5.683.32 bit with 32 bit java version 7 update 79. It won't accept more than 4 GB of RAM so for java heap reasons I'm frozen on this version until I move to the new hardware I've had for a long time now.

I haven't tried to move to version 9 64 bit on the new hardware yet. Mostly it's the time commitment because I would be trying to replicate key Windows Home server features on Windows 10 desktop OS. As far as I know MS hasn't added those features into some current OS. The drive pool and photo hosting have long been available 3rd party so it's the rest of the features that are a challenge. I don't know how to build a remote access website on Windows 10 desktop. Or I could kick the can down the road by just installing a new copy of unsupported WHS 2011 on the new hardware and be done in a few hours.

[JREkiwi]

You need to be running Java 8 to be able to download plugins using HTTPS. If you upgrade your JAVA you should be OK.

John

[photon]

That solved it. I installed Java 8. All fixed. SageMC UI installed on all clients successfully.

Thank you!

[egeller]

Originally Posted by JREkiwi

You need to be running Java 8 to be able to download plugins using HTTPS. If you upgrade your JAVA you should be OK.

John

Uh.... I think we have an issue, and I cannot believe I am the only one. I am running the SageTV Docker on Unraid. Sage reports my Java version is:1.8.0_161.

I have 3 plugins that now have the JVM=8+ dependency listed. They are External Apps, Phoenix Fanart for SageTV, and Upcoming Movies 2.

For all three, I now see a refusal of the plugins to update, Compatible=No, Reason=Java Version 8+.

I am going to start up my development instance of Sage on a Windows Machine to see if the behavior is different. In the meantime, I wonder if anybody is seeing the same thing or has any ideas on a possible fix.

[photon]

Originally Posted by egeller

Uh.... I think we have an issue, and I cannot believe I am the only one. I am running the SageTV Docker on Unraid. Sage reports my Java version is:1.8.0_161.

I have 3 plugins that now have the JVM=8+ dependency listed. They are External Apps, Phoenix Fanart for SageTV, and Upcoming Movies 2.

For all three, I now see a refusal of the plugins to update, Compatible=No, Reason=Java Version 8+.

I am going to start up my development instance of Sage on a Windows Machine to see if the behavior is different. In the meantime, I wonder if anybody is seeing the same thing or has any ideas on a possible fix.

Not sure if this helps but I just installed Java 8 and sage reports my new java version as 1.8.0_231. Going by the second digit in both cases I think you have Java 8 installed.

[egeller]

Originally Posted by photon

Not sure if this helps but I just installed Java 8 and sage reports my new java version as 1.8.0_231. Going by the second digit in both cases I think you have Java 8 installed.

It does help, sort of. With Unraid, Java is part of the Docker. It's a combined-all-in-one package. I understand I am running Java 8.

I think the problem may be the way the Java version is referred to in the Plugin XML. It says <minversion>8</minversion>. I suspect it is supposed to say "1.8" and not "8".

I see other plugins, in the XML, dependent on Java 6 and 7. They all say "1.6" and "1.7" respectively.

Unfortunately, I do not know how to change the plugin XML on the fly, as it seems Sage downloads the XML on startup.

Therefore, I think it needs to be fixed at the source.

[BobPhoenix]

Originally Posted by egeller

I do not know how to change the plugin XML on the fly, as it seems Sage downloads the XML on startup.

Copy the XML entry from the SageTVPlugins.xml to a file named SageTVPluginsDev.xml in the SageTV directory but change the plugin version to a higher number. Then also change any settings you feel need to be changed. Then select the new entry when you restart the server.

I think that should work to at least change the settings of an existing plugin.

[JREkiwi]

Originally Posted by egeller

I have 3 plugins that now have the JVM=8+ dependency listed. They are External Apps, Phoenix Fanart for SageTV, and Upcoming Movies 2

I'll fix the repository

John

Fixed.

[waynedunham]

Originally Posted by JREkiwi

You need to be running Java 8 to be able to download plugins using HTTPS. If you upgrade your JAVA you should be OK.

John

I'm calling on my addled brain, but back when Java 8 came out didn't it break multiple plugins unless you downgraded to Java 7?
I don't recall the list of plugins it did break (was there ever a "list"), but seem to recall that at least one of them noted was critical to me so I've never gone past Java 7 on my SageTV machines.

Does anyone recall what plugins it broke, and has that been addressed?

Within the last couple weeks several of my plugins have been "updated" that are either JREWiki plugins, or ones he gets co-credit for, to change the address to HTTPS from HTTP. Needless to say none of these will update since I'm on Java 7. CMT, Encoder names, and Comskip Playback plugins plus the Nielm_sageIMDB library file are the ones on my systems.

I get failed messages when I try to download any of these updates. Again, not surprising since Java 7 can't do HTTPS. (really?? wow!)

It might not have been a big deal since the link to the file is really the only thing changed apparently, but now at the very least my IMDB functions aren't working.

PLEH, PLEH!! (a dyslexic cry for HELP)

[JREkiwi]

The only changes on all those plugins was just the download path as BinTray are no longer supporting HTTP
The IMDB issue is not resolved yet as IMDB have once again changed to a "New Interface"

You could try setting a new System Environment Variable, instructions here

_JAVA_OPTIONS
with a value of
-Dhttps.protocols=TLSv1.1,TLSv1.2

that may work, although some of the plugins have a pre-req of Java 1.8

John

[waynedunham]

Originally Posted by JREkiwi

The only changes on all those plugins was just the download path as BinTray are no longer supporting HTTP
The IMDB issue is not resolved yet as IMDB have once again changed to a "New Interface"

You could try setting a new System Environment Variable, instructions here

_JAVA_OPTIONS
with a value of
-Dhttps.protocols=TLSv1.1,TLSv1.2

that may work, although some of the plugins have a pre-req of Java 1.8

John

Well this morning I shut down SageTV on both of my servers and uninstalled Java 7 and installed Java 8 (32bit on both machines and 64bit on one of the machines running Win8.1 64 bit). So far, so good. (fingers crossed)

Fired them up and both booted into SageTV service just fine. I updated the plugins that required Java 8 (3 plugins, 1 library). Restarted SageTV and so far everything seems to be working fine. IMDB is back, thanks to that getting updated again for the new IMDB interface. No other plugins have complained about Java so far.

[JREkiwi]

I think the only plugin that had a problem with JAVA 8 was the Kodi one

John

[waynedunham]

Found another one which is pretty important to my needs (travel and controlling SageTV from remote).

SageTV Mobile Web Interface (2.1.0 which is the newest one in the SageTV V9 plugin repository). The main parts work fine, but any time you try to use either of the search menu items (search airings, search recordings) you get an error which never happened under Java 7 with the same plugin. Plus you also get a different error when trying to use either of the listings menu items (listings, HD listings).

Those are the only ones I've seen so far and luckily using the old "non" mobile web interface will allow you to be able to preform these functions.

I'm pretty sure that this was one of the items with an issue back when Java 8 first came out and people started having problems. It was also most likely one of the reasons I never installed Java 8 back then because Mobile Web Interface was pretty important to me.

Looking at the plugin details for Mobile Web Interface I see that it has an older "last Updated" date than the standard web interface plugin. I also checked the dependencies and I have the latest versions of all of those installed in the plugin library as well.