Staging error connecting to server

Brian Bailey asked on September 13, 2018 23:03

I have seen some posts similar to this, but not sure my question is answered. I have 3 servers - dev, test, prod. Test is new. I previously had dev and prod. I successfully staged from dev to prod in the past without issue. We recently forced https on the sites (which are hosted in Azure). Today, we also had the certificates expired and had to upload and bind new certificates. Now when I try to check server availability in the servers portion of staging from the source server (dev), I get "The underlying connection was closed: An unexpected error occurred on a send.". I get it on the prod server (which used to work) and also on the new test server that we are adding into the mix. Based on other posts and our circumstances, it would appear that this is related to introducing SSL or the new certificate. I restarted the sites in question, but I am still getting the error. If anyone can point me to documentation on how to resolve staging over forced HTTPS, that would be appreciated as that seems to be the issue here.

Thanks.

Recent Answers


Brian Bailey answered on September 14, 2018 15:42

I ended up resolving this. Lowered SSL to TLS 1.0 instead of 1.2 and it seems to have resolved.

0 votesVote for this answer Mark as a Correct answer

David te Kloese answered on September 14, 2018 15:51

You might want to look into TLS and security issues.

As you can see in this old Kentico article from 2016(!)

https://devnet.kentico.com/articles/tls-1-2-support

https://www.google.com/search?q=tls+1.0+security+risk

0 votesVote for this answer Mark as a Correct answer

Brian Bailey answered on September 14, 2018 16:40

Good points. We're still on version 10 of Kentico deployed as a web app to Azure. It appears that we built it with .Net 4.5. I think we are thus limited to the directions about enabling it. If I set to 1.1 or 1.2, connections to target servers fail. Will go that route if possible. I can connect at 1.0, but it is then giving me an error with "Synchronization client error: Exception occurred: The request failed with an empty response.". Others seem to have gotten this and indicate a login problem, but have double checked it. Always something....

0 votesVote for this answer Mark as a Correct answer

   Please, sign in to be able to submit a new answer.