iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Reinstalling Monarx normally means removing the existing agent and installing it again, not rebuilding the VPS. On a managed VPS dashboard, open Security → Malware Scanner, choose Uninstall, then return to the same page and use the installation banner. A previously purchased Monarx license is reattached automatically. On a self-managed Linux VPS, restore the agent configuration, repository and signing key, install monarx-protect-autodetect, restart the web server if necessary, and verify the PHP protection module. Reinstallation can repair an agent or scanner that stopped reporting, but it does not by itself clean a compromised database, administrator account or WordPress persistence mechanism.
When should you reinstall Monarx on a VPS?
Reinstall when the scanner is missing, no longer reporting, or behaves incorrectly after a server operating-system change. Reinstallation refreshes the agent and its protection components; it is not a substitute for incident response when malware is suspected.
- Reinstall after changing the VPS operating system, because the previous installation may no longer match the new system.
- Reinstall when the managed dashboard offers a repair path through its Malware Scanner page.
- Reinstall a self-managed installation when the agent, PHP extension or repository setup is damaged.
- Preserve evidence before removing an agent if you are investigating an active compromise. Record alerts and affected paths, and review accounts, scheduled tasks, web-server configuration, databases and backups separately.
Restoring a VPS snapshot has a separate effect: current malware diagnostic results are reset, so a new scan is needed after the restore.
How do I reinstall Monarx from a managed VPS dashboard?
Use the provider’s current dashboard labels; the documented workflow is to uninstall from the Malware Scanner page and then install again from the banner on that page.
- Sign in to the account that manages the VPS and open the relevant virtual machine.
- Open Security → Malware Scanner.
- Select Uninstall and complete the confirmation prompts.
- Return to Malware Scanner. The page should display an installation banner after the old installation is removed.
- Select the banner and follow the displayed installation instructions.
- Wait for the dashboard status to change to an installed or active state, then start a fresh scan.
A license purchased previously is automatically reattached during this managed reinstall. If no license is present, the scanner can still detect and report malicious files, but automatic removal remains unavailable; an administrator must handle deletion, quarantine or replacement manually.
Dashboard labels and banner wording can change. If you do not see the banner, reload the VPS page, confirm that you opened the correct virtual machine, and check whether the uninstall operation has finished before attempting installation again.
Do I need to uninstall Monarx before reinstalling it on Linux?
The self-managed procedure is centered on restoring the configuration and package installation; the vendor instructions do not require a separate destructive uninstall step. Avoid deleting evidence or configuration until you know which files are needed for the replacement installation.
#1 Best Overall
Have administrative shell access, a supported distribution, the Monarx agent configuration and permission to add the vendor repository and signing key. If the existing agent is still functioning, save its configuration and note the current web-server and PHP setup before changing packages.
Which Linux versions does the current Monarx guide support?
The vendor guide published May 11, 2026 lists the following major-version ranges. An unsupported variant should be confirmed with Monarx before changing repositories or packages.
| Distribution family | Supported versions listed in the guide |
|---|---|
| CentOS, RHEL and CloudLinux | 6–10 |
| Ubuntu | 16–26 |
| Debian | 9–13 |
| AlmaLinux and Rocky Linux | 8–10 |
Those ranges identify the releases covered by that guide, not a promise that every derivative or custom image will work unchanged. Check the exact operating-system release and architecture before adding a repository.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →How do I reinstall Monarx on a self-managed Linux VPS?
The essential sequence is configuration, repository and key, package installation, then verification. Use the distribution-specific repository and key commands in the current Monarx installation guide rather than copying commands intended for another Linux family.
1. Put the agent configuration in place
Obtain the agent configuration from the Monarx web application and save it as:
Rank #2
/etc/monarx-agent.confSet the user_base values to match the accounts and directory layout on your VPS. Incorrect user mappings can prevent the agent from associating monitored files with the right hosting account.
2. Add the repository and signing key
Use the repository definition and public-key import command for your distribution family from the official Monarx guide. The repository must be trusted by the package manager; do not substitute a key or repository copied from an unrelated server.
Recommended Free Tools
3. Install the protection package
Install monarx-protect-autodetect. On RHEL-family systems, the documented package-manager form uses yum; on Ubuntu and Debian, it uses apt-get:
yum install monarx-protect-autodetectapt-get install monarx-protect-autodetectThe autodetect package pulls in monarx-agent and monarx-protect. If the package manager reports an unsupported release, stop and resolve repository compatibility instead of forcing installation.
4. Restart the relevant web server when required
PHP protection is loaded through the web-serving stack. Restart the relevant web server after installation if the extension is not visible immediately or if the package instructions request it. The exact service name depends on the web server and distribution, so use the service name configured on your VPS.
5. Verify the PHP protection module
From a shell, run:
php -m | grep monarxprotectA matching monarxprotect entry confirms that the PHP CLI module is visible. Also open the Monarx web application and check Agent → Extensions. If the CLI check is empty but the web application still shows the extension, compare the PHP version used by the command line with the PHP version used by the web server.
Free tools Windows power users keep installed
One-click scans. No signup required.
6. Add auditd processing when appropriate
On systems that support auditd, you can optionally install monarx-agent-auditd. It processes filesystem activity near real time, but it is an enhancement rather than a prerequisite for the basic reinstall.
Can I automate the uninstall step through an API?
A managed-VPS API documents an authenticated DELETE request for removing Monarx from a virtual machine:
DELETE /api/vps/v1/virtual-machines/{virtualMachineId}/monarxReplace {virtualMachineId} with the actual VM identifier and send valid authorization credentials. If Monarx is not installed, the request succeeds without changing the VM, which makes it suitable for an idempotent cleanup step in automation. The documented endpoint covers uninstalling; installation still requires the provider’s installation workflow or the self-managed Linux procedure.
What does a Monarx license change after reinstallation?
Installation and cleanup are different capabilities. The scanner can monitor and report detections without a paid license. Automatic removal of compromised or malicious files requires a Monarx license.
Rank #4
- Without a license: review scan results and manually delete, quarantine or replace the reported files.
- With a license: automatic removal can be enabled according to the account’s entitlements. On a managed reinstall, an existing license is reattached automatically.
Do not interpret a successful package installation as proof that cleanup is enabled. Confirm the entitlement in the management interface before relying on automatic removal.
What does Monarx scan, and what does it miss?
Monarx monitors activity in the VPS filesystem. It does not scan database contents, so a clean result cannot prove that a WordPress or other web application compromise is fully removed.
Filesystem coverage
The agent coordinates filesystem scanning, malicious-process monitoring and malicious cron-file activity with the Monarx Cloud. These controls help identify activity in files and processes on the VPS.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteAreas requiring separate investigation
- Database rows, stored procedures and injected content are outside the stated filesystem scope.
- Compromised administrator accounts can recreate malicious files after a clean scan.
- WordPress
wp-content/mu-pluginspersistence may require manual review. - Web-server configuration, scheduled tasks and backup sets should be checked during an incident.
If compromise is suspected, preserve evidence before cleanup, rotate credentials through a controlled plan, and compare affected files with known-good copies. Reinstalling the scanner restores monitoring; it does not establish that the application or data layer is clean.
How do I troubleshoot a failed Monarx reinstall?
| Symptom | Likely check | Next action |
|---|---|---|
| No installation banner appears after dashboard uninstall | The uninstall job may still be running, or the wrong VPS may be selected. | Refresh the VPS Malware Scanner page, verify the virtual-machine identity and wait for the uninstall operation to complete. |
| Existing license is not active | The account has no previously purchased license, or the entitlement is not attached. | Confirm the license in the management interface; plan for manual file handling if no license is present. |
| Package cannot be found | The repository or signing key is missing, incorrect or incompatible with the OS release. | Recheck the distribution-specific repository instructions and supported-version range before retrying. |
php -m | grep monarxprotect returns nothing |
The web-server PHP environment may not have loaded the extension. | Restart the relevant web server, compare CLI and web PHP versions, and inspect Agent → Extensions. |
| Scan is clean but the site is reinfected | Database, account or application persistence is outside filesystem scanning. | Investigate databases, administrator accounts, scheduled tasks, web-server settings and wp-content/mu-plugins. |
| Previous results disappeared after recovery | A snapshot restoration resets current malware diagnostic results. | Run a new scan after the restore and retain the old incident records separately. |
What should a successful reinstall look like?
For a managed VPS, the Malware Scanner page shows the scanner installed and a new scan can be started. For a self-managed VPS, the configuration exists at /etc/monarx-agent.conf, the autodetect package and its dependencies are installed, the PHP module appears in verification, and the Monarx web application reports the agent and extensions. Treat that state as restored monitoring—not as certification that every database record, account or application component is free of malware.
Frequently Asked Questions
Can I call the uninstall API if Monarx is already absent?
Yes. The documented authenticated DELETE endpoint succeeds without changing the virtual machine when Monarx is not installed, so an automation run can safely repeat the removal check.
Is the auditd component required for the reinstall?
No. monarx-agent-auditd is optional on systems that support auditd. It adds near-real-time filesystem activity processing but is not required for the core agent and protection package.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
What should I do if my Linux release is outside the listed ranges?
Do not force a repository or package intended for another release. Confirm support for the exact distribution and version with Monarx before proceeding, or use a supported VPS image.
Does reinstalling preserve earlier scan history?
A snapshot restoration resets current malware diagnostic results, and an uninstall/reinstall should therefore be treated as a new monitoring state. Keep any incident records or exported findings separately before making changes.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
