You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
|Commit statuses|Read-only|Allows the GitHub app to read and update commit statuses, indicating whether a commit has passed checks (e.g., CI/CD pipelines).|
148
-
|Contents|Read and write|Grants access to read and modify repository contents, including reading files, creating commits, and updating files.|
149
147
|Issues|Read and write|Enables reading, creating, updating, closing, and commenting on issues within the repository.|
150
-
|Merge queues|Read-only|Allows interaction with merge queues to manage the order of pull request merges.|
151
148
|Metadata|Read-only|Provides read-only access to repository metadata, such as its name, description, and visibility.|
152
149
|Pull requests|Read and write|Allows reading, creating, updating, merging, and commenting on pull requests.|
153
150
@@ -256,3 +253,55 @@ To configure GitHub integration, you'll need to create a GitHub App within your
256
253
8. Once you've created the app, [activate the GitHub Enterprise integration in Plane](https://docs.plane.so/integrations/github?edition=github-enterprise#connect-github-organization).
257
254
</Tab>
258
255
</Tabs>
256
+
257
+
258
+
## Troubleshooting
259
+
260
+
### Invalid private key
261
+
262
+
<divstyle={{color:"red"}}>
263
+
Error: Failed to create GitHub connection: Invalid keyData
264
+
</div>
265
+
266
+
This error usually occurs when the private key is not correctly generated. To fix this, follow the below steps.
267
+
268
+
1. Generate a new private key.
269
+
2. Convert the private key to base64.
270
+
```bash
271
+
cat private_key.pem | base64 -w 0
272
+
```
273
+
3. Add the private key to the `.env` file.
274
+
```bash
275
+
GITHUB_PRIVATE_KEY=<private_key>
276
+
```
277
+
4. Save the file and restart the instance.
278
+
279
+
### Unable to connect GitHub organization account or personal account
280
+
281
+
<divstyle={{color:"red"}}>
282
+
Error: Invalid request callback URL.
283
+
</div>
284
+
285
+
This error usually occurs when the callback URL is not correctly configured or the GitHub App is not marked public. To fix this, follow the below steps.
286
+
287
+
1. Check if the callback URL is correctly configured.
288
+
2. Check if your GitHub App is marked public.
289
+
290
+
### Application secret value not found
291
+
292
+
<divstyle={{color:"red"}}>
293
+
Error: Application secret value not found for key: x-github-id
294
+
</div>
295
+
296
+
This error usually occurs when the application secret is not correctly configured. To fix this, follow the below steps.
297
+
298
+
1. Delete the `plane_app_details_github` key from redis cache. ```del plane_app_details_github```.
299
+
2. Set the `SILO_BASE_URL` in env with plane self hosted url and restart the api server. ```export SILO_BASE_URL=https://<your-domain>```
300
+
3. Run this command in api server shell `python manage.py reset_marketplace_app_secrets` to reset the application secrets.
301
+
4. Try to connect again to the organization account to Plane.
302
+
303
+
### Github integration suddenly stopped working after a while
304
+
305
+
This error usually occurs when the GitHub integration is not correctly configured. To fix this, follow the below steps.
306
+
307
+
1. Make sure you've `opted out` of Server Token expiration and reconnect once again to the organization account to Plane. Check in Github App Settings > Optional Features
0 commit comments