Skip to content

🛠️ Troubleshooting & FAQ

If your server isn't starting or the console is behaving unexpectedly, check these common solutions.

🔍 Common Issues

  • Server Already "Active"

    Issue: RSM shows "Active" but you didn't start the server.

    Fix: RSM uses PID Handoff. It found a running process from a previous session. Click Force Stop if the ID is incorrect.

  • :material-console-off: Blank Console Window

    Issue: The server is running, but no text appears in RSM.

    Fix: * MC: Ensure -nogui is in arguments. * SE: Ensure -console is in arguments. * Admin: Try running RSM as Administrator.

  • :material-ethernet-alert: Port Binding Error

    Issue: "Port 25565 already in use" in logs.

    Fix: A ghost process is holding the port. Kill java.exe in Task Manager or use netstat -ano in PowerShell to find the culprit.

  • :material-account-shield: Permission Denied

    Issue: Server fails to write logs or save world.

    Fix: Ensure RSM has Write access to the server's Root Directory. Running from C:\Program Files\ often requires Admin rights.

🧠 Advanced Technical Info

How PID Handoff Works

Unlike simple batch files, RSM saves the Process ID (PID) to a local database. 1. When you click Start, RSM records the ID. 2. If RSM crashes or is closed, the server keeps running. 3. Upon restart, RSM "scans" for that ID. If it's still alive, it re-attaches the controls instantly.

Memory Leaks

If your RAM usage bars in RSM are hitting 90%+, the manager may struggle to capture logs. Always ensure you leave at least 1-2GB of "Headroom" for the Windows OS to breathe.

📥 Still Need Help?

If your issue isn't listed here, please collect your logs from the appdata/roaming/RSM/logs folder and open a ticket.

Report an Issue (WIP) Join the Community (WIP)