Skip to content
AleForge
Back to Homepage

Fix Keepalive Timeout When Joining Server

You join a server, teleport to a new area, or walk into a busy build, and your game suddenly freezes. Chunks stop loading, you cannot break blocks or open menus, and after 15 to 30 seconds you are kicked to the multiplayer screen with an error like Timed out or keepalive timeout.

This guide covers client-side disconnects caused by your game freezing or failing to respond to the server. If you are a server owner troubleshooting server-side connection issues, see Read Timed Out Errors instead.

What a Keepalive Timeout Means

Section titled “What a Keepalive Timeout Means”

Minecraft constantly checks that your client is still connected. A keepalive timeout means the server stopped receiving a response from your game. Your client stopped replying, usually because it froze completely.

This is different from a normal server kick. The server is often still running fine; your game just could not keep up.

Common Symptoms

Section titled “Common Symptoms”
  • The game freezes after joining or teleporting
  • Chunks stop loading or render as empty space
  • You cannot interact with blocks, entities, or menus
  • You are disconnected after 15 to 30 seconds
  • The disconnect message mentions Timed out or keepalive timeout

Why It Happens

Section titled “Why It Happens”

Most keepalive timeouts on join fall into one of three categories:

  1. Not enough RAM: Your client runs out of memory while loading many chunks, entities, or custom content at once.
  2. Network overload: Your connection struggles to download a large burst of chunk and entity data.
  3. Incompatible client mods: Mods that alter protocol handling can break custom server content from plugins like ItemsAdder or Oraxen.

Work through the fixes below in order. Step 1 resolves the issue for most players.

Step 1: Increase Your Allocated RAM

Section titled “Step 1: Increase Your Allocated RAM”

When you teleport into a busy area, Minecraft may need to load hundreds of blocks, entities, and custom models instantly. If your launcher does not have enough memory, the game can freeze hard enough to trigger a timeout.

Aim for at least 4096 MB (4 GB). Modded clients and servers with custom resource packs often need 6144 MB (6 GB) or more.

Prism Launcher / CurseForge / Modrinth App

Section titled “Prism Launcher / CurseForge / Modrinth App”
  1. Open your instance or profile settings.
  2. Go to Settings → Java / Minecraft (or Memory).
  3. Increase Maximum Memory to 4096 MB or 6144 MB.
  4. Save and relaunch the game.

Vanilla Launcher

Section titled “Vanilla Launcher”
  1. Open Installations.
  2. Click the three dots on your profile and choose Edit.
  3. Click More Options.
  4. Find -Xmx2G at the start of JVM Arguments.
  5. Change it to -Xmx4G or -Xmx6G, depending on how much RAM your PC can spare.
  6. Click Save.

For detailed steps across other launchers, see How do I allocate more RAM to Minecraft?.

Step 2: Lower Your Render Distance

Section titled “Step 2: Lower Your Render Distance”

If your internet connection struggles with large bursts of data, high render settings can create a traffic jam between your client and the server. Lowering them before you join gives the game time to catch up.

  1. Before joining the server, open Options → Video Settings.
  2. Set Render Distance to 6 or 8 chunks.
  3. Set Simulation Distance to 5 chunks.
  4. Join the server and wait about 30 seconds for the area to finish loading.
  5. If performance is stable, slowly raise your settings again.

Also close bandwidth-heavy apps, downloads, streams, or VPNs on unstable routes, while joining busy areas for the first time.

Step 3: Disable Incompatible Client Mods

Section titled “Step 3: Disable Incompatible Client Mods”

Servers that use custom resource packs, custom blocks, or plugins like ItemsAdder or Oraxen send data your vanilla client does not understand. Some client-side mods make this worse by failing to translate custom packets correctly.

Temporarily remove or disable mods such as:

  • ViaFabricPlus
  • ViaForge
  • ItemFixer
  • Other protocol, proxy, or item-translation mods you did not install specifically for this server

After disabling them, restart your launcher completely and try joining again. Only use client mods that the server owner explicitly recommends.

Quick Checklist

Section titled “Quick Checklist”
Check What to do
RAM Set at least 4 GB; use 6 GB+ for modded or custom-content servers
Render distance Start at 6–8 chunks until the area loads
Client mods Remove ViaFabricPlus, ViaForge, ItemFixer, and similar mods
Server type Confirm you are on the correct Minecraft version and mod loader

Still Need Help?

Section titled “Still Need Help?”

If you have tried all three steps and still disconnect with a keepalive or timed out error, open a support ticket and include your latest client log:

  • Prism Launcher: Right-click the instance → Upload Log, then paste the link in your ticket.
  • Vanilla Launcher: Open the logs folder in your Minecraft directory and attach or paste the contents of latest.log.
  • CurseForge / Modrinth: Upload the crash or game log from the launcher’s log folder.

Include what you were doing when the disconnect happened (joining, teleporting, entering a specific area) and which fixes you already tried. That helps our team diagnose the issue faster.

Section titled “Related Guides”