Getting Started

Introduction to ServerPlane Creating Your Account Dashboard Overview Quickstart: First Server & App

Servers

Connecting a Server Server Overview Managing Services Alert Rules & Monitoring Server Settings SSH and Permissions SSH Keys

Apps

Deploying an Application Deploying a WordPress Application Deploying a Node.js Application Deploying a Python Application Deploying a Docker Application Deploying a Static Site App Detail Page Domains & SSL Environment Variables PHP Configuration App Logs Load Balancing Deleting an Application App Recipes

Databases

Creating a Database Managing Database Users Browsing Data & Running Queries Export & Import Linking Databases to Apps Database Discovery Database Replication

Backups

Backup Destinations Creating a Backup Managing Backups Restoring from a Backup

File Management

File Manager File Operations SFTP Accounts

Git & CI/CD

Connecting Your GitHub Account Git Deployments Auto-Deploy on Push Deployment History & Rollback

Teams

Managing Teams Team Members Whitelabel Branding

Settings

Profile and Security Audit Log

Web Terminal

Web Terminal

Reference

Frequently Asked Questions Troubleshooting Glossary

Connecting Your GitHub Account

ServerPlane uses a separate GitHub OAuth connection for repository access. This is independent of any GitHub account you may have used to sign in to ServerPlane — the repo connection requests broader permissions so it can read your repositories, manage deploy keys, and register webhooks.

What Permissions Are Requested

When you connect GitHub for repo access, ServerPlane requests the following OAuth scopes:

  • repo — Full access to your public and private repositories. This is required to clone code, add deploy keys, and create webhooks.
  • read:org — Read-only access to your organization memberships. This allows ServerPlane to list repositories from organizations you belong to.

Connecting Your Account

  1. Navigate to any app's detail page and open the Git & Deploy tab.
  2. You will see a Connect GitHub button with the GitHub logo. Click it.
  3. You will be redirected to GitHub's authorization page. Review the requested permissions and click Authorize.
  4. GitHub redirects you back to ServerPlane. Your connection is saved to your user account.
  5. The Git & Deploy tab now shows a repository browser instead of the connect button.

Once connected, GitHub access is available across all your apps — you only need to connect once.

Disconnecting Your Account

To revoke ServerPlane's access to your repositories:

  1. Go to GitHub Settings > Applications.
  2. Find the ServerPlane OAuth application under Authorized OAuth Apps.
  3. Click Revoke to remove access.

This revokes access on GitHub's side. Any apps that were connected to a repo will retain their existing configuration, but new repo connections will require re-authorization.

Troubleshooting

  • "Failed to load repositories" — Your connection may have expired or been revoked. Disconnect and reconnect your GitHub account.
  • Private repos not showing up — Make sure you granted the repo scope. If you denied it during authorization, revoke the app on GitHub and reconnect.
  • Organization repos missing — If your organization has OAuth app restrictions enabled, an org admin must approve the ServerPlane OAuth app before org repos will appear.

Previous

SFTP Accounts

Next

Git Deployments