How to Write a Game Server Support Ticket That Gets Fixed Fast

A support ticket gets fixed fast when it gives the host everything they need on the first read: which server, which game and version, the exact error text, the log lines around it, what changed just before it broke, and what you already tried. Most slow tickets are slow because the first reply has to ask for those things. Spend five minutes gathering them and you often get a fix in one message instead of three.

Why the first message matters

Support teams work through queues. A ticket that says "server broken pls help" gets a reply asking which server, what game, what error. You answer, it goes to the back of the queue, someone else picks it up and asks for logs. A full first message skips all of that.

What to include

1. Which server

• The server address (IP and port) or the server name exactly as it appears in your dashboard.
• The game and, if you know it, the server type: Paper or Fabric for Minecraft, Oxide or Carbon for Rust, tModLoader or TShock for Terraria.
• The account email if you are writing from a different address.

2. What is wrong, in one sentence

Describe what you see, not what you think the cause is:

• Good: "The server shows Running but nobody can connect, the client says Connection timed out."
• Less useful: "I think the port is blocked."

You can add your guess afterwards. Starting with the symptom stops support from chasing your theory.

3. The exact error text

Copy and paste, do not paraphrase. "Failed to verify username!" and "Outdated server! I'm still on 1.21.11" point to completely different fixes, and both get described as "can't join". If the error is on screen, take a screenshot as well.

4. Log lines

Logs are where the answer usually is. Paste the 20 to 50 lines around the first error, not the whole file. Where to find them:

If the server crashed, the most useful line is usually the first one with "Exception", "Error" or "FATAL" in it, plus the lines just before.

5. What changed

Almost every sudden problem follows a change. Say what it was and when:

• A game update came out today.
• You added or updated a mod or plugin.
• You edited a config file.
• You changed the server type or version.
• You restored a backup.
• Nothing changed, it just stopped (that is useful too).

6. When it started, with your time zone

"Since about 8 PM Eastern on Saturday" lets support match your report with their own logs.

7. What you already tried

List it so nobody asks you to do it again: restarted, removed the new mod, rolled back a backup, checked the version matches.

8. What a good outcome looks like

"I need to get the world back to how it was on Friday" is different from "I just need it to start". Say which.

A template to copy

Server: play.example-address:25565 (name: "Friday Survival")
Game and type: Minecraft Java, Paper 1.21.11

Problem: Server starts then stops after about 30 seconds. Nobody can join.

Exact error (from logs/latest.log):
[Server thread/ERROR]: Encountered an unexpected exception
java.lang.NoClassDefFoundError: ...
(lines 120 to 160 pasted below)

What changed: Added the plugin "ExamplePlugin 2.3" at about 7:40 PM Eastern.

Started: 7:45 PM Eastern, Saturday.

Already tried: Restarted twice. Removed ExamplePlugin, still crashes.

What I need: Server running again. Happy to roll back to last night's backup if needed.

Things that slow tickets down

• Several problems in one ticket. Split them, or number them clearly.
• Screenshots of text. Paste logs as text so support can search them. Use screenshots only for things that are not text.
• Sharing passwords. A good host never needs your account password. Never paste it in a ticket.
• Changing things while waiting. If you keep trying fixes, say so in the ticket, or support may be looking at a state that no longer exists.
• Opening duplicate tickets. It usually pushes you further back, not forward.

Try these first

Some problems you can solve before writing:

1. Restart the server and read the console from the first line. Many errors explain themselves.
2. Check the game version. After a patch, most "can't join" reports are a version mismatch. Update the server or wait for players to update.
3. Remove the last mod you added. If it starts, that mod is the cause.
4. Restore yesterday's backup if a config change broke things and you cannot find which. See how to restore a backup.
5. Check the game's own server status. Login services for Steam, Epic or Mojang go down sometimes, and that is not your server.

Our guide to why your game server is lagging covers performance problems the same way.

What good support looks like back

A good reply addresses your actual error, explains the cause in plain words, tells you what they changed, and says what to do if it happens again. If support only sends a generic article that does not match your error, reply quoting the exact line again and ask them to look at it.

Contacting GamezServers support

Email support@gamezservers.com any time; support runs 24/7. Include the server name from your dashboard and the details above, and paste console output from the Console tab or log files from the Files tab. If you have not got a server yet, pick a game and you will have a live console and file access from the first minute.

FAQ

How long should a game server host take to reply?

It varies by host and time of day. A good host replies to an outage in minutes to a few hours, and the more complete your first message, the fewer replies it takes to fix.

What logs should I send to game server support?

The 20 to 50 lines around the first error in the main server log, plus a crash report if the game wrote one. Paste them as text.

Should I give support my account password?

No. Support staff can reach your server from their side. If anyone asks for your password, check that the message really came from your host.

Is it OK to email support about a mod problem?

Yes, but say which mod and version, and expect help with getting the server to start rather than debugging the mod itself. Mod authors fix bugs in their own mods.