1. Choose the right server
Ask each player which edition and version they use. A Java client normally joins a Java server and a Bedrock client joins Bedrock Dedicated Server. Start with Vanilla for an unmodified world or Paper for plugins. Fabric, Forge and NeoForge need matching loader and Minecraft versions. Cross-play through Paper and Geyser is a separate setup with its own version and UDP requirements. Owning TomoNode does not provide a Minecraft license.
2. Create it in TomoNode
Open New server and select Minecraft, its edition, server type and game version. Select a dedicated writable folder with room for both the world and backups. Review the PC diagnosis, memory and port suggestions rather than assigning all available RAM. Java servers require compatible Java; Bedrock does not use Java. If Java is missing, review the Temurin download and license before approving it. Read the Minecraft EULA and confirm it yourself. Complete creation, start the server and wait for the log to show readiness.
3. Test locally before inviting friends
On the host PC, test a Java server using localhost and the configured game port. From a second device on the same LAN, use the host PC's private IPv4 address and that port. Bedrock uses the configured UDP port and its client server-entry screen. If local access fails, resolve that first. For friends outside the LAN, choose a supported relay or configure forwarding for the actual game protocol. A private address is not reachable from another home. CGNAT, firewall rules and relay limits can still prevent access. Never disable the entire firewall as a workaround.
4. Add content and change settings safely
Mods belong to a matching Fabric, Forge or NeoForge loader. Plugins belong to a compatible plugin server such as Paper. Data packs belong to the selected world, not the mods directory. In Extensions, check the game version, loader, dependencies and server support before accepting a Modrinth installation plan. Client-only mods should not be installed on the server; some gameplay mods also need installation on every player's client. Stop the server and back up before changing a combination. Change one component at a time and respect each project's license.
5. Make a backup you can restore
Record which server, version and folder the backup belongs to. For a consistent manual copy, save the world and stop the server first. Keep the world, configuration and required extension files together; a copy on the same disk does not protect against disk failure. For an app backup, wait for completion and verify the entry appears. Before restoring, stop the server and preserve its current state. Select the intended backup and check its date and integrity result. Start the restored server and confirm a known build or inventory in the game before treating recovery as successful. Do not depend on scheduled backups while the scheduling UI remains in development.
6. Find the cause before changing more settings
Read the first meaningful startup error rather than only the last line. A Java version error needs compatible Java; an EULA error needs your explicit acceptance; a bind error usually needs a free port or stopping the conflicting process. Test on the host and LAN before changing router rules. For lag, compare CPU, memory and storage usage while the problem occurs, then reduce view or simulation distance or test without a recent extension. Change one setting at a time. The linked troubleshooting page includes recovery checks. When reporting a problem, send the app version, game and steps, not full logs, IP addresses, passwords or player details.