@@ -214,6 +214,54 @@ description: "Learn how to use Helm chart to install Digger on your Kubernetes c
214
214
215
215
</Steps >
216
216
217
+ ## Troubleshooting
218
+
219
+ <Accordion title = " Failed to validate installation_id error" >
220
+ If you see "Failed to validate installation_id" after GitHub App installation:
221
+
222
+ 1 . ** Check GitHub App credentials in your values.yaml:**
223
+ ``` yaml
224
+ digger :
225
+ secret :
226
+ githubAppClientID : " Iv1.abc123def456" # Should not be empty
227
+ githubAppClientSecret : " github_secret" # Should not be empty
228
+ ` ` `
229
+
230
+ 2. **Verify environment variables are set in the pod:**
231
+ ` ` ` bash
232
+ # Get pod name
233
+ kubectl get pods -n digger
234
+
235
+ # Check environment variables in the pod
236
+ kubectl exec -n digger deployment/digger-backend -- printenv | grep GITHUB_APP_CLIENT
237
+ ```
238
+
239
+ 3 . ** Restart the deployment to pick up new environment variables:**
240
+ ``` bash
241
+ kubectl rollout restart deployment/digger-backend -n digger
242
+ ```
243
+ </Accordion >
244
+
245
+ <Accordion title = " No response after creating pull request" >
246
+ If Digger doesn't respond when you create a pull request:
247
+
248
+ 1 . ** Check backend logs for errors:**
249
+ ``` bash
250
+ kubectl logs -n digger deployment/digger-backend --tail=100 -f
251
+ ```
252
+
253
+ 2 . ** Verify webhook deliveries in GitHub:**
254
+ - Go to your GitHub App settings: ` https://github.com/settings/apps/your-app-name `
255
+ - Click on "Advanced" tab
256
+ - Check "Recent Deliveries" for failed webhook attempts
257
+ - Look for 4xx/5xx HTTP status codes or connection timeouts
258
+
259
+ 3 . ** Common webhook issues:**
260
+ - Ensure your hostname is accessible from GitHub
261
+ - Check that your ingress is properly configured
262
+ - Verify SSL certificates are valid
263
+ </Accordion >
264
+
217
265
## Advanced Configuration
218
266
219
267
<Accordion title = " Using existing secrets" >
0 commit comments