Join our Discord Server
Ajeet Raina Ajeet Singh Raina is a former Docker Captain, Community Leader and Distinguished Arm Ambassador. He is a founder of Collabnix blogging site and has authored more than 700+ blogs on Docker, Kubernetes and Cloud-Native Technology. He runs a community Slack of 9800+ members and discord server close to 2600+ members. You can follow him on Twitter(@ajeetsraina).

How to Fix “Support for password authentication was removed” error in GitHub

1 min read

GitHub is a popular platform for version control and collaboration, but in August 2021, GitHub removed support for password authentication for HTTPS URLs. This means that if you try to clone a repository using an HTTPS URL and authenticate with a password, you will receive the following error message: “Support for password authentication was removed on August 13, 2021.” Fortunately, you can fix this issue by switching to a personal access token (PAT) or an SSH URL.

I was trying to push my latest committed code to the remote GitHub repository, but faced the following error message:

remote: Support for password authentication was removed on August 13, 2021.
remote: Please see https://docs.github.com/en/get-started/getting-started-with-git/about-remote-repositories#cloning-with-https-urls for information on currently recommended modes of authentication.
fatal: Authentication failed for 'https://github.com/collabnix/reponew'

To fix the “Support for password authentication was removed” error in GitHub, you need to switch to using a personal access token (PAT) instead of a password for authentication. Here are the steps to follow:

Option 1: Use a Personal Access Token (PAT)

Step 1. Create a personal access token (PAT) on GitHub

Login to your GitHub account. Go to Settings.

Image1

Step 2. Generate a new token

Select “Developer settings,” and then “Personal access tokens.”

Image2

Next, you need to generate a new token by selecting the “Generate new token” button. Give your token a name and select the scopes you need. For cloning repositories, you need to select the “repo” scope.

Image3

Step 3. Copy the token to your clipboard.

When prompted for your GitHub credentials while cloning a repository using an HTTPS URL, paste your PAT as your password.

Option 2: Use an SSH URL

Alternatively, you can configure Git to use your PAT for all future interactions with GitHub by running the following command in your terminal:

git config --global credential.helper store

This command will save your credentials to a local file, so you don’t have to enter them every time you interact with GitHub. You can then enter your GitHub username as usual, and your PAT as your password.

Keep in mind that using an SSH URL to clone a repository is a more secure and recommended option, as it allows you to authenticate using your SSH key instead of a password or PAT.

Further Reading

  • How to Build a PromptOps Playbook for Teams

    How to Build a PromptOps Playbook for Teams

    What happens when your best prompt engineer leaves the company and takes their “magic” strings with them? Most DevOps teams struggle with this exact void, facing a chaotic reality where AI instructions are scattered across Slack threads and private Notion pages. Moving from ad-hoc experimentation to a reliable production environment needs a shift of mindset.…

  • Why IT Departments Need Enterprise Password Management Tools

    Why IT Departments Need Enterprise Password Management Tools

    IT departments are under increasing pressure to safeguard sensitive information. As cyber security threats rise, password protection has become pivotal to the digital economy. Using enterprise password management tools can help you avoid unnecessarily exposing sensitive information. Implementing these systems allows organizations to remain protected and efficient while reducing friction for employees as they go…

  • Small Business AI Playbook: 5 Use Cases That Pay Off Fast

    Small Business AI Playbook: 5 Use Cases That Pay Off Fast

    Small businesses do not need flashy AI projects to get real value. They need quick wins that remove friction from work they already repeat. The best use cases are the ones tied to daily volume, customer messages, quotes, invoices, and internal questions. Start with one workflow, set a baseline, and put a human approval step…

Have Queries? Join https://launchpass.com/collabnix

Ajeet Raina Ajeet Singh Raina is a former Docker Captain, Community Leader and Distinguished Arm Ambassador. He is a founder of Collabnix blogging site and has authored more than 700+ blogs on Docker, Kubernetes and Cloud-Native Technology. He runs a community Slack of 9800+ members and discord server close to 2600+ members. You can follow him on Twitter(@ajeetsraina).
Join our Discord Server
Index