Skip to main content

Troubleshooting

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

GPU Dedicated Server behavior can vary depending on the provider, hardware setup, and available management features. Always use the current status and controls shown in Dash as your primary reference.

Server is not active after payment​

If payment is completed but the server 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 service appears in your GPU Dedicated Server list

GPU Dedicated Servers may take longer to provision than VPS services because physical preparation, GPU validation, and final deployment checks may be involved.

If the delay continues, contact support and include:

  • invoice number
  • service ID if available
  • selected server
  • selected location

Cannot connect to the server​

If you cannot access the server:

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

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

Server is online but not responding normally​

If the server appears active but behaves unexpectedly:

  • restart the server 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.

GPU workload is not performing as expected​

If a GPU-related workload is running but performance is lower than expected:

  • confirm that your software stack is configured correctly
  • review CPU, RAM, and storage usage
  • check whether another system resource is limiting the workload
  • confirm that the selected server matches the intended workload
  • review whether the issue is related to application setup rather than the platform itself

Performance behavior can depend on workload design, software configuration, data handling, and resource balance across the full server environment.

Power action does not work​

If a power-related action such as power off or reboot does not complete:

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

Not every GPU Dedicated Server includes the same management capabilities. Some available actions depend on the provider or deployment model.

Reinstall is unavailable or not suitable​

If you expected a reinstall option but do not see one, it may not be available for that specific server.

If reinstall is available but you are unsure whether to use it:

  • treat it as a destructive action
  • back up important data first
  • confirm that other recovery steps are no longer suitable

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

IPMI or low-level access issues​

If IPMI access is available for your server but is not working as expected:

  • confirm that you are opening the correct service
  • check whether the service is fully active
  • refresh Dash and try again
  • review whether there is any provider-side delay or temporary issue

If low-level access is not shown at all, it may simply not be exposed in Dash for that server.

Console access availability​

Some GPU Dedicated Server services may include console-based access, while others may not.

If console access is shown, it can help when:

  • remote login is unavailable
  • network settings inside the server were changed incorrectly
  • you need direct access during troubleshooting

If console access is not shown, that does not automatically mean the server is broken. It may be a provider-specific limitation or a service-specific design choice.

If the server 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 server itself is technically healthy.

When to contact support​

Contact support when:

  • the server does not activate after a reasonable provisioning period
  • access details appear correct but the server remains unreachable
  • power or billing actions fail repeatedly
  • the service state in Dash appears incorrect
  • you suspect a platform-side or provider-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