Prerequisites
- Admin privileges on your GitHub Enterprise Server organization where you want to install the app
- Access to your organization’s repositories where you want to install the app
- Network connectivity to communicate with our external services (see Network requirements section below)
Network requirements
Outbound connectivity
Your GitHub Enterprise Server must be able to reach:- Mintlify’s API endpoints (https://leaves.mintlify.com)
- Webhook receivers (port 443)
Firewall configuration
The following outbound connections must be allowed:- Connections from Mintlify’s static IP:
54.242.90.151 - HTTPS (port 443) to Mintlify’s service domains
- DNS resolution for Mintlify’s service domains
Step 1: Register the GitHub App
See Registering a GitHub App in the GitHub documentation for detailed instructions.Navigate to your organization settings
- In the upper-right corner of any page on GitHub, click your profile picture. 2.Click Your organizations.
- Click Settings next to the organization that you want to create the app for.
Create a new GitHub App
- In the left sidebar, click Developer settings.
- Click GitHub Apps.
- Click New GitHub App.
Step 2: Configure app permissions
Set repository permissions
Set the following permissions for the app. No Organization, Account, or Enterprise permissions are required:
- Checks: Read and write
- Contents: Read and write
- Deployments: Read and write
- Metadata: Read-only
- Pull Requests: Read and write
Step 3: Generate and secure credentials
Generate private key
- Scroll down to the Private keys section.
- Click Generate a private key.
- Download the
.pemfile and securely store it.
Step 4: Install the app
Navigate to app installation
- From the app settings page, click Install App in the left sidebar.
- Select your organization from the list.
Choose installation scope
Select either:
- All repositories (for organization-wide access)
- Only select repositories (choose specific repositories)
Step 5: Configure webhook URL
Set webhook URL
Configure the following:
- Webhook URL:
https://leaves.mintlify.com/github-enterprise/:subdomain(replace:subdomainwith the URL that we provide you with) - Webhook secret: Generate a random string (32+ characters) and record it securely. Mintlify can also generate this and provide it to you.
Share credentials with us
Please share the following information with our team using your secure information transfer method of choice.Required credentials
- GitHub Enterprise Server base URL: https://your-github-server.com
- App ID: (from step 3)
- App client ID: (from step 3)
- App client secret: (from step 3)
- Installation ID: (from step 4)
- Private key: The entire contents of the
.pemfile (should be shared via secure file transfer) - Webhook secret: (from step 5)
Optional credentials for troubleshooting
- Organization name: Your GitHub organization name
- Repository names: Specific repositories where the app is installed
- GitHub Enterprise Server version: Found in your site admin dashboard
Mintlify connection
We take the credentials you provide us and store them, encrypted, in a secure location. Then we work with you to either:- Integrate your GHES environment with an existing Mintlify deployment.
- Integrate your GHES environment with a new Mintlify deployment that we provision for you.
The webhook URL may change based on our configuration. We test the integration and provide you with the new URL.
Test the integration
Verify webhook delivery
- Go to your GitHub App settings.
- Click the Advanced tab.
- Check “Recent Deliveries” for successful webhook deliveries.
- Look for HTTP 200 responses.
FAQ and Troubleshooting
The app installation is failing with permission errors.
The app installation is failing with permission errors.
Ensure you have:
- Site admin privileges for app creation
- Organization owner or admin rights for app installation.
- Proper repository permissions if installing on specific repositories.
Webhooks aren't being delivered
Webhooks aren't being delivered
- Verify the webhook URL is correct and accessible.
- Ensure your firewall allows outbound HTTPS connections.
- Check the webhook secret matches what was configured.
- Review webhook delivery logs in the “Advanced” tab of your GitHub App settings.
I'm getting SSL/TLS certificate errors
I'm getting SSL/TLS certificate errors
Your GHES might use self-signed certificates. Our services cannot verify your server’s certificate.Solution: Ensure your GHES has a valid SSL certificate.
The app installs, but doesn't respond to events.
The app installs, but doesn't respond to events.
- Ensure webhooks are being delivered and acknowledged by our server with response code 200.
- Required permissions were granted during installation.
Can I limit which repositories the app accesses?
Can I limit which repositories the app accesses?
Yes, during installation you can select “Only select repositories” and choose specific ones. You can modify this later in your organization’s installed apps settings. This is the recommended form of installation.
How do I update app permissions later?
How do I update app permissions later?
- Go to the app settings as a site admin.
- Modify permissions as needed.
- The app will need to be re-approved by organization owners.
- Notify us of any permission changes as they may affect functionality.
Our GHES is behind a corporate firewall, nginx proxy, or similar setup.
Our GHES is behind a corporate firewall, nginx proxy, or similar setup.
You must:
- Whitelist our service domains in your firewall.
- Ensure outbound HTTPS (port 443) connectivity.
- If direct internet access is not allowed, set up a proxy.
Can this work with GHES in air-gapped environments?
Can this work with GHES in air-gapped environments?
No, your GHES must be able to communicate with our cloud-hosted server.
Who should I contact if I need help?
Who should I contact if I need help?
Please reach out to your customer success representative who you’ve spoken to at Mintlify, or our support team at support@mintlify.com with:
- Your GitHub Enterprise Server version.
- Specific error messages.
- Screenshots of any issues.
- Network/firewall configuration details (if relevant).