Source Control (4-2), Git - Configure To Connect To DevOps And GitHub

This is a series of articles related to Source Control or Version Control issues, from a stand-alone app, such as MS SourceSafe, to a Server app, such as MS TFS (Team Foundation Server), to web services such as GitHub, AWS, and MS Azure DevOps. We tried to categorize this series of articles as Source Control or Version Control, but this site does not have these categories, so we put the articles in the  as DevOps category, as explained in the wiki:

DevOps is a set of practices that combines software development (Dev) and IT operations (Ops). It aims to shorten the systems development life cycle and provide continuous delivery with high software quality.[1] DevOps is complementary with Agile software development; several DevOps aspects came from the Agile methodology.

The structure of this article series will cover,

  • Stand Alone App:
    • MS Source Safe
  • Server App
    • MS TFS (Team Foundation Server)
  • Online (Cloud) Centralized Service:
    • MS Azure: DevOps
      • Boards
      • Repos
      • Pipelines
      • Test Plans
      • Artifacts
    • GitHub
    • AWS GitHub Enterprise
  • Distributed App:
    • Git

Because these are huge topics,  I will not go step by step, instead, each section will be relatively independent to become a reading unit.


As we discussed in Source Control (4-1), Git --- Configuration, we usually do not need to configure Git when we install it either through Visual Studio or independently, except when we try to connect local Git to either DevOps or GitHub, we might get some issues due to configuration. 

This is the structure of this article,

  • Introduction
  • Problem
  • Possible Solutions
  • Fix
  • Summary


When trying to connect either DevOps or GitHub, in a certain situation, we got the error,

Or trying to Clone a repository to local,

We got an error message,

Or in the output window,

Possible Solutions

By searching online we found similar articles trying to solve the SSL issue, such as,

but they are not true solutions for this issue, we can just work around the issue easily.


This is a simple configure issue, due to not configuring Git at the setup stage,

Can be fixed by command,

git config --system http.sslbackend schannel

You have to have admin right to do so, otherwise, you will get error like this,

After this fix, everything will be working well.


This exception is found in some setup, it is a configuration issue, not a SSL problem


Similar Articles