Minecraft, FiveM & game servers · 6 min read
Deploy Minecraft servers and test the first accession
An ongoing process is the first milestone. For a playable Minecraft server you also need the right game version, a reachable address and a successful joining with a normal player account. This guide will guide you from the provided instance to a test that also works from a foreign network. You can find the entry to the page for [Minecraft Servers].](/minecraft-server/).
Set Edition and Server Version
First, determine which edition your group is playing with. Minecraft Java and Minecraft Bedrock use different protocols. If you set up a Java server, start the test with a Java client. A connection error in the Bedrock client is not a clue to a broken instance in an ordinary Java server. Additional bridges between the editions are a separate project and should only be added when normal access works.
Decide whether you want to use an unchanged world, plugins or a modpack. For a modpack you write down the Minecraft version, the loader and the exact pack version. Pass this information on to all test persons. Even if two packs are similar, versions may differ. For the first connection a minimal setup with exactly the components that your project needs is suitable. Thus, you can later understand which extension caused a change.
Distinguishing deployment and launch
Open the Gameserver management and select the Minecraft instance provided. If the job is still in progress, the final connection address may still be unavailable. Keep the order reference at hand if the deployment remains unclear. Once the instance is set up, start it and track progress in the console or protocol. A new world may need additional time to generate at first launch.
Watch the order of the messages. An output about loading a world shows that the process is working. Only after the start is completed, the accession attempt is worthwhile. Ends the output with an error, secure the corresponding lines and the time. For several messages the first concrete exception is often more meaningful than the subsequent follow-up errors. Start again only after you have checked a possible cause. This leaves the logs clear.
Connect to the actual address
Copy the address from the instance view. If a port belongs to the address there, take it completely on the first test. In the game, go to multiplayer mode and try the direct connection. A default port from a general guide only helps if it corresponds to the assigned address. You can set up your own domain later as soon as the access with the provided address is proven to work.
Then test with a second person from another network. It should use the same version and address. If only one accession fails, first compare the client version, the account used and the exact error message. If both fail, check the server status and whether the accession attempt appears in the protocol. A timeout, a rejected connection and an error message to the game version indicate different places in the process. Hold the exact wording before changing settings.
Check access and world
For a private start, a registration list is suitable. Enter the intended player names and check the access with a normal account. Administrator rights are only required for people who actually manage the server. Let the test person enter the world, move and perform a harmless action. Check whether the server processes the action and whether joining with the same account is possible afterwards.
If you move an existing world, check typical orientation points, inventories and the affected dimensions. An empty new world can mean that the server loads another world folder. Compare the set world name with the transferred file and folder structure. Keep the original backup until you have seen the world in play. In case of modifications, you also check whether objects and blocks from the extensions appear correct. Perform this check before opening for the whole community.
Limiting errors by layers
If the server breaks off at startup, start with the console. Check whether the error calls a specific file or extension and whether it occurred for the first time after a certain change. Change a point and record the result. If the server is running, but the client does not get a connection, check the address, port and edition first. If the client comes up to login and is then rejected, game version, account check and admission list are the next check points.
For a ticket, you collect instance name, date, time, Minecraft version and the relevant part of the error message. Also, describe which tests have already been successful. The difference between an error for all players and an error for a single account is particularly valuable for the diagnosis. You can find the access to the support in the [Help Center].](/hilfe/). Remove login data, tokens and private messages from screenshots or log statements before you pass them on.
Before releasing to the community
Write down the tested server address, the edition, the loader and the time of the first successful joining in a common place. Determine who is responsible for technical changes and who informs the gamers about maintenance. A short announcement with the specific access data and a contact option is enough for the start. If necessary, add a guide for the modpack to allow new players to install the same files.
Create a backup of the working starting position and determine which world and configuration it includes. At least check whether the backup is visible in the administration and how a recovery is done. A later update can be more easily limited if you know the working version and its extensions. For the start of a community, this documented base is more helpful than many untested additional functions.
Frequently asked questions
Do I always have to enter port 25565?
Use the full address assigned to your instance. If there is a port, take it over. This allows you to test the first connection regardless of assumptions about standard ports or a later set-up domain.
Why do I see the world list in the game, but can't join?
An ad in the server list only proves that certain information was available. Check the error message when joining, the game version and the admission list. In a modpack, compare the versions of the extensions used.
Do I need a domain for the first test?
The provided server address is sufficient. Test it directly first and then complete your own domain if you need it. This allows you to distinguish between server access and DNS in case of a later malfunction.
What should I do when the first world is empty?
If you have expected an existing world, check the world name and the transferred folder. Keep the old backup and check known locations and inventories after the next launch.