Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • admiss 20 posts 100 karma points
    Jul 25, 2016 @ 11:37
    admiss
    0

    Courier 2.52.7

    Hey,

    Since we switched our sites (test and live) to SSL, Courier has issues with deployment.

    We use TLS1.2 Protocol (and Umbraco 7.4.3 ) - does anyone know, if Courier (2.52.7) has a default(?) TLS protocol, or any SSL specs set in it somewhere, or not?

    Thanks a lot

    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 at System.Net.SSPIWrapper.AcquireCredentialsHandle(SSPIInterface SecModule, String package, CredentialUse intent, SecureCredential scc) at System.Net.Security.SecureChannel.AcquireCredentialsHandle(CredentialUse credUsage, SecureCredential& secureCredential) at System.Net.Security.SecureChannel.AcquireClientCredentials(Byte[]& thumbPrint) at System.Net.Security.SecureChannel.GenerateToken(Byte[] input, Int32 offset, Int32 count, Byte[]& output) at System.Net.Security.SecureChannel.NextMessage(Byte[] incoming, Int32 offset, Int32 count) at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult) at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result) at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size) at System.Net.ConnectStream.WriteHeaders(Boolean async) --- End of inner exception stack trace --- at System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest request) at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) at Umbraco.Courier.RepositoryProviders.CourierWebserviceRepositoryProvider.CloseSession(String sessionKey) at Umbraco.Courier.RepositoryProviders.CourierWebserviceRepositoryProvider.Dispose(Boolean disposing) at Umbraco.Courier.RepositoryProviders.CourierWebserviceRepositoryProvider.Dispose() at Umbraco.Courier.Core.Repository.Dispose(Boolean disposing) at Umbraco.Courier.Core.Repository.Dispose() at Umbraco.Courier.UI.Dialogs.CommitItem.OnInit(EventArgs e) at System.Web.UI.Control.InitRecursive(Control namingContainer) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) The client and server cannot communicate, because they do not possess a common algorithm

    System.ComponentModel.Win32Exception (0x80004005): The client and server cannot communicate, because they do not possess a common algorithm at System.Net.SSPIWrapper.AcquireCredentialsHandle(SSPIInterface SecModule, String package, CredentialUse intent, SecureCredential scc) at System.Net.Security.SecureChannel.AcquireCredentialsHandle(CredentialUse credUsage, SecureCredential& secureCredential) at System.Net.Security.SecureChannel.AcquireClientCredentials(Byte[]& thumbPrint) at System.Net.Security.SecureChannel.GenerateToken(Byte[] input, Int32 offset, Int32 count, Byte[]& output) at System.Net.Security.SecureChannel.NextMessage(Byte[] incoming, Int32 offset, Int32 count) at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult) at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result) at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size) at System.Net.ConnectStream.WriteHeaders(Boolean async)

  • Sebastiaan Janssen 5060 posts 15522 karma points MVP admin hq
    Jul 26, 2016 @ 15:08
    Sebastiaan Janssen
    0

    I assume your site has a redirect to force all traffic from http to https? I believe that in the latest Courier 2.52.13, we follow that redirect, but I don't remember for sure.

    Either way, have you checked your courier.config file? The configured repositories should be configured with an https <url /> instead of http, that should hopefully help.

  • admiss 20 posts 100 karma points
    Jul 27, 2016 @ 19:45
    admiss
    0

    Thanks, Sebastian Will check this tomorrow. Btw, is it possible that Courier/Umbraco is trying to do a transfer via TLS1.0 while the server works only at TLS1.2 ?

  • Sebastiaan Janssen 5060 posts 15522 karma points MVP admin hq
    Jul 27, 2016 @ 19:46
    Sebastiaan Janssen
    0

    It's just your local browser connection to a URL, so whatever your browser supports.

  • admiss 20 posts 100 karma points
    Jul 27, 2016 @ 20:41
    admiss
    0

    Right, thanks for this.

    I was just asking about the possible default built-in stuff, beacuse I downloaded the Courier 2.52.1 approx 2 months ago, decompiled some files, and in the Ssl.Protocols.cs found: Default = Tls | Ssl3; in the SecurityProtocolType.cs: Ssl3 = 48, Tls = 192

    enter image description here

  • admiss 20 posts 100 karma points
    Jul 27, 2016 @ 21:09
    admiss
    0

    Also, my coding fellow is running around in circles for some time with this... Additional info, log about this Courier issue: https://our.umbraco.org/forum/using-umbraco-and-getting-started/78098-courier-error-occurred-on-a-recieve

Please Sign in or register to post replies

Write your reply to:

Draft