Common problems

The fastest route to a fix for the things that go wrong most often, with the likely cause for each.

Support2 min read

On this page
  1. Getting into your account
  2. Your server
  3. Buying, billing, and cancelling
  4. None of these

The problems that come up most often, grouped by where they bite. Each one names the usual cause and links to the page that fixes it.

Getting into your accountYour serverBuying, billing, and cancellingStart in the panelA check or a fix you can make yourselfCannot sign inPlayers cannot connectServer off or unreachableSSH or RDP will not connectForgot the root passwordBlocked your own addressOrdered, no server appearedInvoice will not payAdding a card firstCancelling a serviceA request to the teamYou file it, and the team acts on itLost authenticator deviceA support request:no recovery codesClosing the accountFiled by Close account,on Privacy & dataMore diskFiled as an enquiry,from the storage pageDropping an unpaid orderFiled by Cancel,on the Orders listStart in the panelA check or a fix you can make yourselfGetting into your accountCannot sign inYour serverPlayers cannot connectServer off or unreachableSSH or RDP will not connectForgot the root passwordBlocked your own addressBuying, billing, and cancellingOrdered, no server appearedInvoice will not payAdding a card firstCancelling a serviceA request to the teamYou file it, and the team acts on itGetting into your accountLost authenticator deviceA support request: no recovery codesClosing the accountFiled by Close account, on Privacy & dataYour serverMore diskFiled as an enquiry, from the storage pageBuying, billing, and cancellingDropping an unpaid orderFiled by Cancel, on the Orders list
The fourteen problems on this page, by who acts on them. Ten start in the panel, with a check or a fix you can make yourself. Four are requests the team acts on, even where a button in the panel files the request for you. Derived from the cards on this page.

Getting into your account

Your server

Buying, billing, and cancelling

None of these

If nothing above matches, work through Checking platform status first so you can tell the team what you already ruled out, then open a ticket with the server attached, the exact error, when it started, and what changed just before.

Need a server, or a hand with one?

Pick a plan to deploy a server, or open a ticket in the panel. Support runs 24/7/365.