Skip to main content

Expired Version Control Credentials

When version control personal access tokens (PATs), app passwords, or other credentials expire or are revoked, Git operations in Coalesce will fail with authentication errors (401) errors.

Renewing and Updating Credentials​

  1. Regenerate your token on the provider’s website.
  2. Update the token in Coalesce:
    1. Go to User Settings > Version Control Accounts.
    2. Locate the account with the expired token and click Edit.
    3. Paste the new token and click Save.

Possible Errors by Platform​

Below are common error messages returned by Coalesce when using expired credentials.

GitHub​

Can't connect to git: Error: Issue cloning repository: Support for password authentication was removed on August 13, 2021. Please see https://docs.github.com/... for recommended authentication methods.
Error pushing to remote: HTTP Error: 401 Support for password authentication was removed on August 13, 2021. Please see https://docs.github.com/... for recommended authentication methods.

Bitbucket​

Can't connect to git: Error: Issue cloning repository: Invalid credentials

GitLab​

Can't connect to git: Error: Issue cloning repository: HTTP Basic: Access denied. If a password was provided for Git authentication, the password was incorrect or you're required to use a token instead of a password. If a token was provided, it was either incorrect, expired, or improperly scoped. See https://gitlab.com/help/topics/git/troubleshooting_git.md#error-on-git-fetch-http-basic-access-denied

Azure DevOps​

Can't connect to git: Error: Issue cloning repository: HTTP Error: 401 Unauthorized – the Personal Access Token has expired.

What's Next?​

After updating the token in Coalesce, retry your failed action. If problems persist, verify token scopes and expiration date on the provider's site.