By default, which network port is used for administrative SSH access to a GitHub Enterprise Server appliance (distinct from user Git SSH)?
Select an answer to reveal the explanation.
Short Explanation and Infographic
On GHES, user Git-over-SSH and admin shell access are intentionally separated. Administrative SSH typically lands on port 122 so you can lock down who reaches the admin shell without fighting end-user Git traffic on 22. Open 122 only from bastion/jump hosts and keep MFA/SSH keys tight — that shell can reconfigure the whole appliance.
Full explanation below image
Full Explanation
The correct answer is port 122. GitHub Enterprise Server separates end-user Git SSH (commonly port 22) from the administrative shell used for commands such as ghe-repl-status, support bundle collection, and maintenance operations. Administrative SSH defaults to port 122. Option B is incorrect because conflating admin and Git SSH reduces the ability to apply different firewall rules. Option C is wrong: 8443 is associated with HTTPS Management Console access, not admin SSH. Option D is wrong: 9418 is the unauthenticated git protocol port and is not the admin shell. Network design should restrict 122 to jump hosts, require key-based auth, and monitor admin shell usage via audit and host logging.