Restarting your server is sometimes necessary to apply system updates, resolve performance issues, or clear system memory.
In this post, we will explain how to restart your server without leaving the RunCloud dashboard.
Understanding the Difference Between Service Reloads and Server Restarts
If you’re restarting your server solely to apply a new configuration or to update a specific setting within your environment, you should first consider using the reload services functionality.
- Reloading a service is often a better choice because it tells the application to read the new configuration files without terminating the main process or dropping active user connections.
- Restarting an individual service stops it completely before restarting it, which may cause a few seconds of downtime for that function. You should only restart your entire server if you absolutely need to.
Within the Services Tab, you can choose to “Reload” or “Restart” specific items such as NGINX, OpenLiteSpeed, PHP-FPM versions, or MariaDB.
A full reboot should be reserved for instances where the operating system requires a kernel update, the system has become completely unresponsive, or you are experiencing a deep-seated memory leak that cannot be resolved by restarting individual services.
Please note that restarting your server will cause all hosted websites to go offline for a brief duration. Ensure all unsaved data is secured before proceeding.
How to Restart Your Server Using RunCloud
- Open your RunCloud dashboard.
- Select the specific server you wish to restart from the list.
- Navigate to the side menu and click Settings.
- Scroll to the bottom of the Settings page to find the “Restart Server” section.
- Click the Restart Server button.
- This will open a confirmation modal. Click the Restart Server button within the modal to confirm the action.
- Wait for the server to complete the reboot process.
If you have any other questions or need help – please feel free to get in touch with our 24/7 support team. We’re here to help!