Integration page never loads on self-hosted instance

Last updated: June 15, 2026

If the Integrations page never loads or shows a blank screen on your self-hosted Plane instance, this is almost always caused by the Silo service not being reachable or misconfigured.


Why this happens

The Integrations page depends on the Silo service to load available integrations and their configuration. If Silo is down, misconfigured, or can't reach external services, the page will fail to load, often silently with no visible error.

Common causes include:

  • Silo container not running or crashing on startup

  • Missing environment variables for integrations (GitHub, GitLab, Slack, etc.)

  • application_secrets or auth_applications tables not populated in the database


Step 1: Check if the Silo service is running

If the Silo container isn't running or is restarting repeatedly, that's your issue. Check the Silo logs and look for any errors on startup. Missing environment variables, database connection failures, or external API connection errors are the most common causes.


Step 2: Check browser Console and Network logs

  1. Open your browser's Developer Tools (F12)

  2. Go to the Console and Network tabs

  3. Navigate to the Integrations page

  4. Look for any failed requests, specifically anything hitting /silo/api/...

A 500 error on Silo endpoints confirms the Silo service is the problem. A 502 or 504 means the reverse proxy can't reach Silo at all.


Step 3: Populate the application secrets

If Silo is running but integrations still don't show up, the application_secrets and auth_applications tables may not be populated. Run the following command in the API container:

bash

python manage.py reset_marketplace_app_secrets

This registers the integration OAuth apps and should make the Integrations page load correctly.


Step 4: Check integration environment variables

Make sure the relevant environment variables are set for the integrations you want to use. For example:

  • GitHub: GITHUB_CLIENT_ID, GITHUB_CLIENT_SECRET

  • GitLab: GITLAB_CLIENT_ID, GITLAB_CLIENT_SECRET

  • Slack: SLACK_CLIENT_ID, SLACK_CLIENT_SECRET


Still not working?

Reach out to support with the following:

  • Silo container startup logs

  • Browser Console and Network logs when loading the Integrations page

  • Output of docker ps -a

  • Any error messages from the failed network requests