title:"Troubleshooting GitOps Runtime installation"

description:"Review how to resolve issues during Runtime installation"

toc:true

Before initiating the installation, Codefresh automatically validates the`values.yaml` file to verify that the supplied values are correct.

Validation errors in your`values.yaml` file.

1. Get more detailed information on the reason for the validation failure by running:

where:

`{NAMESPACE}` is the namespace of the Hybrid GitOps Runtime.

1. Fix the errors. The table below describes the settings that are validated in the`values` file.

| Setting| Validation|

|----------------------|------------------------------------------------------------------------------------------------------------|

|`userToken`| If explicitly defined, or defined as a`secretKeyRef` which exists in the current k8s context and the defined namespace.|

|**Account permissions**| If the user has admin permissions for the account in which they are installing the runtime.|

|**Runtime name**| If defined, and is unique to the account.|

|**Access mode**| {::nomarkdown}<ul><li>For tunnel-based, the default, if`accountId` is defined, and matches the account of the`userToken` defined in the file.</li><li>For ingress-based, if the`hosts` array contains at least one entry that is a valid URL (successful HTTP GET).</li><li>If both tunnel-based and ingress-based access modes are disabled, if`runtime.ingressUrl` is defined.</li></ul>{:/}|

|`gitCredentials`| When defined, includes a Git password either explicitly, or as a`secretKeyRef`, similar to`userToken`. The password or token has the required permissions in the Git provider.|

This error displayed when you try to Configure the Runtime as Argo CD Application.

The Shared Configuration Repository (`ISC`) has been created but is not yet initialized.

Wait a few seconds, and try again.

One of these errors indicating a timeout:

* For tunnel-based access mode, the`codefresh-tunnel-client` pod fails after installation.

* Pods failed error

The Runtime installed successfully, but the Application Proxy (`cap-app-proxy`) pod is not running.

This status persists for the duration that the resources necessary for App Proxy are being created and initialized.

1. Verify the status of the`cap-app-proxy` pod:

1. If the pod is still**Pending**, check for resource constraints.

1. Scale up your cluster if needed.

The`--wait` flag in Install Runtime command controls how long the installation process waits for pods to become ready before timing out.

* Do one of the following:

* If already defined, increase the timeout beyond the default**5 minutes**.

* If not defined, add the`--wait` flag to allow time for the pods to initialize.

Example:`--wait 10m`

Your token is invalid because of missing scopes

OR

You are using a fine-grained token or one with custom scopes

**GitHub Git Runtime token**

{: .table .table-bordered .table-hover}

| Type| Required scopes|

| --------| -----------------|

|**Classic**|{::nomarkdown}<ul><li><codeclass="highlighter-rouge">repo</code></li><li><codeclass="highlighter-rouge">admin:repo_hook</code></li></ul>{:/}|

|**Fine-grained** (personal or group-based)|{::nomarkdown}<ul><li>Repository access: <codeclass="highlighter-rouge">All repositories</code> or <codeclass="highlighter-rouge">Only select repositories</code> including all repos that Argo CD syncs from</li><li>Repository permissions:<ul><li>Administration: <codeclass="highlighter-rouge">Read and write</code></li><li>Commit statuses: <codeclass="highlighter-rouge">Read and write</code></li><li>Contents: <codeclass="highlighter-rouge">Read and write</code></li><li>Metadata: <codeclass="highlighter-rouge">Read-only</code></li><li>Pull requests: <codeclass="highlighter-rouge">Read and write</code></li><li>Webhooks: <codeclass="highlighter-rouge">Read and write</code></li></ul></li></ul>{:/}|

{: .table .table-bordered .table-hover}

| Type| Required scopes|

| --------| -----------------|

|**Classic**| {::nomarkdown}<ul><li><codeclass="highlighter-rouge">repo</code></li><li><codeclass="highlighter-rouge">admin:repo_hook</code></li></ul>{:/}|

|**Fine-grained** (personal or group-based) | {::nomarkdown}<ul><li>Repository access: <codeclass="highlighter-rouge">All repositories</code> or <codeclass="highlighter-rouge">Only select repositories</code> including all repos that Argo CD syncs from

</li><li>Repository permissions:<ul><li>Administration: <codeclass="highlighter-rouge">Read and write</code></li><li>Commit statuses: <codeclass="highlighter-rouge">Read and write</code></li><li>Contents: <codeclass="highlighter-rouge">Read and write</code></li><li>Metadata: <codeclass="highlighter-rouge">Read-only</code></li><li>Pull requests: <codeclass="highlighter-rouge">Read and write</code></li><li>Webhooks: <codeclass="highlighter-rouge">Read and write</code></li></ul></li</ul>{:/} |

**GitHub Git user token**

{: .table .table-bordered .table-hover}

| Type| Required scopes|

| ------------| -----------------|

|**Classic**|{::nomarkdown}<ul><li><codeclass="highlighter-rouge">repo</code></li></ul>{:/}|

|**Fine-grained**|{::nomarkdown}<ul><li>Repository access: <codeclass="highlighter-rouge">All repositories</code> or <codeclass="highlighter-rouge">Only select repositories</code></li><li>Repository permissions:<ul><li>Contents: <codeclass="highlighter-rouge">Read and write</code></li><li>Metadata: <codeclass="highlighter-rouge">Read-only</code></li></ul></li></ul>{:/}|

{: .table .table-bordered .table-hover}

| Type| Required scopes|

| --------| -----------------|

|**Classic**| {::nomarkdown}<ul><li><codeclass="highlighter-rouge">repo</code></li><li><codeclass="highlighter-rouge">admin:repo_hook</code></li></ul>{:/}|

|**Fine-grained** (personal or group-based)| {::nomarkdown}<ul><li>Repository access: <codeclass="highlighter-rouge">All repositories</code> or <codeclass="highlighter-rouge">Only select repositories</code> including all repos that Argo CD syncs from</li><li>Repository permissions:<ul><li>Administration: <codeclass="highlighter-rouge">Read and write</code></li><li>Commit statuses: <codeclass="highlighter-rouge">Read and write</code></li><li>Contents: <codeclass="highlighter-rouge">Read and write</code></li><li>Metadata: <codeclass="highlighter-rouge">Read-only</code></li><li>Pull requests: <codeclass="highlighter-rouge">Read and write</code></li><li>Webhooks: <codeclass="highlighter-rouge">Read and write</code></li></ul></li></ul>{:/}|

If using a custom-scope or fine-grained token and your_Runtime version is v0.18.0 or lower_, you must disable token validation to prevent failures.

1. Check Runtime version:

* In the Codefresh UI, on the toolbar, click the**Settings** icon.

* From the sidebar, select**GitOps Runtimes**.

* In the**Versionw** column, if the chart version is v0.18.0 or lower, continue with_step 2_.

1. Add the`skipGitPermissionValidation` flag to your`values.yaml` file:

app-proxy:

config:

skipGitPermissionValidation:"true"

1. If you have configured auto-detect for Argo CD services, check if the labels are correctly defined:

<!--- Run this script to verify if the labels are correctly assigned:add the script -->