How to Fix “Badly Compressed Packet” on a Minecraft Server

Direct answer

A “badly compressed packet” disconnect means the receiver rejected compressed network data. Confirm matching versions and inspect compression, proxy and packet-transforming plugin settings before touching unrelated performance settings.

What it means

Compression packets must obey the negotiated threshold and protocol format. A nonstandard proxy configuration, version translator or networking mod can corrupt or misinterpret a compressed packet.

If you are a player

Test a clean client on the same Minecraft version as the server.
Record whether failure occurs while joining, changing servers through a proxy, or receiving a large data update.

If you run the server

Capture the first compression/decoder error from logs/latest.log and the proxy log, if one exists.
Verify the protocol and compression settings are documented for your server/proxy release; do not copy thresholds from another stack.
Temporarily remove packet-modifying plugins only on an isolated staging server to identify a conflict.
Compare a direct backend test against the proxy route without opening the backend to the public internet.

Confirm the fix: A successful fix permits repeated joins and normal inventory/chunk loading. Changing compression thresholds is a diagnostic experiment, not proof of root cause.

Important notes

Packet exceptions often wrap the real cause. Keep the full nested exception and identify the first plugin/mod/protocol component named in it.

References

Use the documentation for the exact software and release you run. These sources support the settings or diagnostic behavior used in this fix.

Was this article helpful?

Help us improve this article

Tell us what is missing, unclear, outdated, or incorrect. You can also suggest something we should add.