Failed Plugin Download -- MAVEN.ORG enforcing https

[dexterdom]

Hello all,
I'm doing a new install of v9 32bit on a Windows 10 x64 machine. I was originally getting download errors installing plugins, but that was (mostly) fixed by upgrading to Java 8.
There are, however, still some plugins that I cannot install due to failed downloads, and they all seem to be hosted on maven.org. For example, this is what I get when trying to install Batch Metadata Tools:
plugin-install-error-maven.org.JPG
When I point a browser to the specified URL (http://central.maven.org/maven2/comm...ons-io-2.5.jar) I get the following:

501 HTTPS Required. 
Use https://repo1.maven.org/maven2/
More information at https://links.sonatype.com/central/501-https-required

From the last URL above, it looks like maven.org is now enforcing https as of Jan 15. Can this be fixed in Sage, or any advice on how I can manually install the plugins if not?

[egeller]

Originally Posted by dexterdom

Hello all,

When I point a browser to the specified URL (http://central.maven.org/maven2/comm...ons-io-2.5.jar)

This is almost funny.

I took the URL, above, changed http to https and get the following error in Firefox when I tried to go to it:

"Unable to communicate securely with peer: requested domain name does not match the server’s certificate."

So, they require https, but do not set their server up correctly.

I came to say that you might try the following:

1. copy the plugin definition whichever xml file it is in to a file named SageTVPluginsDev.xml
2. change http to https,
3. then restart SageTV

and it might work. Not sure what happens with the security risk error. The plugin definition will be in either SageTVPlugins.xml or SageTVPluginsV9.xml.

[wayner]

This raises a good question about the long term sustainability of SageTV.

Are all of the plugins available on web sites that are going to be around for the long term?

I don't know exactly how this works, but if they aren't already, maybe all of the plugins should be stored in one central location that will be kept alive as long as you can still download SageTV.

[jpwegas]

Back when the Google thing first happened someone created a script to download all the plugins for backup. Then you could set the plugin URL or whatever to your own copy (or someone else's). Between devs leaving and issues like this it may time to revisit that.

--John

[dexterdom]

Originally Posted by egeller

This is almost funny.

I took the URL, above, changed http to https and get the following error in Firefox when I tried to go to it:

"Unable to communicate securely with peer: requested domain name does not match the server’s certificate."

So, they require https, but do not set their server up correctly.

I came to say that you might try the following:

1. copy the plugin definition whichever xml file it is in to a file named SageTVPluginsDev.xml
2. change http to https,
3. then restart SageTV

and it might work. Not sure what happens with the security risk error. The plugin definition will be in either SageTVPlugins.xml or SageTVPluginsV9.xml.

I got it to work but I needed to jump through a couple of hoops. Thanks for pointing me in the right direction!

0) I was able to manually download the jar file without error when I pointed my browser to https://repo1.maven.org (it was in the original error message from maven.org)
1) I found the plugin definitions in SageTVPluginsV9.xml
2) per your note I copied this to SageTVPluginsDev.xml and search/repaced http://central.maven to https://repo1.maven -- sage didn't appear to be acknowledging this file, plugins were still pointing to the old location
3) tried to edit SageTVPluginsV9.xml directly but when restarting Sage that file would get overwritten with a previous copy
4) based on this thread, I set SageTVPluginsV9.xml to read-only, my changes were not overwritten when I restarted Sage and the plugin installed successfully!
https://forums.sagetv.com/forums/sho...07&postcount=5

This is obviously a hack that will likely break when I update sage, but for now I have it documented in case I need to do this again in the future.
Hopefully, someone who knows what they're doing will implement a more permanent fix

[JREkiwi]

The V9 repository has been changed for all the Maven links in all it's plugins

John

[dexterdom]

Awesome! As a test, I removed my modified SageTVPluginsV9.xml file, restarted sage and saw that a new SageTVPluginsV9.xml was created with the corrected maven URLs - brilliant! Now I'll check my clients as well

This is the most attention I've paid to my SageTV config in about 5 years

[tvmaster2]

Originally Posted by JREkiwi

The V9 repository has been changed for all the Maven links in all it's plugins

John

Sorry, I’m a bit thick, lol. so all the plugins are indeed available somewhere then?