Scheduling.KeepAlive Fail - Remote Certificate is Invalid
I've just updated my load-balanced site (Umb 7.2.8) to use SSL and am now getting the following error in my log (on the second node) every 5 minutes:
[P7512/T125/D12] Failed (at "https://www.MySite.com:443/umbraco").
System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. ---> System.Security.Authentication.AuthenticationException: The remote certificate is invalid according to the validation procedure.
This did not happen on my test site, and I believe it has something to do with my production bindings and certs. I"m using two certifications, one each for a primary domain binding and another for subdomain. Could this be an issue for Umbraco?
My bindings look similar to:
MySite.com - SSL: MySite.com
MySite.Domain.com - SSL: *.Domain.com
MySite1.Domain.com - SSL: *.Domain.com (used for Umb backoffice)
I actually don't even remember having this issue. If it's what I think it is, then the solution was to turn on Require Server Name Indication for my site bindings. To do so:
In IIS Manager, click on your site and go to the Bindings edit window
Double-click a binding to edit and check the Require Server Name Indication checkbox
Scheduling.KeepAlive Fail - Remote Certificate is Invalid
I've just updated my load-balanced site (Umb 7.2.8) to use SSL and am now getting the following error in my log (on the second node) every 5 minutes:
[P7512/T125/D12] Failed (at "https://www.MySite.com:443/umbraco"). System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. ---> System.Security.Authentication.AuthenticationException: The remote certificate is invalid according to the validation procedure.This did not happen on my test site, and I believe it has something to do with my production bindings and certs. I"m using two certifications, one each for a primary domain binding and another for subdomain. Could this be an issue for Umbraco?
My bindings look similar to:
May i know if you solved this issue?
I actually don't even remember having this issue. If it's what I think it is, then the solution was to turn on Require Server Name Indication for my site bindings. To do so:
Hope this helps!
is working on a reply...