Need Assistance?

We’re here to help you get the most out of your GPU machine.

Contact Support

Email us at support@gamepc.io

Helpful Resources

Common Problems

Connection Problems

Symptoms

  • •Browser warns about the certificate when opening Studio
  • •SSH says Permission denied (publickey)
  • •Studio or SSH times out

What to try

  • ✓The certificate warning is expected the first time: choose Advanced, then Proceed
  • ✓Add your public key to ~/.ssh/authorized_keys from a Studio terminal, then log in as root
  • ✓Check the machine shows Running in your dashboard
  • ✓Contact support with the machine ID if it still fails
GPU or Software Issues

Symptoms

  • •torch.cuda.is_available() returns False
  • •CUDA out of memory errors
  • •A package or tool is missing

What to try

  • ✓Run nvidia-smi in a Studio terminal to check the GPU is visible
  • ✓Lower the batch size, or deploy a tier with more VRAM
  • ✓Install it: you are root, so pip install or apt-get install works
  • ✓Contact support if nvidia-smi shows no GPU
Machine Won't Start

Symptoms

  • •Machine is stuck in a starting state
  • •Dashboard shows a failed status
  • •Start button is not responding

What to try

  • ✓Wait a few minutes — a deploy not running after 10 minutes is cancelled and not charged
  • ✓Check you have at least $1.00 of credit
  • ✓If the tier is out of stock, try another tier
  • ✓Contact support if the issue persists
Billing Questions

Symptoms

  • •Unexpected charges on your account
  • •Credit balance not updating
  • •Need to request a refund

What to try

  • ✓Review your usage history in the billing dashboard
  • ✓Remember that running time is charged by the second, at the tier's hourly rate
  • ✓Stop machines when not in use to avoid ongoing charges
  • ✓Contact support for billing disputes or refund requests

Get Help Faster

When contacting support, include as much of the following as possible:

  • ✓Your Machine ID (found in the dashboard)
  • ✓Screenshots or screen recordings of the issue
  • ✓Steps to reproduce the problem
  • ✓Whether you were using Studio or SSH, and any error message you saw