2017-11-21, 11:13
I just downloaded the exact same nightly build and installed it, expecting to get the same error (and then be able to say something like "Nightly builds break some times..."), but it all worked fine for me, so I honestly don't know.
The only difference is I'm using Windows 7, not 10. If 10 is the problem... That's a little above my pay grade.
The only suggestion I can make is to go into Settings/System/Logging and enable component-specific logging and specify "Verbose logging for the libcURL library" and then upload your debug log with that enabled (after refreshing the library of course).
That might give a little more insight into what the issue is beyond the "Failed: SSL connect error(35)".
The only difference is I'm using Windows 7, not 10. If 10 is the problem... That's a little above my pay grade.
The only suggestion I can make is to go into Settings/System/Logging and enable component-specific logging and specify "Verbose logging for the libcURL library" and then upload your debug log with that enabled (after refreshing the library of course).
That might give a little more insight into what the issue is beyond the "Failed: SSL connect error(35)".
