There are a few common ways to restrict SSH access to your server but still allow our technicians to access your server.

Changed SSH Port or Requirement to Use sudo or su

In this case, please do the following:

1. Log into the management interface.
2. Click on "Device Manager"
3. Click on the server that is affected by your changes.
4. Click on "Edit" link on the "Device Metadata" section.
5. Input the changes in port, username, password, and any additional login directions that might be needed.

Firewalled or Restricted SSH connections to certain IP ranges

In this case, please be sure to allow the IP ranges:

67.202.100.0/23 (Chicago Offices)
10.252.0.0/24   (Edison, NJ Office)
10.254.4.0/24   (Corporate & Engineering Office)
2607:f128::/48  (For IPv6)

SSH Public Key Authentication Only

For CentOS Systems: We now have an RPM that can be installed to handle this automatically. See the following knowledge base article: Adding Support Staff SSH Keys using RPM.  If you use this method, the keys will update automatically when we publish a new version.

If you are not using CentOS or wish to maintain the list of keys manually, you can find the current key file here.

To use it, download and place the file at /root/.ssh/authorized_keys2 on your server.

Note: As our staff changes, we will update this list of keys.  We recommend that you check the file at the link above periodically for a new version.  The modification date is always listed in the comment at the top of the file.