[[["わかりやすい","easyToUnderstand","thumb-up"],["問題の解決に役立った","solvedMyProblem","thumb-up"],["その他","otherUp","thumb-up"]],[["わかりにくい","hardToUnderstand","thumb-down"],["情報またはサンプルコードが不正確","incorrectInformationOrSampleCode","thumb-down"],["必要な情報 / サンプルがない","missingTheInformationSamplesINeed","thumb-down"],["翻訳に関する問題","translationIssue","thumb-down"],["その他","otherDown","thumb-down"]],["最終更新日 2025-09-04 UTC。"],[],[],null,["# Troubleshoot\n\nThis page shows you how to resolve issues with Secure Source Manager.\n\nError message when creating a repository\n----------------------------------------\n\nThe following error appears when you try to create a repository: \n\n```\nThere was an error while loading /repo/create. Try refreshing the page.\n```\n\nThis issue occurs when:\n\n- The Secure Source Manager API isn't enabled in your project.\n- You don't have the Repo Admin role on your project or permissions to create repositories in the Secure Source Manager instance.\n\nTo resolve this issue:\n\n- [Enable the Secure Source Manager API](/secure-source-manager/docs/enable-disable) in your project.\n- Ask your administrator to grant you the following roles:\n - Repo Admin (`roles/securesourcemanager.repoAdmin`) role on your project.\n - Instance Accessor (`roles/securesourcemanager.instanceAccessor`) on the Secure Source Manager instance.\n - Instance Repository Creator (`roles/securesourcemanager.instanceRepositoryCreator`) on the Secure Source Manager instance.\n\nSee [Access control with IAM](/secure-source-manager/docs/access-control) for more details.\n\nError message when cloning a repository on a Mac\n------------------------------------------------\n\nThe following error appears when you try to clone a repository: \n\n```\ngit: 'credential-gcloud.sh' is not a git command. See 'git --help'.\nfatal: Authentication failed for [repo-url]\n```\n\nThis issue occurs when:\n\n- gcloud CLI is installed using Homebrew or other non-standard installation.\n- `git-credential-gcloud.sh` is not added to your PATH.\n\nTo resolve this issue:\n\n- Run `source $HOMEBREW_PREFIX/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/path.zsh.inc`\n- Check that `git-credential-gcloud.sh` is in your path by running the\n following command:\n\n which git-credential-gcloud.sh\n\nGit HTTPS requests fail with permission denied or unauthorized error\n--------------------------------------------------------------------\n\nWhen Git commands are attempted over HTTPS, a permission denied or unauthorized\nerror message is given.\n\nThis issue occurs when one of the following occurs:\n\n- The global Git config file is missing the Secure Source Manager authentication helper.\n- Git's built-in credential store is being used instead of calling the Secure Source Manager authentication helper to get a fresh credential.\n- A system credential helper is being used instead of calling the Secure Source Manager authentication helper to get a fresh credential.\n- An older version of Google Cloud CLI is used when interacting with Secure Source Manager repositories using HTTPS. Secure Source Manager requires Google Cloud CLI version 395.0.0 or newer.\n\nTo resolve this issue:\n\n1. Run the following command to determine the contents of your global Git\n config.\n\n git config --list | grep credential\n\n2. If you see any line similar to `*credential*.helper=store` on macOS, or\n `credential.helper = manager` on Windows OS, then remove those lines, and\n then re-authenticate using `gcloud auth login` before trying the Git\n command again.\n\n3. If the response doesn't include\n `credential.https://*.*.sourcemanager.dev.helper=gcloud.sh` on macOS or\n Linux, or\n `credential.https://*.*.sourcemanager.dev.helper=gcloud.cmd` on Windows,\n then add the Secure Source Manager authentication helper to your global Git\n config:\n\n ### Linux\n\n 1. To add the Secure Source Manager authentication helper to your global Git\n config, run the following command:\n\n git config --global credential.'https://*.*.sourcemanager.dev'.helper gcloud.sh\n\n 2. Validate that the authentication helper line is added to your global Git\n config by running the following command:\n\n git config --list | grep credential\n\n The output should include\n `credential.https://*.*.sourcemanager.dev.helper=gcloud.sh`.\n 3. Authenticate by running `gcloud auth login`.\n\n 4. Run a Git command to test the authentication.\n\n ### Windows\n\n 1. Check your gcloud CLI version by following the [Install Git\n and Google Cloud CLI](/secure-source-manager/docs/use-git#install_git_and) instructions.\n 2. To add the Secure Source Manager authentication helper to your global Git\n config, run the following command:\n\n git config --global credential.https://*.*.sourcemanager.dev.helper gcloud.cmd\n\n 3. Validate that the authentication helper line is added to your global Git\n config by running the following command:\n\n git config --list | grep credential\n\n The output should include\n `credential.https://*.*.sourcemanager.dev.helper=gcloud.cmd`.\n 4. Authenticate by running `gcloud auth login`.\n\n 5. Run a Git command to test the authentication.\n\nProject not showing up in web interface product selector\n--------------------------------------------------------\n\nWhen using the Secure Source Manager web interface product selector, your\nproject doesn't appear.\n\nThis issue occurs when you have multiple login credentials for\nSecure Source Manager.\n\nTo resolve this issue:\n\n- Clear your cookies by appending the following to your Secure Source Manager\n instance URL:\n `/_oauth/consent`\n\n For example, if your instance URL is\n `https://my-instance-098765432123.us-central1.sourcemanager.dev/`, enter\n `https://my-instance-098765432123.us-central1.sourcemanager.dev/_oauth/consent`\n into your browser address bar and then sign in with the correct credentials.\n\nTriggers file doesn't trigger builds\n------------------------------------\n\nIf builds aren't triggered as expected after submitting your triggers file, you\nmight have one of the following problems:\n\n- The triggers file isn't in the default branch. To resolve this, move your triggers file to your default branch.\n- The triggers file has an invalid format. This error is indicated by a banner in the repository page that reads `Build triggers configuration error: ...`. To fix this, read the [Triggers file schema](/secure-source-manager/docs/triggers-file-schema). When the triggers file configuration is correct, the banner in the repository page reads `Valid build triggers configuration`.\n\nBuild triggers configuration error\n----------------------------------\n\nAfter submitting your `triggers.yaml` file to your Secure Source Manager\nrepository you get the following error displayed in a banner: \n\n Build cannot be created.\n\nThis issue occurs for the following reasons:\n\n- The Cloud Build configuration file has invalid options.\n- The Cloud Build configuration file has an invalid format.\n- The Secure Source Manager service account doesn't have the required permissions to use the user-specified Cloud Build service account.\n\nTo fix this issue:\n\n- Make sure you're following the correct [Triggers file schema](/secure-source-manager/docs/triggers-file-schema).\n- Make sure that the Secure Source Manager service account and the Cloud Build service account have sufficient permissions. To view the required permissions, see [Required service account roles](/secure-source-manager/docs/connect-cloud-build#required-sa-roles).\n\nBuild fails during execution\n----------------------------\n\nIf a build is triggered successfully, but fails during execution, the associated\ncommit has a Failure commit status.\n\nTo troubleshoot a failed build, in the repository page, next to the failed\ncommit status, click **Details**.\n\nThe Cloud Build execution log opens. For more information on troubleshooting\nbuilds in Cloud Build, see\n[Troubleshooting build errors](/build/docs/troubleshooting)."]]
