Roastd / Minecraft

warning

The server ended this session

Applies to the game client.

What it looks like in your log

Client disconnected with reason: Disconnected

What causes it

The connection was closed from the server side, in this log during protocol negotiation. On modded servers that usually means the client pack does not exactly match the server; otherwise it is a kick or a server-side problem.

How to fix it

Check the server log at the same timestamp for the reason. On a modded server, make sure the client runs the exact same pack version; if everyone drops at once, the server is the place to investigate.

Why it happens

This is a client log line: the server closed the connection and told the client why, or did not. "Disconnected" with no reason is the server dropping the session during the protocol handshake, which on a modded server almost always means the client pack does not match the server pack, and on any server can be a kick, a timeout or a server-side crash at that moment.

The client log only ever shows the client half. The reason is in the server log at the same timestamp.

Fix it step by step

  1. 1Get the server log for the same minuteThe server logs the disconnect with the real reason: a kick, a mod mismatch, a timeout, a whitelist rejection. Match the timestamps.
  2. 2On a modded server, compare pack versionsClient and server must run the same pack version with the same server-side mods. A client on 1.2.3 and a server on 1.2.4 disconnect exactly like this. Reinstall the pack from the same page on both sides.
  3. 3If everyone dropped at onceThe server restarted, crashed or lost its network for a moment. Read the server log; the client logs will all say the same thing.
  4. 4If only one player dropsTheir connection, their client version or their mods. Ask them for the server log line at their timestamp.

If that didn't work

"Connection closed during protocol change" is the same event caught one step later, when the server rejected the transition to the play state. Same diagnosis.

Not sure this is your problem? Paste your log and Roastd will tell you which of these it actually matched, and what else it found.

Check your own log

Errors that travel with this one