Skip to content

Troubleshoot a VPS provisioning or connection problem

Separate provisioning, ownership, boot, firewall, and application failures.

Before you start

Keep the service ID and time of the failure. Do not deploy duplicate servers while investigating.

Steps

  1. Open the service under the correct customer account and inspect provisioning state and any displayed error.
  2. If the VM is running, confirm its current assigned address and connect through SSH or the supported web console.
  3. Inspect the guest’s network configuration, SSH service, firewall, and listening application ports.
  4. If the VM appears missing, check account selection first. Do not claim or transfer another user’s provider resource.
  5. Open a support ticket with the service ID, region, action attempted, and a redacted error message. For a paid order, include the related billing identifier.

Check the result

You know whether the failure is in ordering, provider provisioning, guest boot, networking, or the application.

Troubleshooting

A provider outage or missing service cannot be repaired by repeatedly clicking Start. Support should reconcile ownership and billing before any replacement or retry.

Last updated October 12, 2026. Availability and prices are shown in the console before checkout.
Still need help? Open a support ticket with your service name, the time of the issue, and a redacted error message. Never include passwords or API keys.