Get Better Help with a Minecraft Server Problem

You get disconnected just as you reach your base. Rejoining does not help, and “the server is broken” is the only message you can think of. A useful report can turn that frustrating moment into something the server team can investigate: what happened, where it happened, and what they should look for.

Start with the exact error, your edition and game version, the time of the problem, and the action just before it. Add a screenshot if it shows something important. You do not need to diagnose the cause, understand a crash report or write a technical essay.

Jump to: Quick checks · Copyable report template · Useful examples · Screenshots and clips · Java logs · Where to send it

Before sending a report, answer three questions

Is there already an announcement?

Check the server’s own status page, announcements or support channel for maintenance and known problems. If the team has already announced a restart, follow that thread rather than opening another “cannot join” ticket. You can still add information when your symptoms differ or continue after the announced fix.

Does it affect just this server?

If practical, try another server you already trust, or ask a friend whether they can join the affected one. Write down the result: “I can join our other server; this one disconnects me” is useful. It narrows the situation without pretending you have proved who is at fault.

For a modded server, also check that you launched its required modpack profile. A single-player world opening successfully does not prove that your client matches the server. If the error explicitly says the game version is incompatible, use our Java server version-mismatch guide before changing unrelated settings.

What exactly stopped working?

Separate a connection error from an in-world problem. “I cannot connect,” “blocks reappear after I break them,” “the game closes when I open this chest,” and “I cannot build in my claimed area” give the team different places to start. Report what you observed; do not label all four as lag.

A kick message about a whitelist, ban or permission is also useful evidence. Follow the server’s access or appeal route rather than assuming the service is offline.

A report you can copy and fill in

Use the server’s own form when it has one. Otherwise, copy this short structure into a ticket or support message and leave out fields that do not apply.

Title: [What fails] when [action or location]

Game: [Java or Bedrock] · [exact version] · [device/operating system]

Server or world: [server name, game mode, Realm or friend’s world]

When: [date, local time and time zone]

What I did:
1. [First action]
2. [Next action]
3. [The point where it failed]

Expected: [What should have happened]

Actually happened: [What you saw, including the exact error]

How often: [Once, every attempt, or sometimes; number of attempts if known]

Already tried: [Action → result]

Attachments: [Screenshot, short clip, or log requested by support]

A good title might be “Disconnected when entering the Nether from the town portal.” It is much more useful than “HELP!!!” because the administrator can recognize the affected action before opening the message.

Write the exact installed version, not “latest.” Java snapshots, Bedrock Preview builds and stable releases are different. On a modded setup, include the modpack name and pack version; the Minecraft version alone does not identify the pack.

Three examples that help support act

The following are fictional examples. Replace their details with what actually happened in your game.

Example 1: a disconnect at one portal

“On Java, using the server’s required pack, I can play in the Overworld. At about 19:40 UTC+2, entering the town’s Nether portal returned me to the server list with ‘Connection lost.’ It happened on both attempts. My friend stayed connected in the Overworld. I have attached the full error screen and can send the portal coordinates privately.”

This tells the team that joining works, identifies the transition that fails and gives them a time to compare with server records. It does not guess that the Nether is corrupted or claim that everyone was disconnected.

Example 2: missing items after a rollback

“After the restart around 21:10 UTC, the iron I moved into the storage-room chest was missing and my last few block placements had reverted. I was in Survival in the Overworld. I noticed this once after reconnecting. I have a screenshot of the chest location, but no recording of the transfer.”

List the items and approximate quantities you remember, and say when you last saw them. Be honest about missing evidence. A screenshot of an empty chest shows its present state; it cannot prove what was inside before the restart. The server’s restoration policy determines what the team can return.

Example 3: a modpack crash

“The game closes when I open the quest book after joining. I am using pack version [exact version] from the server’s instructions. It happens every time after entering the lobby, before I move anywhere. Restarting the same profile did not help. I have the crash report and the log from that session.”

Say whether you added or removed anything from the pack. If the server requires a particular setup, do not remove random dependencies from it to chase a fix. Keep your working profile intact and follow the pack’s support instructions.

Capture the detail that answers a question

For an error screen, include the whole message and any extra lines below the heading. A cropped image containing only “Disconnected” often removes the useful part. For a building problem, show the affected block or machine and enough of the surroundings to identify it.

A short clip is better for a sequence: an item disappears after a click, a minecart stops at one junction, or a portal sends you back. Start recording just before the action and stop once the problem is visible. You do not need a long video of unrelated gameplay.

In Java, F2 captures the game view when the game window is active; some keyboards require Fn+F2. If you are looking at a launcher error or the game has already closed, use your device’s screenshot tool instead. Bedrock players can use their device’s normal capture controls.

Keep private chat, account details, invite codes and hidden-base coordinates out of public screenshots. Send exact locations through the server’s private ticket system when they are needed. Do not crop away the error itself while hiding unrelated details.

When Java support asks for a log

A screenshot explains what you saw; the log records what the game was doing. If support asks for it, use the affected profile’s logs/latest.log. A generated crash report is a separate file under crash-reports. Share the files from the failed session, not an unrelated later launch.

For the official launcher’s default game folder:

• Windows: %appdata%\.minecraft
• macOS: ~/Library/Application Support/minecraft
• Linux: ~/.minecraft

A custom profile or another launcher can use a different folder. Use its folder or log-opening action rather than assuming the default path. Fabric’s log guide explains these locations.

Keep an untouched local copy. Review what you share for private messages, credentials or other sensitive details, and use the support channel’s requested upload method. Send readable text or the file, not dozens of screenshots of a log. An exit code alone usually does not explain the failure.

Bedrock players: do not hunt for Java’s .minecraft log folders. Start with your exact game build, device, error and reproduction steps. Supply additional diagnostics only when the relevant support team explains what it needs for your platform.

Send the report to the team that can change the problem

• One community server: its administrators handle access, plugins, world-specific problems, item recovery and local rules. Use their designated support route.
• A particular mod or modpack: use its official support or issue tracker. Include the pack version and required logs. Server-specific behavior may still need the administrator first.
• Account access or a purchase: use Minecraft Help. A public bug report is not an account-recovery request.
• A reproducible problem in Minecraft itself: read Mojang’s bug-report instructions and search for an existing report before adding another.

You do not need to determine the responsible mod or diagnose the network before asking for help. Describe the setup accurately and let the receiving team redirect you if necessary. Server rules and behavior added by plugins are not automatically Minecraft bugs.

Follow up without starting the investigation over

Keep new information in the same ticket. If someone suggests a check, reply with both the action and result: “I launched the requested profile, tried the same portal and got the same error” is useful; “still broken” leaves them guessing.

Change one relevant thing at a time. Avoid deleting worlds, resetting a profile or reinstalling everything merely to make the report look thorough. Those changes can remove the setup that caused the problem and create new ones.

When the issue is resolved, add the successful fix and whether it stayed fixed after reconnecting. If you cannot reproduce it any more but do not know why, say that. The next player with the same problem benefits from an accurate conclusion more than an invented explanation.