Authentication Errors (401 / 403) with the API or Git

Details
Category: Troubleshooting
  • Applicable Software: MokoGIT
  • Min Version Number: Not Applicable
  • Max Version Number: Not Applicable

401 / 403 or "Only signed in user is allowed to call APIs"

This means the request reached MokoGIT anonymously. Generate a personal access token (Settings → Applications → Generate Token) and send it on every request as an HTTP header:

Authorization: token YOUR_ACCESS_TOKEN

The redirect that drops your token

The API may answer with a 307 redirect. Some HTTP clients strip the Authorization header when they follow a redirect, so the retried request lands anonymously and fails with 401/403 - even though your token is valid. Use a client that preserves auth across redirects:

  • curl: use --location-trusted (not plain -L).
  • PowerShell: Invoke-RestMethod -PreserveAuthorizationOnRedirect.

Token scope

A valid token still returns 403 if it lacks the scope for the action (for example, writing to a repository or administering an organization). Recreate the token with the scopes the operation needs.

Git over HTTPS

For git clone/push over HTTPS, use your username and the access token as the password. For automation, prefer SSH keys (see the SSH Keys guide).

Hits: 15