Error with SSL tasks

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
9 years ago
Hi,

I have been experiencing an issue with the Keep Alive Scheduled task with the following error:

Error while running the 'Keep alive' schedule task. The request was aborted: Could not create SSL/TLS secure channel.


This is happening every 5 minutes (whenever the job runs).

I think the issue is here that the Scheduled Task is trying to use SSL3 which isn't supported by the Server (due to the POODLE exploit).

Has anyone else experienced this and are there any steps to resolve? I haven't seen a setting in the store to define which SSL Protocol to use.

This has cropped up as I am experiencing issues with SSL when calling a 3rd party API with the same error and I have narrowed this down to the use of SSL3 rather than TLS1.

To get around this I have tried setting System.Net.ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls; but this doesn't seem to work.

Edit: Using nopCommerce 3.4
9 years ago
Has no one else had this?
9 years ago
Hi AJ

Yes we are having the same issues with our sites, not quite sure how to resolve it though.

Please let me know if you find a solution.
9 years ago
Hi AJ

I have been doing some digging around to see if I could find the issue, and I came across this on Stackoverflow:

http://stackoverflow.com/questions/13413214/ssl-webservice-could-not-create-ssl-tls-secure-channel

It appears to be the following issue: IIS does not send all of the intermediate certificates during SSL handshake.

http://forums.iis.net/t/1211005.aspx?SSL+Problem+IIS7+does+not+send+all+of+the+intermediate+certificates+during+SSL+handshake
9 years ago
Ah right.

I am moving the app to a Windows 2012 Server. Will report back to see if a newer version of IIS resolves this issue...

Thanks
9 years ago
Moving to Windows Server 2012 seems to have fixed the issue.

Still not 100% on the explanation as it has worked before on this server, but it seems there could be an issue with the version of IIS in WS 2008 and SSL causing the issue.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.