Troubleshooting HTTPS Authentication

HTTPS authentication uses either a service account or a generic HTTP/S credential from Gitfox → Settings → Accounts & Credentials.

Check the remote URL

HTTPS credentials only apply to HTTPS remotes. If the remote URL starts with git@ or ssh://, use the SSH troubleshooting article instead.

Reauthorize the account

Open Settings → Accounts & Credentials, select the account, open the gear menu, and choose Reauthorize Account.

Check token type and scopes

For personal access tokens, confirm that the token has the required scopes shown by Gitfox when adding the account. Also check that the token has not expired.

GitLab Self-Managed and Gitea require a valid Base URL in addition to the token.

Choose the account for a remote

If Gitfox cannot authenticate an HTTPS remote, it prompts you to select the account or HTTP/S credential that should be used for that connection.

You can also change the selected account manually. Right-click the remote, choose Edit Remote, then choose the service account or HTTP/S credential for that remote.

Use a generic HTTP/S credential

If the remote is not tied to a supported hosted account, add an HTTP/S Credential. Gitfox can store a display name, username, and password for basic HTTPS authentication.