There is something a bit odd about their server configuration or certificate I think. If I try to open the same URL above in the File Reader
node, then in my ‘normal’ copy of KNIME (i.e downloaded/installed from KNIME website, KNIME 3.7.2), it works OK:
But, if I try the same thing in KNIME 3.7.2 running from my SDK for node development and testing, the URL does not work in a File Reader
:
A bit more digging into the respective java jre folders in each case shows some differences. It may be worth taking a look in the \lib\security subfolder as follows:
cd C:\KNIME\plugins\org.knime.binary.jre.win32.x86_64_1.8.0.152-01\jre\lib\security
dir
In the case of my KNIME install where the file reader accesses the URL OK, the result is as follows:
12/12/2017 12:33 <DIR> .
12/12/2017 12:33 <DIR> ..
04/12/2017 14:39 4,054 blacklist
04/12/2017 14:38 1,253 blacklisted.certs
04/12/2017 14:39 115,314 cacerts
04/12/2017 14:38 2,466 java.policy
04/12/2017 14:39 38,397 java.security
04/12/2017 14:39 98 javaws.policy
04/12/2017 14:40 3,035 local_policy.jar
12/12/2017 12:33 <DIR> policy
04/12/2017 14:38 0 trusted.libraries
04/12/2017 14:40 3,023 US_export_policy.jar
9 File(s) 167,640 bytes
3 Dir(s) 40,361,308,160 bytes free
Whereas in the non-functional installation, the result is:
20/12/2016 17:58 <DIR> .
20/12/2016 17:58 <DIR> ..
23/11/2016 21:09 4,054 blacklist
23/11/2016 21:09 1,188 blacklisted.certs
30/11/2018 16:56 105,204 cacerts
23/11/2016 21:09 2,466 java.policy
23/11/2016 21:09 24,633 java.security
23/11/2016 21:09 98 javaws.policy
23/11/2016 21:09 3,035 local_policy.jar
23/11/2016 21:09 0 trusted.libraries
23/11/2016 21:09 3,023 US_export_policy.jar
9 File(s) 143,701 bytes
2 Dir(s) 40,343,908,352 bytes free
Assuming your install looks similar to or the same as the first result, above, then unless your web browser if configured to used a proxy server somehow and KNIME is not, then not sure what else to suggest. Probably worth talking to your IT department to check.
Good luck!
Steve