Docs
Remote access

Remote access

All of Latitude.sh's servers feature Intelligent Platform Management Interface (IPMI) so your server can be managed remotely. You can access your server's IPMI through the browser or CLI. Remote access allows you to manage your server even when it's off or unresponsive.

Remote Access is included at no cost.

Connecting to the VPN

The first step is to connect to our internal network via VPN. This is needed because IPMI runs on private IPs.

  1. On the Servers page, select the server you'd like to access, click on Actions and select Remote access.

Server actions on the Latitude.sh dashboard.

  1. Click on Create VPN session to get credentials for the VPN. Note that the password is only shown once. Every time you create a new VPN session the password will change.

VPN credentials section on the Latitude.sh dashboard.

  1. Use the credentials provided to connect to our network using the VPN client you downloaded.

VPN credentials section on the Latitude.sh dashboard.

  1. Save the connection, insert the username and password provided and click on Connect.

Connecting to the IPMI

Now that you have established a VPN tunnel between your computer and Latitude.sh's internal network, you're ready to connect to the IPMI.

  1. On Step 2 in the Remote Access page, click on Retrieve IPMI credentials. This will give you the private IP, username, and password for your server's IPMI.
  2. Copy the username and password and paste the IP Address on your browser window.

VPN and IPMI credentials on the Latitude.sh dashboard.

  1. On the IPMI login screen, insert the username and password provided.

Troubleshooting

openfortivpn

ErrorCauseFix
Sorry, try againBad username or passwordMake sure you're using the correct username and password as shown in the dashboard. Passwords are ephemeral.
Sorry, try againIssues with daemonRestart daemon: sudo launchctl stop openfortivpn && sudo launchctl start openfortivpn
Gateway certificate validation failedConnection refused due to lack of certificateAdd the trusted-cert line to your configuration file or append it to the auth command.