The 401 error suggests GitHub isn't receiving valid authentication credentials. Since you've already tried changing the URL, I'd check these things next:

1. Confirm the token is valid. If it's a classic personal access token, make sure it hasn't expired or been revoked. For a private repository, it needs the appropriate repo scope.
2. Avoid putting the token directly in the clone URL. Shells can interpret special characters, and the token may also be saved in your Git remote or shell history.
3. Check for cached credentials. Git Credential Manager may be reusing an old username/token. Remove the saved GitHub credential from your operating system's credential manager, then retry and sign in with the correct token when prompted.
4. Try the normal HTTPS URL:

   git clone https://github.com/OWNER/REPO.git

   When prompted, enter your GitHub username and use the personal access token as the password.

If it still fails, could you share your OS, Git version (git --version), and whether the repository is public or private? Please never share the token itself.

Solution: Fixing GitHub Clone Authentication (HTTP 401)

The problem is with how the token is supplied to Git. Your command uses http:// and places the token before @github.com, which treats it as the username rather than using it as the password.

Here is how to fix it.

Step 1: Use the correct HTTPS clone URL

Instead of:

git clone http://$MY-CLASSIC-TOKEN@github.com/OWNER/REPO.git new-name

Use:

git clone https://github.com/OWNER/REPO.git new-name

Replace OWNER and REPO with the actual repository owner's username or organization and repository name.

Step 2: Authenticate using your personal access token

If the repository is private, Git will prompt you for credentials.

• Username: Enter your actual GitHub username.
• Password: Paste your personal access token, not your GitHub account password.

The token is used for authentication even though Git asks for your username.

If the repository is public, you can normally clone it without a token.

Step 3: Check your token permissions

If you still receive HTTP 401, check the following:

• The token has not expired or been revoked.
• A classic personal access token has the required repo scope for private repository access.
• A fine-grained token has access to the correct repository and the necessary permissions.
• If the repository belongs to an organization, check whether organization SSO authorization is required.

Step 4: Recommended approach — use GitHub CLI

You can avoid manually inserting tokens into clone URLs by using GitHub CLI.

First, install GitHub CLI if it is not already installed: https://cli.github.com/

Then run:

gh auth login

Follow the prompts to authenticate with GitHub, preferably using the browser.

After authentication, clone the repository into your desired local folder:

gh repo clone OWNER/REPO new-name

This clones the repository into a directory named new-name.

Step 5: Keep your token secure

Avoid putting your personal access token directly into a clone URL. Tokens in URLs can be exposed through shell history, logs, or other local configuration. Use GitHub CLI or a credential manager instead.

In summary: Use the HTTPS clone URL, authenticate with your GitHub username and personal access token, and use GitHub CLI for a more convenient workflow.

Official references:

• https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens
• https://cli.github.com/manual/gh_repo_clone