Getting started with your first Minecraft server

A practical checklist for choosing the right edition, connecting successfully, protecting your world, and avoiding the most common beginner mistakes.

Published by PortalMine Operations & Documentation TeamReviewed July 13, 2026Reading time: 8–12 minutes

Start with three decisions

Before creating a server, decide which Minecraft edition your group uses, whether the world will be private or public, and how important the world is. These choices affect the software you select, the way players connect, the security settings you need, and how frequently you should make backups.

Edition

Java players need a Java server. Bedrock players need a compatible Bedrock/Nukkit server. Do not choose based only on the device you own; ask every player which edition they use.

Access

A private friend server should normally use a whitelist. A public server needs moderation, rules, backups, and a plan for abuse reports.

Value of the world

If losing the world would matter, download backups regularly and especially before any software or configuration change.

Expected load

Player count, plugins, mods, entities, farms, and view distance all affect performance. Start small and increase complexity gradually.

Creation checklist

  1. Create one account

    Use accurate account details, verify your email, and do not create duplicate accounts to bypass service limits.

  2. Select Java or Bedrock/Nukkit

    Choose the edition your players actually use. Plugin ecosystems and connection methods are different.

  3. Choose a compatible version

    Match the client version when possible. Avoid downgrading an existing world.

  4. Wait for installation

    Installation is a server-side process and can continue after the page appears ready. Watch the state rather than submitting another request.

  5. Connect using the displayed details

    Paste the exact address. Bedrock players should also enter the displayed port.

  6. Secure the server

    Use a whitelist for private play, limit operators, and never share account credentials.

  7. Make the first backup

    Create or download a clean backup before adding plugins, changing versions, or inviting a large group.

Your first 30 minutes as an owner

Join the world yourself before inviting others. Confirm spawn works, difficulty is correct, player-versus-player behavior matches your plan, and the whitelist or permissions are functioning. Ask one trusted friend to test the same connection details from another device or network.

Then write five simple rules: who may join, whether griefing is allowed, which language is expected in chat, how disputes are handled, and who has administrator access. Clear rules prevent more problems than complicated moderation tools.

Common early mistakes

  • Using a Java address in a Bedrock client or forgetting the Bedrock port.
  • Installing several plugins at once and then not knowing which one caused the failure.
  • Giving operator permissions to every friend.
  • Assuming the live server is a backup.
  • Running high view distance, large farms, or excessive entities on limited resources.
  • Changing to an older server version with an existing world.
  • Sharing screenshots that expose account details, tokens, or private addresses.

First 20 minutes after creation

  1. Wait until installation changes to a stable Offline or Online state.
  2. Start the server once and read the console until it reports a ready state.
  3. Copy the exact Java or Bedrock address shown by PortalMine.
  4. Join with the owner account, then reconnect to verify the address.
  5. Set whitelist, difficulty, game mode, PvP, online mode, and Hardcore intentionally.
  6. Create a backup before adding plugins, mods, or imported worlds.

Pre-launch decision table

QuestionWhy it mattersGuide
Do players own Java or Bedrock?The editions use different clients and server ecosystems.Java vs Bedrock
Do players install mods?Mods require a loader and often matching client files.Plugins vs mods
Is the server private?Whitelist reduces random joins and moderation load.Whitelist vs public
Can you restore the world?A backup is useful only when restoration works.Backup plan

Common first-day mistakes

  • Pressing Start repeatedly while installation is still active.
  • Sending the Java address to Bedrock players or omitting a required Bedrock port.
  • Installing several extensions before testing a clean server.
  • Giving operator access to every friend instead of using normal-player tests.
  • Enabling Hardcore Mode without explaining its consequences to the community.