iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Godlike.Host offers hosted Minecraft Java servers with its own game panel, SFTP access and free DDoS protection, if you would rather not host it yourself.
When a Minecraft server stops working immediately after an update, the cause is usually one of four things: the client and server are on incompatible protocol versions, the server process fails during startup, the Java runtime is wrong for the Java Edition build, or a firewall/router rule no longer matches the configured port. Diagnose those in that order. Port forwarding cannot repair a server that never started, and changing world files before making a backup can turn a recoverable update problem into data loss.
This guide covers Java Edition servers and Bedrock Dedicated Server separately, then shows how to distinguish a local software failure from an internet-access problem.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchStart by identifying the edition, build and failure stage
Java Edition and Bedrock Dedicated Server are different server software products. A Java client cannot join a Bedrock server simply because both display the same game version, and the reverse is also true. Write down the exact edition, the client version, the server version, and whether either side is using a preview, snapshot or other test build.
Microsoft describes an “Outdated Client” or “Outdated Server” message as a protocol-version mismatch. Patch-level differences can matter, so matching only the first two numbers is not enough. Use the latest stable release on both sides unless you have a specific reason to run a preview or snapshot.
#1 Best Overall
| What you observe | Most likely stage | First check |
|---|---|---|
| The server window closes or shows an error before a “ready” message | Process startup, runtime or permissions | Launch from the server directory and read the first error |
| The server starts, but the world fails to load | World data or configuration | Stop, back up the world, then inspect the world-load error |
| You can join on the host computer but not from another device on the LAN | Local firewall, bind address or LAN routing | Test the host’s LAN address and check the firewall |
| LAN players can join, but internet players cannot | Router forwarding, public address or upstream NAT | Forward the configured port to the host’s current LAN address |
| An “Outdated Client” or “Outdated Server” message appears | Client/server protocol mismatch | Update both sides to the same stable release |
Protect the world before changing anything
Do not replace server files, edit configuration, or attempt a rollback while the process is still running. A clean stop ensures pending world data is written.
- Stop the server using its normal shutdown command or control, and wait for the process to exit.
- Copy the complete world folder to a separate backup location. Include every dimension folder used by that server.
- Copy the configuration files, server launch scripts and any custom plugins or mods you rely on.
- Keep the previous server directory intact. Do not overwrite it with the new release until the new installation has been tested.
- Record the old and new version numbers in the backup folder name so you can identify which files belong together.
Microsoft’s Bedrock guidance recommends separate directories for multiple versions. That arrangement also gives you a practical rollback path: each version has its own binaries, while the world backup is restored only after you have verified that the target server build can load it.
Confirm that the server process actually starts
Run the server from its own directory and leave the terminal or console open. Startup output is more useful than a launcher’s generic “server stopped” notification. Capture the first error after a clean restart; later messages are often consequences of the original failure.
Bedrock Dedicated Server on Windows
Microsoft documents launching the Windows server with the bedrock_server executable. Open a terminal in the directory containing that executable, start it, and watch for the normal startup sequence. If the executable is missing, blocked by the operating system, or exits immediately, fix that process-level problem before testing network access.
Bedrock Dedicated Server on Ubuntu
From the directory containing the Bedrock files, Microsoft documents this command:
LD_LIBRARY_PATH=. ./bedrock_server
Run it in the foreground while diagnosing the update. A missing library, permission error or incompatible binary will be visible in the terminal. Do not diagnose port forwarding until this command remains running and the server reports that it is ready for connections.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Java Edition startup
Use the launch script or command supplied for the exact Java server build, and verify that the terminal uses the Java installation you intend. If a third-party launcher or custom script points to a deleted or older Java executable, the update can fail before the world is opened. Keep the console visible so you can distinguish a Java runtime error from a world or configuration error.
Use the Java runtime required by your Java Edition build
Minecraft Java Edition 1.18 requires Java 17 when the server is using a custom Java runtime. A server may appear updated while the launch script still selects Java 8, Java 11 or another incompatible installation. The same applies to a launcher: changing Java on the desktop does not help if the server script uses a different path.
- Identify the Java executable selected by the server script, service definition or launcher.
- Run that executable’s version command and confirm it reports Java 17 or newer for a 1.18-era server.
- Make the launcher and the server script use the same intended installation, or deliberately document why they differ.
- Restart from a terminal and read the complete error if startup still fails.
Do not assume that installing a new Java version changed every environment variable or service account. The path configured in the actual launch mechanism is the one that matters.
Resolve an “Outdated Client” or “Outdated Server” error
The wording identifies which side needs attention. “Outdated Client” means the client is older than the server protocol it is trying to use; “Outdated Server” means the server is older than the client protocol. In both cases, the underlying issue is a mismatch, not a firewall failure.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Rank #3
- The classic UNO card game builds fun on game night with a Minecraft theme.
- UNO Minecraft features a deck and storage tin decorated with graphics from the popular video game.
- Players match colors and numbers to the card on top of the discard pile as in the classic game.
- The Creeper card unique to this deck forces other players to draw 3 cards.
- Makes a great gift for kid, teen, adult and family game nights with 2 to 10 players ages 7 years and older, especially Minecraft and video game fans.
- Close the game and identify the exact stable release installed by the client.
- Check the server console or server package name for its exact release.
- Update the older side, or intentionally install the matching server build for the client.
- Make sure a preview or snapshot client is not connecting to a stable server, or vice versa.
- Reconnect only after both sides report compatible versions.
Updating one side while leaving the other untouched is a common way to create this error. Even a patch release can change the protocol expected by multiplayer.
Audit server.properties after the update
Updates can add, rename or regenerate settings. Compare the new file with your backed-up copy instead of pasting an old file over it wholesale. Java release documentation specifies that server.properties is read and written as UTF-8; preserve that encoding when editing.
Check the connection settings
- Port: Record the exact port value. Firewall rules and router forwarding must use this value, not an assumed default.
- World or level name: Confirm that the configured name still matches the backed-up world folder.
- Authentication: Verify that the setting matches how your clients are authenticated. A changed authentication setting can prevent entry even when the process is healthy.
- Gameplay settings: Review values that the update may have regenerated. Do not discard newly introduced keys simply because they were absent from the old file.
- Bind or address settings: Keep documented defaults unless you have a specific networking requirement. Binding to the wrong local interface can make a running server unreachable.
Save the file, restart cleanly, and test from the host before changing the router. If the server reports an unknown or invalid property, restore only that key from the new release’s default rather than replacing the entire file.
Test locally before testing the internet path
A local test separates software problems from network problems.
Free tools Windows power users keep installed
One-click scans. No signup required.
- On the host computer, connect to the local address used by the server. For a same-machine test, use the local-loopback address supported by your client; for a second device in the house, use the host’s LAN address.
- If the local connection fails, return to the console. Check startup output, Java, world loading and
server.properties; port forwarding is irrelevant at this stage. - If the host works but another LAN device fails, inspect the operating-system firewall, the host’s LAN address and any bind/address setting.
- If LAN devices work, test from a genuinely external network, such as a phone hotspot. Testing from inside the same LAN may not exercise the router’s external forwarding behavior.
Keep a note of which test passed. “Works on the host,” “works on LAN,” and “works from outside” are different results and point to different fixes.
Rank #4
- Now Minecraft lovers can play a special version of UNO!
- Same as Basic UNO but features Minecraft characters and includes special Creeper rule card. Draw this card and the other players have to draw three more cards from the pile!
- The goal is to get rid of all the cards in your hand.
- First player or team to 500 wins.
- When you're down to one card, don't forget to yell "UNO"!
Open the firewall port that the server actually uses
For Bedrock Dedicated Server, Microsoft documents default ports 19132 and 19133. The values in your server.properties file take precedence if you changed them, and those actual values must be allowed through the host firewall. Do not open a port simply because it is a commonly quoted default.
- Read the configured port and protocol requirements from the server documentation for your edition.
- Create or update an inbound firewall rule for the server executable or service and the configured port.
- Apply the rule to the network profile used by the host.
- Restart the server and test from another device on the LAN.
If a local connection succeeds but LAN access fails, temporarily compare the result with the firewall rule disabled only long enough to confirm the diagnosis, then re-enable it and create a correctly scoped rule. Do not leave the host unprotected as a permanent workaround.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsForward the port for remote players
Remote access requires the router to send the same server port to the host’s current LAN address. A server can be perfectly healthy and still invisible from the internet when forwarding points to an old address.
- Find the host’s current LAN address and reserve it in the router’s DHCP settings, or otherwise ensure it will not change.
- Forward the server’s configured port from the router to that address. Use the edition’s documented protocol and the same external and internal port unless your design requires a translation.
- Check that the host firewall allows the forwarded traffic.
- Keep the server’s bind/address settings at their documented defaults unless you have a specific reason to change them.
- Test from outside the home network. An internal test may fail on routers that do not support hairpin or loopback access even when external players can connect.
If external access still fails while LAN access works, check whether the internet service uses another router, carrier-grade NAT or a managed gateway. In that situation, a forwarding rule on the inner router may never receive the public traffic; the upstream device must also pass it through.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Match the symptom to the right repair
The console reports a missing file or library
Stop the server and compare the installation with the official package for the exact edition and operating system. Do not copy a library from an unrelated version. Restore the missing file from a clean package, then repeat the foreground startup test.
Best Value
The process exits with a permission error
Confirm that the account running the server can read the binaries and write the world, logs and configuration directories. On Ubuntu, verify that the server executable can be run by the service account. On Windows, check file permissions and whether security software quarantined a newly updated binary.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →The world fails to load
Do not repeatedly start the server against the only copy of the world. Stop it, preserve the original backup, and test a copy in the new server directory. A world-load error may indicate incompatible data, a damaged file or a configuration mismatch; the first stack-trace line usually determines which branch to investigate.
The server starts but no one can join
Check the exact client/server versions, then perform the host, LAN and external tests in that order. A successful startup does not prove that the firewall and router are configured.
Only some players are rejected
Compare the affected players’ edition, release and preview/snapshot status with a player who can connect. A subset of clients often indicates different installed versions or authentication settings rather than a server-wide outage.
Rollback safely when the update is the cause
Rollback is safest when the old binaries and a world backup are separate from the new installation.
- Stop the updated server and keep its logs.
- Rename the updated directory instead of deleting it.
- Restore the previous server directory or launch the previous version from its own directory.
- Use a backup copy of the world made before the update; never experiment first on the only copy.
- Test locally, then on the LAN, before allowing remote players back in.
If the old version loads the backup and the new version does not, preserve the evidence: the startup log, version numbers and configuration differences. That information is more useful than repeatedly swapping files without a known baseline.
When self-hosting is no longer the practical repair path
Self-hosting requires maintaining server binaries, an operating-system runtime, world backups, firewall permissions and router forwarding. If you cannot keep the process running in the foreground, cannot control the upstream router, or need others to manage updates and backups, a managed Minecraft host may remove those operational tasks. Before moving a world, verify that the provider supports your edition and exact release, permits world export, documents backup retention, and serves your players’ region. A managed service does not eliminate protocol mismatches: clients still must use a version compatible with the hosted server.
Quick Recap
A repeatable update checklist
- Record the edition and exact stable client and server releases.
- Stop the old server cleanly.
- Back up the world, configuration and launch files.
- Keep old and new server versions in separate directories.
- Start the new process in a visible terminal and capture the first error.
- For Java Edition 1.18-era software, verify that the selected custom runtime is Java 17 or newer.
- Review
server.properties, including world name, authentication, gameplay values and port. - Connect on the host, then from the LAN, then from an external network.
- Allow the configured port through the host firewall; Bedrock’s documented defaults are 19132 and 19133 unless your configuration differs.
- Forward that same port to the host’s current LAN address.
- If the update remains incompatible, roll back using the preserved directory and a tested world backup.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.

