SSL errors in Azure
Trying to setup Coveo for Sitecore 72 3.0 (784), in Azure. Getting this error when trying to search within sitecore though:
[Win32Exception (0x80004005): The client and server cannot communicate, because they do not possess a common algorithm] System.Net.SSPIWrapper.AcquireCredentialsHandle(SSPIInterface SecModule, String package, CredentialUse intent, SecureCredential scc) +8615164 System.Net.Security.SecureChannel.AcquireCredentialsHandle(CredentialUse credUsage, SecureCredential& secureCredential) +439 System.Net.Security.SecureChannel.AcquireClientCredentials(Byte& thumbPrint) +2666 System.Net.Security.SecureChannel.GenerateToken(Byte input, Int32 offset, Int32 count, Byte& output) +444 System.Net.Security.SslState.StartSendBlob(Byte incoming, Int32 count, AsyncProtocolRequest asyncRequest) +77 System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte buffer, AsyncProtocolRequest asyncRequest) +8551966 System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult) +230 System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) +645 System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) +9 System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) +87 System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result) +1467 System.Net.TlsStream.Write(Byte buffer, Int32 offset, Int32 size) +84 System.Net.ConnectStream.WriteHeaders(Boolean async) +816
Our setup has Sitecore on a separate server to CES.
This looks like a Windows Authentication related error (because of SSPI). I'd guess something is trying to authenticate with Windows Auth but it's not working because your machines aren't on the same domain, but this is only a shot in the dark --- I'm clearly out of my element here (Sitecore and Azure).
Are there any more frames in the call stack that'd give me an indication of who is calling what?
Some folks in a different timezone might be able to provide a better answer later on.