Fixing insufficient permissions errors for Git platforms
Learn how to troubleshoot repository and metadata access issues.
Insufficient permissions errors may occur when the account or access token used to connect a protected Git platform with GitProtect does not have the required access rights. Verifying the assigned permissions and updating the account or token configuration can restore access and allow backup and recovery operations to run correctly.
General information
If a backup or restore task fails due to insufficient permissions, GitProtect logs the failure directly in the task summary. These notifications follow a structured format that includes an error code and message.
DV9022
Access to repository is forbidden.
Insufficient permissions to access the repository.
DV9030
Metadata download failure.
Insufficient permissions to download the metadata.
DW0834
Your Branch Protection Rules blocked this action. Add your Personal Access Token (PAT) to complete the [process name].
Insufficient permissions to backup/restore the branch protection rules.
DW5001
Repository permissions are insufficient.
Insufficient permissions to back up the repository.
DW5083
Git - GitHub App has insufficient rights to get branch protecting rules. Please provide Personal Access token in additional credentials.
Insufficient permissions to backup/restore the branch protection rules.
Resolving permission errors
Restoring branch protection rules requires a token configured with write access to the target repository.
If you encounter one of the specific errors listed above, follow these steps to adjust your backup or restore plan configuration:
Log in to the target Git platform, then verify your account permissions and adjust them if needed. Ensure the account used for synchronization with GitProtect has the required permissions to access the repository causing the error.
Generate a new personal access token (PAT) or API token for Atlassian.
Log in to GitProtect Management Service. Add the generated PAT or API token to the Password Manager (Settings > Password Manager).
Update the access token in the backup or restore plan that generates the error (Edit plan > Advanced settings > Additional Git credentials).
Useful links and items
Last updated
Was this helpful?