We are seeing this same error on an SSL secured website:

[P10828/D70/T24] ERROR Umbraco.Web.Scheduling.ScheduledPublishing - Failed (at "https://admin.domain.com/umbraco").
System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: The underlying connection was closed:

Hi,

I'm having the same issue but with a couple of differences.

Both staging and production servers have been working for a while and suddenly we are getting these errors (we are currently investigating for changes in our network or settings but haven't found anything yet)

Also in our case all transfers are working correctly except for media files. I checked production and the folder seems to have the right permissions and there's plenty of room in the hard drive.

The files we are transferring are small, well below the maxRequestLength and the site timeout settings are also generous.

Does anyone have any idea on the issue? Thank you!

Did either of you manage to resolve this?

We are seeing this regularly occurring in the log files (every 5 minutes) and believe it is something to do with the disabling of the old SSL/TLS protocols on the server. I'm currently investigating it with the host but do not yet have a solution.

In addition to the ScheduledPublishing exception the following is also flooding the logs with a similar exception, both I'm sure are related:

2017-01-31 09:37:56,028 [P7044/D2/T48] ERROR Umbraco.Web.Scheduling.KeepAlive - Failed (at "https://www.sitename.org.uk/umbraco").
System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host
   at System.Net.Sockets.NetworkStream.EndRead(IAsyncResult asyncResult)
   --- End of inner exception stack trace ---
   at System.Net.TlsStream.EndWrite(IAsyncResult asyncResult)
   at System.Net.ConnectStream.WriteHeadersCallback(IAsyncResult ar)
   --- End of inner exception stack trace ---
   at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
   at System.Net.Http.HttpClientHandler.GetResponseCallback(IAsyncResult ar)
   --- End of inner exception stack trace ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Umbraco.Web.Scheduling.KeepAlive.<PerformRunAsync>d__4.MoveNext()

At present, I am still no further forward with this.

This is becuase most of the API providers require TLS 1.2 nowadays

Trying adding the below code to your Global.asax.cs:

ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12;

Regards

Craig

Hi Craig,

Thanks for lightning-fast reply! Since we do not develop our razor views in Umbraco (among other things) I only have a Global.asax to work with.

Can the setting you list above be set in some xml .config file instead?

Thanks again! Dustin

Hi Dustin & Craig,

At the time no-one knew anything so we had to battle out what the problem was. And it is just as Craig is saying:

<script runat="server">
        void Session_Start(object sender, EventArgs e){
        System.Net.ServicePointManager.SecurityProtocol = System.Net.SecurityProtocolType.Tls12;
        }
</script>

Cheers

J

Thank you James!

Craig:

I tried to add that SecurityProtocol to the Global.asax:

<script runat="server">

    void Session_Start(object sender, EventArgs e)
    {           
        System.Net.ServicePointManager.SecurityProtocol = System.Net.SecurityProtocolType.Tls12;
    }

</script>

and the error I see now is:

System.Net.Http.HttpRequestException: An error occurred while sending the request. --->

System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a receive. ---> System.ComponentModel.Win32Exception: The client and server cannot communicate, because they do not possess a common algorithm

please use https://www.ssllabs.com/ssltest to test what algorithm is on your server and then set it in Global.asax. For example:

Did anyone find a solution to this issue? I have the same problem on a website that I'm running.

You're welcome Dan, glad someone else found it useful. And thanks for reminding me that I really should check back on those projects and make sure I kept my word of removing the temporary fix ;)

Thank you Simon you have saved me also. Free beers if you ever get to Brisbane!

Simon Dingley, is the recommended code supposed to be dropped into the API site or the front-end web site, or both?

I just deployed two Umbraco 7.15.5 sites to two different servers. Both sites are configured to only respond to HTTPS requests. Both sites are configured the same in IIS.

Site A: The Health Checks in the CMS all run just fine. And if I look in the umbraco log I see that there are no keepalive errors.

Site B: The Health Checks in the Security section fail with this message: 'The request was aborted: Could not create SSL/TLS secure channel.' And in the umbraco log the keepalive requests are failing with the same error.

I compared the SChannel Protocols registry keys on both servers and they're the same except: Server A enables TLS 1.2 AND TLS 1.1 while Server B only enables TLS 1.2.

I modified Site B to set "ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12" in the application_starting event handler.

I remoted into Server B and opened up Google Chrome and loaded up Site B to see if perhaps the server has a DNS resolution problem. Nope, the site loaded up properly and showed as having a proper secure connection.

Both servers are Windows Server 2012. The two sites are clones of a third site where we made content changes. So code-wise they're practically identical. Configuration-wise they're practically identical.

Yet, one of them is having this security protocol issue when it's trying to talk to itself. BTW, for both I set the site URL in the umbracosettings.config file.

The only major difference between the two servers as that Server B did not have .Net Framework 4.5.2 when I moved Site B onto it. I had to install the framework and reboot the server.

Any ideas? I'm really at a loss as to what I could be missing. Thanks!

In Umbraco 8 it looks like this

protected override void OnApplicationStarting(object sender, EventArgs e)
        {
            base.OnApplicationStarting(sender, e); ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12;       }

I'm brining this up as we have encountered the issue only just recently. I'm sorry about my simple question, but in Simon Dingley's solution, is the name space he provided just an example and our own name space that our project is part of should replace that?

namespace MyNamespace.www {

}

or does the .www part have to be there?

Thanks.

is working on a reply...