Most Bedrock server problems have a small, identifiable cause: a stopped or overloaded server, mismatched game versions, an incorrect address or port, a firewall/router rule, an unstable Wi‑Fi link, or a client-side issue. Start by classifying who is affected, then check the server process, versions, address and configured ports before changing performance settings. Bedrock Dedicated Server normally uses port 19132 for IPv4 and 19133 for IPv6, but the values in server.properties are authoritative. Reduce player and simulation distances only after connectivity checks pass; those settings directly change server workload.
Why is my Minecraft Bedrock server lagging?
“Lag” can mean two different failures: the server is not processing the world quickly enough, or packets are taking too long to travel between a player and the server. Delayed block breaks, mobs freezing for everyone, and repeated rollbacks usually point to server workload or the host’s network. If only one player sees high ping while others play normally, investigate that player’s Wi‑Fi, device, or route first.
| What players see | Most likely area | First check |
|---|---|---|
| Every player experiences delayed actions or frozen mobs | Server workload, host CPU/RAM, or host network | Watch the server console, then lower workload settings one at a time |
| Only one player has high latency | That player’s Wi‑Fi, device, or Internet route | Test Ethernet or another network and close background traffic |
| Nobody can join | Stopped process, wrong address/port, firewall/router, or version mismatch | Confirm the process is running, then verify version and port |
| “Outdated Client” or “Outdated Server” | Protocol-version mismatch | Update the older side and align preview with preview or stable with stable |
| Server appears in a list but connection fails | Transport or release-specific defect, firewall, or forwarding | Verify the exact Bedrock build and review current release issues |
Do not begin by buying hardware or changing every setting at once. A controlled check identifies whether the fault is local to one player, shared by everyone, or preventing connections entirely.
How do I diagnose a Bedrock server that is lagging or timing out?
Use this order so each test removes a different class of failure. After every change, have one player reconnect and observe the console; changing several variables together makes the result impossible to interpret.
- Classify the symptom. Ask whether all players are affected, whether the problem is limited to one player, and whether anyone can join at all. Shared delay suggests the server or host path; an individual spike suggests that player’s connection or device.
- Confirm the server process is healthy. Watch the Bedrock Dedicated Server console while a player connects. A crashed process, restart loop, or world-loading error must be fixed before client-side tuning. Leave the console visible long enough to see whether the process completes startup and remains running.
- Check the game versions. “Outdated Server” means the server is older than the connecting client; “Outdated Client” means the client is older. Update whichever side is behind. A Preview client needs a compatible Preview server build, and a stable client should be paired with the corresponding stable server release.
- Verify the address and port. Use
localhostor127.0.0.1only for a same-computer test, the host’s LAN address for players on the same network, and the public address plus forwarded port for Internet players. Readserver-portandserver-portv6inserver.propertiesrather than assuming defaults. - Check firewall scope. The host firewall must allow the Bedrock server on the network profile being used. A rule that permits Private networks does not necessarily permit a connection when Windows identifies the network as Public. On Ubuntu, create firewall rules for the configured Bedrock ports using the distribution’s documented firewall procedure.
- Separate Wi‑Fi from server load. Temporarily connect the host to the router by Ethernet, or have the affected player test from another network. Ethernet is generally more stable than Wi‑Fi for a home-hosted server, but it cannot repair overloaded server ticks, a blocked port, or poor ISP routing.
- Reduce server workload. Change
max-players,view-distance, andtick-distanceone at a time, restart the server, and observe. These controls have direct performance impact, so record the original values before testing. - Remove client-side variables. Sign out of the player’s account and sign back in, restart the device and router, close background programs, and disable add-ons one at a time. If the connection improves after one change, restore other settings and isolate that variable.
- Handle same-PC Windows testing correctly. Windows can block a packaged game from reaching a local server through loopback. Stop the server, apply the loopback exemption, restart the server, and connect to
127.0.0.1:19132when that is the configured IPv4 port. - Check release-specific networking problems. If process status, versions, address, ports, firewall, and workload all check out, compare the exact build with current Bedrock release notes and Mojang issue reports. Some defects are tied to a particular release and will not be solved by repeatedly editing the router.
What ports and addresses should a Bedrock server use?
Bedrock Dedicated Server’s documented defaults are 19132 for IPv4 and 19133 for IPv6. Those are defaults, not guarantees: an administrator can change them in server.properties, and every firewall, router-forwarding rule, and player connection must then use the configured value.
Choose the address for your topology
| Players and host | Address to enter | What must be allowed |
|---|---|---|
| Same computer as the server | 127.0.0.1 (or localhost) and the configured port |
Windows loopback exemption may be required |
| Same home or office network | The host’s private LAN address and configured port | Host firewall must allow the local network profile |
| Players on the Internet | The host’s public address and forwarded port | Router forwarding and host firewall must both permit the port |
Do not forward a port to a computer whose private address changes. Reserve the host’s LAN address in the router or configure a stable local address, then point the forwarding rule at that address. If you change server-port or server-portv6, update every dependent rule and give players the new port.
Why a visible server can still reject connections
A listing or discovery result proves only that some announcement reached the player; it does not prove that the game session can complete. A stale forwarding rule, a firewall rule limited to the wrong profile, or a release-specific transport defect can leave a server visible but inaccessible. Test with one player on the same LAN and one outside the LAN to distinguish local reachability from Internet forwarding.
How do I fix “Outdated Client” or “Outdated Server”?
Those messages indicate that the client and server protocol versions do not match. Update the side named in the message, then restart it before testing again; changing ports or lowering view distance cannot correct a protocol mismatch.
When the message says “Outdated Server”
Install the Bedrock Dedicated Server release that matches the player’s current game version. Stop the old process cleanly, replace the server files according to the official installation procedure, and start it again so the console shows the new build.
When the message says “Outdated Client”
Update the player’s Bedrock application through the platform’s normal update channel. If the server was intentionally kept on an older release, the player must use a compatible client rather than a newer one.
Preview and stable builds
Preview clients and stable clients do not share every protocol change. Keep Preview clients with a compatible Preview server and stable clients with the corresponding stable server; do not assume that installing the newest file of either channel will make them interchangeable.
Which server settings reduce Bedrock lag?
Bedrock stores these controls in the INI-style server.properties file. Start with the three settings that most directly change the amount of work: player capacity, view distance, and tick distance. Change one value, restart, and measure the result before changing another.
| Setting | Documented default | What it changes | When to lower it |
|---|---|---|---|
max-players |
10 | Maximum simultaneous players; higher values increase performance impact | Players join successfully but shared simulation slows as the population rises |
view-distance |
32 chunks | How far world data is maintained and sent around players | Chunk generation or loading causes broad, repeatable pauses |
tick-distance |
4 chunks | Area receiving active simulation ticks | Mobs, farms, redstone, or other simulation-heavy areas cause stalls |
max-threads |
Not stated | Threading limit used by the server | Only after confirming a CPU/threading bottleneck and understanding the host |
server-port and server-portv6 |
19132 and 19133 | IPv4 and IPv6 listening ports | Only when a deliberate port change is needed; update firewall and forwarding together |
enable-lan-visibility |
Not stated | Whether the server is advertised for LAN discovery | When LAN discovery is confusing testing; direct LAN addresses remain clearer |
| Compression settings | Not stated | Trade CPU work against bandwidth use | Only after testing; compression changes can move the bottleneck rather than remove it |
Higher player counts and larger distances increase server work. Lower max-players first if the problem appears as additional players join; lower view-distance for chunk-related load; lower tick-distance when active simulation is the problem. Keep a copy of the original file so you can restore a known-good configuration.
Can Ethernet fix Bedrock rubber-banding?
Ethernet can stabilize the host’s local link and is a sensible test when Wi‑Fi is involved. It cannot fix a server that is missing ticks, a blocked or mis-forwarded port, a version mismatch, or congestion elsewhere on the Internet.
Use a controlled network test
- Connect the server computer to the router with Ethernet while leaving the server settings unchanged.
- Reconnect the same player and compare delayed actions, disconnects, and console activity.
- If the host improves on Ethernet, investigate Wi‑Fi signal quality, channel congestion, distance, and other traffic. If it does not, return to workload, firewall, forwarding, or release checks.
A player’s own Wi‑Fi can produce the same symptoms. Have that player test near the access point, then test through Ethernet or a different network. If other players remain smooth, do not lower global server settings to compensate for one player’s local link.
What should I check on the client when only one player has problems?
Client-side cleanup is appropriate when the server console is healthy and other players connect normally. Perform these actions in order and reconnect after each one.
- Sign out of the affected account and sign back in.
- Restart the game, device, and home router.
- Close background downloads, streaming applications, and other programs using the connection or CPU.
- Disable add-ons one at a time, noting which change affects the connection.
- Test the same account from another network or device to separate account data from local hardware and routing.
Do not treat general Windows-maintenance software as a Minecraft-specific fix. The useful troubleshooting actions are the observable ones above: closing background programs and restarting, followed by a controlled retest.
How do I connect to a Bedrock server from the same Windows PC?
Localhost testing can fail on Windows even when the server is running because the packaged Bedrock app may not have loopback permission. Apply the exemption before deciding that the server itself is unreachable.
- Stop the Bedrock Dedicated Server process.
- Open an elevated Command Prompt.
- Run
CheckNetIsolation.exe LoopbackExempt -a -n="Microsoft.MinecraftUWP_8wekyb3d8bbwe". The package identifier can differ for a particular installation; use the identifier documented for that installed Bedrock package if this one is not present. - Start the server again.
- In Bedrock’s server connection screen, enter
127.0.0.1and port19132, unlessserver-portspecifies another IPv4 port.
If local loopback works but LAN players cannot connect, the remaining problem is outside loopback: check the host firewall profile, LAN address, router isolation, and the configured port.
What hardware and bandwidth does a Bedrock server need?
The current Bedrock Dedicated Server download guidance lists 4 GB of RAM, 180 MB to 1 GB of storage, and a broadband Internet connection. Those figures describe installation guidance, not a guaranteed player capacity or latency target.
| Resource | Published figure or guidance | How to interpret it |
|---|---|---|
| Memory | 4 GB RAM | A baseline in the download guidance; world size, add-ons, players, and other host software can require more |
| Storage | 180 MB to 1 GB | Allow room for the server files and expanding worlds rather than treating the lower figure as a total lifetime requirement |
| Internet | Broadband connection | Upload stability and geographic route matter as much as headline speed for remote players |
| Bandwidth rule of thumb | About 5 Mbps upload and 10 Mbps download per 10 players | A Minecraft Wiki community estimate, not an official requirement or guarantee |
No independent benchmark establishes a universal Bedrock tick rate, latency threshold, or guaranteed player count for a particular CPU. Capacity depends on player activity, view and tick distances, world behavior, add-ons, and the host’s network path. Treat the published memory and bandwidth figures as planning inputs, then leave headroom instead of sizing a server to the exact minimum.
Should I host on a LAN or over the Internet?
LAN hosting removes the public routing and port-forwarding path, making it the simplest environment for diagnosis. Internet hosting gives remote players access but adds router configuration, firewall exposure, geographic latency, and an update process that the administrator must maintain.
| Factor | LAN | Internet |
|---|---|---|
| Address | Private host address | Public address plus forwarded configured port |
| Exposure | Limited to the local network | Reachable from outside; firewall and router rules are essential |
| Latency | Usually limited by local Wi‑Fi or Ethernet | Also affected by ISP routing and player geography |
| Troubleshooting | Start with process, version, LAN address, and firewall | Add forwarding, public address, and external-network tests |
| Maintenance | Local operating-system and game updates | All LAN tasks plus public port management, backups, and remote availability |
For a remote group, a managed host can remove operating-system, firewall, forwarding, and update maintenance, but evaluate any provider by capacity, server location, backup policy, and update policy. Those factors affect the experience more directly than a marketing player-count claim.
What if ordinary port and version checks pass?
Bedrock networking defects can be release-specific. Bedrock 26.40 included a fix for a NetherNet probe timeout, and Mojang issue BDS-23108 documents a version-specific transport setting that could make a server visible but inaccessible. Verify the exact client and server build before changing transport settings, and use the release notes or issue tracker for that build.
Do not copy a transport workaround from a different release without confirming that it applies. A setting that addresses one build’s defect can create a new incompatibility on another build. If a newly installed release introduced the failure while the network and configuration are unchanged, record the build number and compare its documented issues before rolling back or editing advanced settings.
How can I prevent recurring Bedrock connection failures?
Keep a small operating record for the server: the Bedrock build, configured ports, LAN address, firewall profile, and the values of the workload settings. Before an update or configuration change, stop the server cleanly and copy the world and configuration files. After the change, test a local connection first, then a LAN connection, then one external connection if the server is Internet-facing.
- Keep clients and the server on the same release channel.
- Reserve the host’s LAN address so forwarding does not silently point to another device.
- Document every non-default port and firewall rule.
- Change one performance setting at a time and retain the prior value.
- Use Ethernet for the host when practical, while remembering that it does not replace capacity planning.
- Check release notes when a problem begins immediately after an update.
Frequently Asked Questions
Does changing the Bedrock server port make it faster?
No. A different port can avoid a conflict or match a network policy, but it does not increase tick capacity or reduce Internet latency. Every port change must be mirrored in the host firewall, router forwarding, and the address players use.
Why can friends on the same Wi‑Fi join while players outside my home cannot?
Local players use the host’s private LAN route, while remote players require the public address and router forwarding. Confirm that forwarding targets the host’s current private address and that the host firewall permits the configured port on the active network profile.
Can a larger view distance improve connection quality?
No. Larger view distance increases the amount of world data the server maintains and sends, which can increase workload and bandwidth use. It is a gameplay choice to tune after connectivity is proven, not a remedy for timeouts.
Should I disable all add-ons to fix rubber-banding?
Use add-ons as an isolation test, not a permanent assumption. Disable them one at a time, reconnect, and note whether the symptom changes; this identifies a problematic add-on without discarding unrelated content.