Comments
1 comment
-
The Microsoft article resolved this issue, so if anyone else experiences this issue, please check the following:
Please also take a look at the following document which should help: https://documentation.red-gate.com/soc/troubleshooting/unable-to-push-changes-to-remote-git-repository
The above links you to the following from Microsoft to resolve this: https://support.microsoft.com/en-gb/topic/update-to-enable-tls-1-1-and-tls-1-2-as-default-secure-protocols-in-winhttp-in-windows-c4bd73d2-31d7-761e-0178-11268bb10392
Add comment
Please sign in to leave a comment.
The error message says the services are not available, but we are able to connect directly and via Visual Studio.
When going to the Azure DevOps site, it notes that they stopped accepting TLS 1.0 and 1.1 connections starting today, so I was wondering if SQL Source Control used one of those versions to connect? If so it appears that will no longer work, and I can not find any settings to configure TLS version being used, so unless I am missing something and there is a workaround I have not discovered, I believe this will take an update to SQL Source Control to resolve.
Could someone please let me know if there is something I can do in the meantime? My team can not Commit to or Get Latest from Source Control and it is critical to our work that we get this back up and running ASAP.
Thank you.
--
Rich