Troubleshoot

This page shows you how to resolve issues with Secure Source Manager.

Error message when creating a repository

The following error appears when you try to create a repository:

There was an error while loading /repo/create. Try refreshing the page.

This issue occurs when:

  • The Secure Source Manager API isn't enabled in your project.
  • You don't have the Repo Admin role on your project or permissions to create repositories in the Secure Source Manager instance.

To resolve this issue:

  • Enable the Secure Source Manager API in your project.
  • Ask your administrator to grant you the following roles:
    • Repo Admin (roles/securesourcemanager.repoAdmin) role on your project.
    • Instance Accessor (roles/securesourcemanager.instanceAccessor) on the Secure Source Manager instance.
    • Instance Repository Creator (roles/securesourcemanager.instanceRepositoryCreator) on the Secure Source Manager instance.

See Access control with IAM for more details.

Error message when cloning a repository on a Mac

The following error appears when you try to clone a repository:

git: 'credential-gcloud.sh' is not a git command.  See 'git --help'.
fatal: Authentication failed for [repo-url]

This issue occurs when:

  • gcloud CLI is installed using Homebrew or other non-standard installation.
  • git-credential-gcloud.sh is not added to your PATH.

To resolve this issue:

  • Run source $HOMEBREW_PREFIX/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/path.zsh.inc

  • Check that git-credential-gcloud.sh is in your path by running the following command:

    which git-credential-gcloud.sh

SSH connection fails with "no matching" error

When attempting Git operations over SSH, you might receive one of the following error messages:

  • Unable to negotiate with <host> port <port>: no matching key exchange method found.
  • Unable to negotiate with <host> port <port>: no matching cipher found.
  • Unable to negotiate with <host> port <port>: no matching MAC found.

This issue occurs when your SSH client does not support the cryptographic algorithms required by Secure Source Manager. This can happen if you are using an older SSH client or if your client is not configured to use supported algorithms.

Secure Source Manager requires one of the following algorithms: