Running a Minecraft server isn't always smooth sailing. In this guide, we'll cover common issues and how to resolve them using the tools available in the MC Bedrock Server Manager.
Server Won't Start
If your server fails to start, check these common causes:
Check the Console
Always start by checking the Console tab for error messages. Look for:
- Red error lines indicating problems
- Exception stack traces showing where errors occurred
- Warning messages that might indicate issues
- Should point to
bedrock_server.exe(Windows) orbedrock_server(Linux/Mac) - Ensure the file exists at that location
- On Linux/Mac, ensure the file has execute permissions:
chmod +x bedrock_server - Must point to the folder containing your server files and worlds
- Should contain
server.properties,worlds/folder, etc. - Ensure the wrapper has read/write permissions
- Stop the conflicting application, or
- Change the port in
server.properties(server-port setting) - Update router port forwarding if using external connections
- Check for syntax errors (missing equals signs, invalid values)
- Review the file using the wrapper's server properties editor
- Reset to defaults if unsure
- Ensure at least one backup job is enabled in Settings → Backup
- Verify the backup directory is configured (click "Browse" if missing)
- Check that the backup directory exists and is writable
- The server must be running for backups to work
- Check that the server responds to commands
- Backups require sufficient free space to create ZIP archives
- Ensure the backup directory has enough space
- Review retention policies if running out of space
- Ensure Activity Logger is enabled in Settings → Player
- Enable Player History if tracking joins/disconnects/deaths
- Verify specific tracking options are enabled (health, location, kills, etc.)
- CPU spikes during specific activities
- High memory usage that might cause lag
- Resource-intensive periods
- Reduce max-players if experiencing lag
- Lower view-distance in server.properties
- Limit entity spawn rates if needed
- Close unused instances to free resources
- Ensure Windows Firewall allows UDP traffic on port 19132
- Check router firewall settings
- Verify antivirus isn't blocking the connection
- Forward UDP port 19132 to your server's local IP
- Use your public IP address (find at whatismyip.com)
- Test connection from outside your network
- Check max-players setting in server.properties
- Increase limit if you want more players
- Enable relevant debugging options in Settings → Debugging
- Review log files in the Debugging tab
- Check console output for specific error messages
- Use the "Repair Server" tool in Debugging → Server Maintenance Tools
Verify Server Binary Path
Check Settings → Server → Server Binary Path:
Check Working Directory
Verify Settings → Server → Working Directory:
Port Conflicts
The default port is 19132 (UDP). If another application is using this port:
Server Properties Errors
Invalid settings in server.properties can prevent startup:
Backups Not Working
Check Backup Job Configuration
Method-Specific Issues
For Save Hold/Query/Resume method:
Check Disk Space
Enable Debug Logging
Enable Debugging → Backups → Operations to see detailed backup logs in the Console.
Player Tracking Not Updating
Check Settings
Restart Required
Player settings require a server restart to take effect. The save message will remind you if a restart is needed.
Check Console for Deployment
When the server starts, you should see Activity Logger deployment messages in the Console. If these are missing, the behavior pack may not have deployed correctly.
Enable Debug Logging
Enable Debugging → Players → Stats Updates to see detailed tracking logs.
Performance Issues
Monitor Performance Metrics
Use the Dashboard's Performance Metrics graphs to identify:
Optimize Settings
Connection Issues
Firewall Configuration
Port Forwarding
For external connections, configure router port forwarding:
Server Full
Getting More Help
If issues persist:
Most issues can be resolved by carefully checking settings, reviewing console output, and using the wrapper's debugging features.