Hi Arlan,

I would try it without the https.

Thanks Andy

Hi,

I get the same error, but the proposed solution by setting umbracoApplicationUrl="http://localhost/umbraco" in config/umbracoSettings.config doesn't work for me. The error still appears every 2 minutes.

We are working with Umbraco 7.5.4 assembly: 1.0.6136.27241

Best regards, Nadine

On our Umbraco 8 site, I've tried the above (changing the web.routing line in umbracoSettings so that the umbracoApplicationUrl="https://ourwebsitename/umbraco"), but still getting the keepalive errors every 5 minutes. I also read it could be a TLS thing but we have TLS 1.0 and 1.1 turned off on our Windows 10 server. I've read about adding this line somewhere, not sure where it goes: System.Net.ServicePointManager.SecurityProtocol = System.Net.SecurityProtocolType.Tls12

Anyone have any more luck with this?

You have to make a composition something like below:

 public class MyComponent : IComponent
    {
        public void Initialize()
        {
            System.Net.ServicePointManager.SecurityProtocol = System.Net.SecurityProtocolType.Tls12;
        }
}

I think it is also covered more exhaustively at https://our.umbraco.com/documentation/Implementation/Composing/

I have umbraco version 7.14.0 and have a same problem with a subdomain

2020-02-13 00:08:42,607 [P9100/D2/T23] ERROR Umbraco.Web.Scheduling.KeepAlive - Failed (at "http://subdomain.domain.com/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 receive. ---> 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.

Could any one help me please?.

If you're using Azure App Services, the service has a built-in "Always On" mode which achieves the same goal. Since Umbraco 8.6 you can disable the keepAlive task if you'd wish to. The configuration can be found in umbracoSettings.config:

<?xml version="1.0" encoding="utf-8" ?>
<settings>
  ...
  <!--
  keepAlive
    @disableKeepAliveTask
      Disables the periodic KeepAliveTask when set to "true".
      Use this setting to disable the KeepAliveTask in case you already have an alternative.
      For example, Azure App Service has keep alive functionality built-in.
      Defaults to "false".
    @keepAlivePingUrl
      The url of the KeepAlivePing action. By default, the url will use the umbracoApplicationUrl setting as the basis.
      Change this setting to specify an alternative url to reach the KeepAlivePing action. eg http://localhost/api/keepalive/ping
      Defaults to "{umbracoApplicationUrl}/api/keepalive/ping".
  -->
  <keepAlive disableKeepAliveTask="true" keepAlivePingUrl="{umbracoApplicationUrl}/api/keepalive/ping" />
</settings>

Last time I tried connecting to localhost on App Services, it denied on both HTTP/80 and HTTPS/443. I don't think the service allows you to do that. This is from Azure Web App sandbox docs:

Rejected connection attempts, such as the following example which attempts to connect to 127.0.0.1:80, from .NET will result in the following exception: Exception Details: System.Net.Sockets.SocketException: An attempt was made to access a socket in a way forbidden by its access permissions 127.0.0.1:80

I ended up disabling the keepAlive task and enabled "Always On". I ended up writing a blog post on the keep alive configuration here: https://swimburger.net/blog/umbraco/introducing-umbracos-keepalive-ping-configuration

Hope it helps!

is working on a reply...