Start and Stop Your Server

Starting Your Server

Step 1: Access Server Controls

1. Log in to your panel
2. Navigate to your server from the dashboard
3. Locate the server control buttons at the top of the server view

Step 2: Start the Server

1. Click the Start button
2. Wait for the server to initialize
3. Monitor the console tab for startup messages
4. Server is ready when startup completes (check console for ready message)

Step 3: Verify Server Status

Check that the server is running:

• Status indicator shows "Online" or "Running"
• Console shows active log messages
• Players can connect to the server

Stopping Your Server

Why Proper Shutdown Matters

Improperly stopping your server can cause:

• Data corruption: Unsaved data may be lost
• Data loss: User data, saves, or progress might not save
• Plugin/Mod issues: Plugins or mods may not save their data properly
• File corruption: Open files may become corrupted

Method 1: Using the Stop Button

1. Click the Stop button in the control panel
2. Wait for the graceful shutdown process
3. Server status will change to "Offline" when complete

Note: This sends a stop command to the server, allowing it to save data properly.

Method 2: Using Console Command

1. Open the Console tab
2. Type the appropriate stop command for your server type (e.g., /stop, quit, exit, or server-specific command)
3. Press Enter
4. Wait for the server to shut down gracefully

Method 3: Emergency Stop

Only use in emergencies! This immediately terminates the server process:

1. Click Force Stop or Kill button
2. Server stops immediately without saving
3. Warning: May cause data loss or corruption

Restarting Your Server

Restarting is useful for:

• Applying configuration changes
• Installing or updating plugins
• Clearing memory issues
• Applying server updates

Step 1: Stop the Server

1. Use the Stop button or /stop command
2. Wait for complete shutdown
3. Verify status shows "Offline"

Step 2: Start the Server

1. Click the Start button
2. Monitor the console for startup
3. Wait for full initialization

Quick Restart Option

The panel offers a Restart button that:

1. Stops the server gracefully
2. Waits for shutdown to complete
3. Automatically starts the server again

This is the recommended method for restarting your server.

Server States

Offline

• Server is not running
• No players can connect
• Files can be safely edited
• No resources being used

Starting

• Server is initializing
• Loading world and plugins
• Console shows startup messages
• Players cannot connect yet

Online

• Server is fully running
• Players can connect
• Active game session
• All systems operational

Stopping

• Server is shutting down
• Saving world and data
• Disconnecting players
• Cleaning up resources

Best Practices

Before Stopping

1. Announce to Users: Give users warning before stopping (if applicable)
2. Check Active Users: See who's connected (if your server shows this)
3. Save Data: Use appropriate save command for your server type if needed
4. Backup: Consider backing up before major changes

During Maintenance

1. Stop Gracefully: Always use proper stop, not force stop
2. Wait for Completion: Don't interrupt the shutdown process
3. Make Changes: Edit files, install plugins, etc.
4. Verify Changes: Check files before restarting
5. Start Carefully: Monitor console for errors

After Starting

1. Check Console: Look for errors or warnings in the console
2. Verify Plugins/Mods: Ensure all plugins or mods loaded correctly (if applicable)
3. Test Connection: Try connecting to verify the server works
4. Monitor Performance: Watch for performance issues or errors

Common Scenarios

Applying Configuration Changes

1. Stop the server
2. Edit configuration files using the File Manager
3. Save changes
4. Start the server
5. Verify changes took effect by checking the console

Installing Plugins or Mods

1. Stop the server
2. Upload plugin/mod files to the appropriate folder (varies by server type)
3. Start the server
4. Check console for loading messages
5. Verify plugins/mods are working correctly

Updating the Server

1. Backup everything (saves, plugins/mods, configs)
2. Stop the server
3. Replace server files with new version (method varies by server type)
4. Start the server
5. Test thoroughly before allowing users to connect

Fixing Crashes

1. Server may auto-restart or stay stopped
2. Check logs for error messages
3. Identify the cause (plugin, config, etc.)
4. Fix the issue
5. Start the server
6. Monitor closely

Troubleshooting

Server Won't Start

1. Check Console: Look for error messages in the console
2. Verify Files: Ensure server files exist and are valid
3. Check Resources: Verify you have enough RAM/CPU allocated
4. Review Logs: Check log files for detailed error information
5. Test Configuration: Verify configuration files are valid and properly formatted

Server Won't Stop

1. Wait Longer: Some servers take time to save
2. Check Console: Look for shutdown messages
3. Force Stop: Use as last resort (may cause data loss)
4. Contact Support: If server is completely unresponsive

Server Keeps Crashing

1. Check Logs: Identify the error causing crashes
2. Review Recent Changes: What changed before crashes?
3. Remove Problematic Plugins: Disable plugins one by one
4. Check Resources: Ensure adequate server resources
5. Verify Server Version: Check compatibility

Slow Startup

1. Check Data Size: Large save files or data take longer to load
2. Review Plugins/Mods: Too many plugins or mods can slow startup
3. Check Resources: Insufficient RAM or CPU can cause delays
4. Review Logs: Look for what's taking time in the console
5. Optimize: Consider data optimization or reducing plugins/mods

Scheduled Restarts

Many servers benefit from scheduled restarts:

• Daily: Clear memory, apply updates
• Weekly: Full maintenance window
• After Updates: Restart after plugin/server updates

Setting Up Scheduled Restarts

The panel supports scheduled tasks for automated restarts:

1. Navigate to your server
2. Go to the Schedules tab
3. Create a new schedule
4. Configure restart time (low activity period)
5. Set frequency (daily, weekly, etc.)
6. Test the schedule
7. Monitor the first few automated restarts