Troubleshooting problems

If you’re spotting any issues, there are a couple of reasons it could be happening.

The server crashes

Sadly, servers sometimes go down. The most common reasons are:

• The server is using too many resources for the number of players.
• There’s something wrong with your build configuration.

If it’s simply a provider issue, we’ll automatically start sending playing to a different provider. But if it’s your configuration, get in touch with our support team.

The servers fail to start

Servers can sometimes fail to boot up. If so, you won’t be able to spin up any session. There are a couple of reasons this might happen:

• There’s something wrong with your build executable.
• You don’t have access to the region you’re calling.

In either case, the first step is to check the API response. If it’s a region problem, the API will tell you. If it’s a problem with your build, get in touch with our support team.

Note

Checking logs. The first port of call is to head to your logs. This will help us diagnose the problem. (Check our section on getting your logs if you don’t already know how to do it.)

New sessions or containers can’t start

If you’re finding that you can’t seem to start new sessions or containers, it’s typically because there’s an issue in the region. Either you don’t have permission to spin up a session there or the region is currently experiencing a problem.

Check with your support team to make sure you have the right permissions.