PortalMine dashboard map
The dashboard separates routine owner tasks so you can identify whether you are changing server state, server configuration, files, software extensions, or account details. A control can be unavailable while the server is installing, starting, stopping, or offline.
| Area | Use it for | Before you change anything |
|---|---|---|
| Server | Status, address, start, stop, restart, timer and extensions | Read the current state and save console evidence before restarting |
| Console | Startup output, warnings, commands and crash context | Copy the first meaningful error and its timestamp |
| Files | Configuration, logs, worlds and uploaded files | Download a backup and avoid editing while the server writes |
| Settings | Name, difficulty, mode, whitelist, online mode, PvP and Hardcore | Understand whether the setting needs a restart |
| Plugins / add-ons | Search, install and remove supported extensions | Match software and Minecraft version |
| Profile | Username, server address and password options | Changing the username can change the PortalMine address |
Create a server safely
- Choose Java or Bedrock based on the players’ actual editions.
- Select the offered server software and version.
- Leave Hardcore Mode off unless permanent-death-style gameplay is intentional.
- Review the level’s memory, player, and runtime limits.
- Create the server and wait for installation to complete before sending repeated power actions.
- Read the first successful console startup and save the connection address.
Hardcore Mode
PortalMine exposes Hardcore Mode during server creation and in Server Settings. It is off by default. When enabled for supported software, the server uses survival-oriented hardcore behavior and hard difficulty. Back up the world before changing this on an established community and verify the result after restart.
Power actions and coins
Start, restart, extend, and level actions can have different coin costs. Read the confirmation text before continuing. A restart is not a substitute for diagnosis: save console errors first, because the most useful crash lines may be lost in the next startup output.
Recommended first-session test
- Join with one owner account.
- Confirm the displayed edition, version, address, and port.
- Break and place blocks, change dimensions, and reconnect.
- Test whitelist and operator access with a second non-admin account.
- Create the first backup before installing plugins, mods, or add-ons.
Support checklist
When contacting PortalMine, include the server type, version, status, approximate time, first error line, and action you attempted. Never send your password, API token, full session cookie, or private player information.
Server Settings reference
Change settings deliberately. Name changes affect display labels; game mode and difficulty change gameplay; whitelist controls access; online mode controls Java identity verification; PvP changes player combat; and Hardcore Mode changes the risk profile of the world. Some changes require a restart before the server process reloads server.properties.
Hardcore Mode safety checklist
- Explain the rules to every player.
- Create a timestamped backup.
- Confirm Survival and Hard difficulty expectations.
- Restart the server after saving.
- Test with a non-owner player.
- Record how deaths, bans, and world resets will be handled.
Files and logs
Use the Files area for controlled edits, not live experimentation. Download the file before changing it, preserve line endings and encoding, and avoid editing world data while the server is actively writing. In logs, start from the first exception or warning tied to the failure rather than only the final shutdown line.
Plugin and add-on checks
Confirm that the extension matches Java Paper/Purpur or Bedrock Nukkit as appropriate. Install one change at a time, restart when required, and verify the feature with an ordinary player account. Remove an extension only after backing up its data and reading its migration notes.
Custom Server workflow
- Select a complete server package and allow automatic type detection where appropriate.
- Wait for the upload and server-side preparation stages to finish.
- Confirm the startup entry file and runtime in the console.
- Use the Java plugin area only when the detected software supports Java plugins.
File Manager workflow
Use Files for uploads, folders, editing, extraction, rename, cut, copy, paste, move, download, and deletion. Stop the server before replacing worlds or editing files written continuously by the process. Large uploads can continue through multiple server-side stages after the browser reaches 100%.
Share selected servers
Profile sharing should expose only the servers selected for that link and only the permissions granted. Revoke old links after ownership changes or when a collaborator no longer needs access. Never share the owner account password.