Skip to main content

Common VPS Actions

This page explains the most common control actions you may use for a VPS after it becomes active in Dash.

VPS controls can vary depending on the VPS type, operating system, template, or current service state. Always use the visible controls in Dash as the source of truth for your specific service.

Before using any action​

Before performing any control action, always confirm:

  • you selected the correct VPS
  • the service is active or otherwise in a controllable state
  • there is no billing issue affecting access or management
  • no important workload will be interrupted unexpectedly

This is especially important for production environments.

Start a VPS​

Use the start action when your VPS is powered off and you want to bring it online.

Before starting the VPS, make sure:

  • the service is active
  • the selected VPS is the correct one
  • the power state shown in Dash matches what you expect

After the action is completed, allow a short time for the VPS to become fully available.

Stop a VPS​

Use the stop action when you want to shut down the VPS.

Stopping a VPS may interrupt:

  • running applications
  • active connections
  • scheduled tasks
  • background processes

Before stopping the VPS, make sure:

  • important work is saved
  • no critical task is running
  • the interruption is expected

Restart or reboot a VPS​

Use restart or reboot when the VPS is online but needs to be restarted.

This is commonly used when:

  • system changes require a reboot
  • the server becomes unstable
  • software updates require a restart
  • troubleshooting requires a clean reboot

A reboot is often the first recovery step before moving to more disruptive actions.

Reinstall the operating system​

Use reinstall when you want to deploy the operating system again from a clean state.

This action is destructive.

Before reinstalling:

  • back up important files
  • confirm that you no longer need the current system state
  • verify that you selected the correct operating system
  • make sure you selected the correct VPS

A reinstall may erase existing data and return the VPS to a fresh state.

Reset access credentials​

Some VPS services may provide options for resetting the main access credentials.

This is commonly used when:

  • you lost the current password
  • access details need to be refreshed
  • credentials must be rotated after a change

After resetting credentials, always store the new details securely.

Review IP and access details​

One of the most common tasks after activation is reviewing the current access information for the VPS.

This may include:

  • main IP address
  • login username
  • password or reset path
  • access port if applicable
  • console availability

Always verify that you are using the latest access details shown in Dash.

Open the server console​

If console access is available, it can help when normal remote access is not working.

Depending on the service, Dash may provide one or more console methods.

Console access is useful when:

  • SSH or RDP is unavailable
  • network settings inside the VPS were changed incorrectly
  • you need direct access during troubleshooting
  • you want to inspect boot behavior

Use console access carefully, especially on active systems.

Some VPS services may provide additional recovery-related controls such as rescue-style tools or related recovery options.

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

  • the VPS is no longer reachable normally
  • operating system access is broken
  • boot or network behavior inside the VPS needs recovery work

Not every VPS will show the same recovery options. Always treat the visible actions in Dash as the source of truth for that service.

Check resource usage​

Another common action is reviewing the service statistics.

This helps when you want to:

  • understand current server load
  • detect unusual usage
  • investigate slow performance
  • confirm whether the selected plan still matches your needs

If resource usage remains high for long periods, you may need to review your workload or consider a different plan.

Confirm billing and renewal status​

Operational issues are sometimes caused by service lifecycle or billing state rather than the VPS itself.

Check the billing section when you need to confirm:

  • whether the service is active
  • whether an invoice is overdue
  • the next due date
  • whether renewal is expected

Check service state before assuming a problem​

If an action is unavailable, disabled, or does not complete as expected, first review:

  • current service status
  • any visible billing issue
  • whether the VPS is still provisioning
  • whether the action is available for that specific VPS type

In some cases, the issue is not with the action itself, but with the current state of the service.

When an action does not work​

If an action fails or the result is not reflected in Dash:

  • refresh the page
  • wait briefly and check again
  • confirm the current service status
  • review billing state
  • verify that the action is available for that service

If the issue continues, contact support and include:

  • service ID
  • the exact action you attempted
  • the current visible service status
  • any error message shown in Dash