Posted by
Deborah Schmidt on
Sep 09, 2019; 9:10pm
URL: http://imagej.273.s1.nabble.com/Java-https-update-sites-tp5022427p5022432.html
Hi Till,
sorry you are having issues with the HTTPS switch. I am trying to get a better grip of the problem with your own update site to see if we can fix anything.
With a fresh install containing the JRE there should be no such warning. Is this happening in your case? What Java version is displayed in the status bar when you click on it?
The changes made to the updater should not affect sites hosted on other servers. We only check if the Let's Encrypt certificate of imagej.net is supported by the local Java installation and if it is not, we throw this warning. Meaning you should still be able to host an update site on a different server and serve it to older Fijis if the certificate is also supported by older Java versions.
I ran tests on your update site
https://pilip.lnx.warwick.ac.uk/quimp-update-site/ with Java 1.8.0_05 and get the same SSLHandshakeException as with
https://imagej.net, that's why you cannot add the HTTPS address to an older Fiji installation.
So did this HTTPS URL ever work with an older Fiji / JRE?
Best,
Deborah
--
Deborah Schmidt, Jug-Lab
Center for Systems Biology Dresden
MPI of Molecular Cell Biology and Genetics
Pfotenhauerstr. 108, 01307 Dresden, Germany
----- Original Message -----
From: "Till Bretschneider" <
[hidden email]>
To:
[hidden email]
Sent: Monday, September 9, 2019 2:46:26 PM
Subject: Java https update sites
Since updating Fiji, and also with a current fresh install under Mac OS, the updater gives a warning:
"Your Java might be too old to handle updates via HTTPS"
Unfortunately our own QuimP site is affected:
https://pilip.lnx.warwick.ac.uk/quimp-update-site/it still works by manually overriding it with http, but I was wondering what the underlying problem was.
Is there a different JRE supplied?
Best wishes,
Till
--
ImageJ mailing list:
http://imagej.nih.gov/ij/list.html--
ImageJ mailing list:
http://imagej.nih.gov/ij/list.html