How it works

A simple 3-step path: create an account, create your server, connect and play. This page provides a detailed walkthrough, helpful tips, and troubleshooting advice.

Create an account Read FAQ

Step-by-step guide

Step 1

Sign up

Click Sign up in the top navigation. Use a real email address so you can verify and recover your account later.

Choose a short username.
Use a strong password (8+ characters).
Verify your email when prompted.

Step 2

Create your server

Inside the dashboard, choose a server name and Minecraft version. Keep it simple if this is your first time.

Start with a popular stable version.
Keep player slots modest for stability.
Write a short description or rules.

Step 3

Connect & play

Copy the connect address and paste it into your Minecraft launcher’s “Add Server” form. Invite friends and start playing.

Copy/paste the IP to avoid typos.
Use a whitelist for private worlds.
Back up before major changes.

Best practices for smooth servers

Start vanilla: Add plugins or mods only after the base world is stable.
Change one thing at a time: If something breaks, you’ll know what caused it.
Keep rules visible: A short “server rules” list prevents drama and griefing.
Schedule restarts: A restart after long sessions can help keep performance consistent.
Respect fair use: The free tier is for friendly servers and modest loads.

Troubleshooting

I can’t connect — what should I check first?

Confirm the server is “Online” in the dashboard.
Copy the server address again (no extra spaces).
Check you’re on a compatible Minecraft version.
Visit Status for outages or maintenance.

My server feels laggy — what can I do?

Try reducing view distance, removing heavy plugins, and keeping player count modest. If lag starts after adding a plugin, remove it and test again.

I forgot my password

Use the “Forgot password” link in the login modal. If email delivery is delayed, check your spam folder.

Where do I get support?

Start with FAQ, then contact us via Contact.

Suggested checklist before inviting friends

Safety

Enable whitelist for private servers.
Add basic anti-grief rules.
Keep your account password strong.
Don’t share admin details publicly.

Stability

Start with a stable version.
Limit heavy mods for the free tier.
Test a restart and reconnection once.
Create a quick backup if available.

Setup and management guideUpdated July 13, 2026

The complete PortalMine workflow

Create and verify your account
Use an email address you can access. Keep your password private and complete any verification step shown by the site. Do not create multiple accounts to bypass platform limits.
Choose the correct Minecraft edition
Select Java for Minecraft: Java Edition players. Select Bedrock/Nukkit for supported Bedrock clients. Java plugins do not run on Nukkit, and Bedrock plugins do not run on Java software.
Select a server version carefully
The safest choice is usually the version your players already use. Changing an existing world to an older version can damage data. Before a major version change, download or create a verified backup.
Wait for installation to finish
Installation can take longer than the page load. Do not repeatedly click create or restart while the server is installing. Watch the status until it is ready or an actionable error appears.
Copy the exact connection details
Java usually uses a server address. Bedrock commonly requires an address and port. Remove accidental spaces and do not add https:// to a Minecraft server address.
Secure the first session
For a private server, enable a whitelist before sharing the address publicly. Grant operator rights only to trusted people. Write down basic community rules and keep backups away from the live server.
Add customizations gradually
Install one plugin or major change at a time, then restart and test. If the server stops working, logs are far more useful when only one change was made.
Maintain the world
Back up before updates, watch entity-heavy farms, remove abandoned plugins, and check the Status page when several users experience the same issue.

Joining from Java Edition

Open Multiplayer.
Select Add Server or Direct Connection.
Paste the address displayed in PortalMine.
Confirm that your client version is compatible.
Join only after the dashboard reports the server is online.

Errors such as “connection refused” usually mean the server is offline, still starting, or using a different address. “Outdated client” or “outdated server” normally indicates a version mismatch.

Joining from Bedrock Edition

Open the Servers tab and choose Add Server.
Enter the hostname without a web prefix.
Enter the exact port shown in the dashboard.
Save and connect after the server is online.

Console editions may restrict custom server entry. Availability depends on the device and platform rules, not only the hosting server.

Before installing plugins or mods

Confirm that the plugin matches the server software and version.
Download only from a source you trust.
Read dependencies and installation notes.
Back up the world and configuration.
Test with a small number of players.
Remove the new file first if startup errors begin immediately after installation.

When to contact support

Contact support after you have checked the service status, refreshed the dashboard, confirmed the server address, and reviewed the latest log lines. Include your username, server name, edition, approximate time of the problem, the action you attempted, and the exact error message. Never send your password.

For deeper diagnosis, use the connection troubleshooting guide.

What happens behind each visible step

Creating a server begins a provisioning workflow: PortalMine validates the request, reserves the allowed resources, prepares the selected software, writes initial configuration, and reports installation state to the dashboard. Starting the server launches the game process. The process then loads configuration, extensions, world data, dimensions, player data, and network listeners before it can accept a connection.

Know the difference between the panel and the game server

PortalMine panel

Handles account access, server records, displayed state, resource policy, power requests, and links to operational tools.

Server process

Runs Minecraft software, loads worlds and extensions, listens on the game port, processes ticks, and writes console output.

Player client

Uses a specific edition and version, resolves the address, reaches the server through the network, authenticates, and loads world data.

External dependencies

DNS, internet routing, Mojang or Microsoft authentication, third-party extension files, and the player’s local network can affect the result.

First-connection validation

Wait until the console reports a complete successful startup rather than connecting during installation or world generation.
Copy the server address exactly and include a port only when the provided connection format requires it.
Use a client with the same edition and a compatible version.
Test with one owner account before inviting the full group.
Verify movement, chat, permissions, world saving, and reconnect behavior.
Create or verify a backup after the baseline works and before adding extensions.

When a step fails

Identify the failed layer before changing settings. An account login problem belongs to authentication or browser state. A server that never reaches ready state belongs to startup, software, configuration, or world loading. “Unknown host” points toward an address or DNS problem. “Connection refused” usually means nothing is accepting the connection at the target address and port. A version mismatch requires edition and protocol alignment, not a restart loop.

Ongoing operating cycle

Stable servers use a repeatable cycle: observe, back up, make one planned change, restart only if needed, verify console health, test with a representative player, and document the result. The Server Owner Handbook expands this into daily, weekly, and update-time routines.