Skip to main content

Troubleshooting

This page covers common VPS issues and the first checks you should make before contacting support.

Always use the visible service status, billing state, and management options shown in Dash as your primary reference.

VPS is not active after payment​

If payment is completed but the VPS is not active yet:

  • refresh Dash and check the service again
  • confirm that the related invoice shows as paid
  • allow a reasonable provisioning window
  • verify that the VPS appears in your VPS list

Standard VPS services are often prepared shortly after payment, but the exact timing can still vary depending on the VPS type and selected options.

If the delay continues, contact support and include:

  • service ID
  • invoice number if relevant
  • the VPS type you ordered
  • the selected location

Cannot connect to the VPS​

If you cannot access the VPS:

  • confirm that the service is active
  • verify that you are using the correct IP address
  • check that the login method matches the installed operating system
  • confirm that your local network is not blocking the connection
  • review whether the issue started after a firewall, network, or system change inside the VPS

If the VPS was reachable before and stopped responding after internal configuration changes, the issue may be inside the operating system rather than in the platform itself.

Wrong username or password​

If access is denied:

  • check that you are using the latest credentials shown in Dash
  • make sure there are no typing mistakes
  • confirm that the correct login method is being used
  • use a password reset option if it is available for that VPS

If you recently changed credentials, make sure you are not using older access details.

VPS is online but not responding normally​

If the VPS appears active but behaves unexpectedly:

  • restart the VPS if that action is available
  • review recent changes made inside the operating system
  • check whether CPU, RAM, or storage usage is unusually high
  • confirm that important services or applications are still running

Issues like this are often related to software configuration, resource pressure, or operating system changes.

High resource usage​

If the VPS becomes slow or unstable:

  • review CPU usage
  • review memory usage
  • review storage usage
  • check whether workload demand has increased
  • confirm that background processes are behaving normally

If usage remains high over time, the current VPS plan may no longer match the workload.

Power or control action does not work​

If a start, stop, reboot, reinstall, or another control action does not complete:

  • refresh the page
  • wait briefly and check the service again
  • confirm that the VPS is still in an active or manageable state
  • review whether there is a billing issue
  • verify that the action is available for that specific VPS type

Not every VPS will show the same controls. Some actions may depend on the VPS type, operating system, or current service state.

Console or recovery access​

Some VPS services may provide console-based access or recovery-related controls.

If these options are shown in Dash, they can help when:

  • normal remote login is unavailable
  • network settings inside the VPS were changed incorrectly
  • the operating system needs recovery work
  • you need direct access during troubleshooting

If a console or recovery option is not shown, use the visible controls in Dash as the source of truth for that service.

If the VPS becomes unavailable and you suspect a billing issue:

  • review the billing tab
  • confirm the current invoice status
  • check the due date
  • verify whether payment has been fully applied
  • confirm that no cancellation action has already been submitted

Billing and lifecycle state can affect service availability even when the VPS itself is technically healthy.

Reinstall concerns​

Before using reinstall, remember that it may erase existing data.

If you are troubleshooting a broken system and considering reinstall:

  • back up important files first
  • confirm that other recovery steps are no longer suitable
  • make sure you selected the correct VPS

Reinstall should usually be treated as a later recovery step, not the first response to every issue.

When to contact support​

Contact support when:

  • the VPS does not activate after a reasonable provisioning period
  • access details appear correct but the VPS remains unreachable
  • power or billing actions fail repeatedly
  • the service state in Dash appears incorrect
  • you suspect a platform-side issue

When opening a support request, include:

  • service ID
  • invoice number if relevant
  • a short description of the issue
  • the exact action you attempted
  • any visible error message