SSH access allows you to run the GitHub Enterprise command line utilities and is useful for troubleshooting, running backups, and configuring replication.
In this guide
- About administrative shell access
- Enabling access to the administrative shell via SSH
- Connecting to the administrative shell over SSH
- Accessing the administrative shell using the local console
- Access limitations for the administrative shell
If you have SSH access to the administrative shell, you can run GitHub Enterprise's command line utilities. SSH access is also useful for troubleshooting, running backups, and configuring replication. Administrative SSH access is managed separately from Git SSH access and is accessible only via port 122.
To enable administrative SSH access, you must add your SSH public key to your instance's list of authorized keys.
Tip: Changes to authorized SSH keys take effect immediately.
In the upper-right corner of any page, click .
In the left sidebar, click Management Console.
Under "SSH access", paste your key into the text box, then click Add key.
- Under the left sidebar, click Save settings.
After you've added your SSH key to the list, connect to the instance over SSH as the
admin user on port 122.
ssh -p 122 email@example.com Last login: Sun Nov 9 07:53:29 2014 from 169.254.1.1 admin@github-example-com:~$ █
In an emergency situation, for example if SSH is unavailable, you can access the administrative shell locally. Sign in as the
admin user and use the password established during initial setup of GitHub Enterprise.
Administrative shell access is permitted for troubleshooting and performing documented operations procedures only. Modifying system and application files, running programs, or installing unsupported software packages may void your support contract. Please contact GitHub Enterprise Support or GitHub Premium Support if you have a question about the activities allowed by your support contract.