Start with the problem you are trying to solve
The PortalMine Knowledge Base is organized around real server-owner tasks rather than a list of disconnected keywords. Choose setup when you are building a new world, operations when the server already has players, performance when actions feel delayed, and troubleshooting when a specific error blocks a connection or startup.
Setup and software
Choose Java or Bedrock, understand Vanilla, Paper, Purpur, Fabric, Forge, and Nukkit, then create a version-compatible plan before uploading worlds or add-ons.
PortalMine documentation
Learn the dashboard, server creation, Hardcore Mode, power actions, settings, logs, file handling, addresses, and safe update workflows.
Errors and connection problems
Use symptom-based checks for connection refused, timed out, incompatible version, authentication failures, mod mismatch, and startup loops.
Terms and concepts
Look up TPS, MSPT, chunks, view distance, simulation distance, whitelist, online mode, ports, SRV records, plugins, mods, and backups.
Recommended learning paths
| Goal | Read first | Then continue with |
|---|---|---|
| Launch a first server | Getting Started | How servers work and Java vs Bedrock |
| Improve performance | Lag diagnosis | Paper optimization and capacity planning |
| Run a modded server | Plugins vs mods | Fabric setup or Forge setup |
| Protect a community | Security checklist | Backups, whitelist policy, moderation, and update planning |
| Fix a connection error | Error library | Connection troubleshooting and IP/port guide |
How PortalMine documentation is reviewed
Each technical page separates platform-specific instructions from general Minecraft administration advice. We avoid claiming benchmark results that were not measured. When a guide links to PaperMC, Fabric, Forge, Minecraft, or Microsoft documentation, that external source is used to verify software behavior or command syntax. PortalMine-specific steps are checked against the current dashboard labels and settings.
Before applying a configuration change
- Record the current software type and game version.
- Create a restorable backup and note the exact file date.
- Change one category at a time.
- Restart only when the setting requires it.
- Test with the same player count and workload.
- Write down the result so you can reverse a bad change.
Popular resources
Evidence to collect before troubleshooting
A useful support request includes the exact server software, Minecraft version, player edition, timestamp, server status, connection address format, first relevant console error, and the last change. Do not send a cropped screenshot that removes the line immediately above the failure. Do not send passwords, cookies, panel tokens, or private player data.
Content categories
Beginner setup
Edition choice, addresses, ports, first start, whitelist, operator access, game mode, difficulty, and backups.
Advanced operations
Change management, incident notes, software migrations, plugin and mod inventories, scheduled maintenance, and restore drills.
Performance engineering
TPS, MSPT, chunks, entities, plugins, storage, memory, and controlled workload comparisons.
Security and trust
Least privilege, extension sources, account protection, moderation evidence, privacy, and community rules.
How to avoid low-value troubleshooting
Do not apply a list of random fixes. Each change should test one explanation. If the server is slow only during exploration, test chunk generation. If one player times out while everyone else plays normally, test that player’s network and client. If startup fails immediately after an update, compare the new software and extension versions before changing performance settings.