Install the Securantis plugin on WordPress: ZIP, activation and prerequisite checks

Purpose of this article

This guide explains how to install the Securantis plugin ZIP file on a WordPress site, activate it and verify that the technical prerequisites and basic settings are correct to ensure safe and reliable operation.

Target audience and prerequisites

• WordPress administrators or developers familiar with site administration.
• Administrator access to the WordPress dashboard (wp-admin).
• FTP/SFTP access or hosting panel access (cPanel/Plesk) if installation through the interface fails.
• PHP 7.4 or a version supported by your host (check compatibility in your contract or with Securantis support if unsure).
• Ability to install/activate plugins (administrative rights).
• Active Securantis license or license information ready (if you plan to finalize activation immediately).

Before installing: precautions

1. Full backup

• Make a full backup of files and the database. A backup allows you to restore the previous state if a conflict occurs.

2. Recommended maintenance mode

• Temporarily enable a maintenance mode if the site is in production and receives critical traffic. This reduces the risk of interruption during activation.

3. Test environment recommended

• If possible, install first on a copy/staging environment to verify interactions with your other plugins, themes and customizations.

Installation steps via the WordPress interface (recommended method)

1. Download the provided ZIP

• Retrieve the Securantis plugin ZIP file from your customer account or the link provided by Securantis.

2. Log in to the dashboard

• Go to your WordPress area > Plugins > Add.

3. Upload the ZIP

• Click the upload option for a plugin, then select the ZIP file and proceed with the upload.

4. Install

• After upload, click Install now. Wait until extraction completes.

5. Activate the plugin

• Once installed, click Activate to start the plugin.

Installation steps by FTP (if WP upload fails)

1. Decompress locally

• Decompress the ZIP locally then upload the plugin folder to wp-content/plugins via SFTP/FTP.

2. Check permissions

• Ensure files have standard permissions (generally 644 for files, 755 for folders).

3. Activate from the admin

• Return to Plugins and activate the plugin.

Post-activation checks and controls

1. Verify access to the Securantis interface

• In the administration menu, look for the Securantis plugin page (or the associated menu entry). Open it to confirm the interface loads correctly.

2. Automatic system checks

• The plugin runs initial checks: site HTTPS status, PHP version, WordPress update status, presence of file editor, xml-rpc, and other security checks. Consult the analysis/status page to view results.

3. Scheduled tasks (cron)

• The plugin registers scheduled tasks for heartbeat and scans. Verify these events are scheduled (sometimes visible via a cron management plugin). If you use hosting restrictions, confirm that WP-Cron or a server task executing WP-Cron is enabled.

4. Networking & report sending

• Depending on your license, the plugin may attempt to communicate with Securantis services. Ensure outbound HTTPS connections to the API are not blocked by your host or a firewall.

Immediate cautious settings to apply

• Disable file editing from the WordPress admin if you allow the editor option (enhanced security).
• Confirm the site URL uses HTTPS; if not, plan to install a certificate and configure the WordPress/Site URLs to use HTTPS.
• Do not change automatic quarantine settings: Securantis does not isolate or delete any files without a human decision.

Common errors and frequent messages

• ZIP upload failure in the interface: often related to PHP limits (upload_max_filesize, post_max_size) or file permissions. Solution: increase limits if possible or use FTP.
• Activation error (white page / 500): PHP conflict or insufficient memory. Check PHP logs, increase memory_limit and retry.
• Missing cron tasks: indicates WP-Cron did not run tasks. Check hosting configuration and plugins that replace WP-Cron.
• API connection refused: check outbound firewall rules and absence of a proxy blocking HTTPS calls.

Detailed troubleshooting

1. PHP logs and debug

• Temporarily enable WordPress debug mode to collect errors (WP_DEBUG in wp-config.php) then check the log file. Do not leave WP_DEBUG enabled in production without supervision.

2. Plugin conflicts

• Disable other plugins, then activate only Securantis to see if the issue persists. If the plugin works in isolation, reactivate plugins one by one to identify the conflict.

3. Verify the PHP environment

• Confirm the PHP version and the PHP extensions required by your host. If the version is too old, plan an upgrade.

4. Permissions and ownership

• Verify that the PHP user has the necessary permissions to read/write in the plugin folders and wp-content.

5. Upload via FTP if the UI fails

• If installation from the dashboard fails, manually upload the plugin folder via SFTP, then activate it.

Precautions and best practices after installation

• Do not allow automatic deletion or quarantine without human control. Securantis reports and proposes actions; deletion remains a manual decision.
• Keep a copy of the backup made before installation until full validation is complete.
• Document any changes made by the plugin (cron tasks, rules, allowlists) to facilitate potential rollback.

When to contact Securantis support

Contact support if:

• The plugin refuses to activate with no clear message after basic checks.
• You observe 500 server errors specifically related to plugin activation.
• Connections to the Securantis API are blocked despite network checks at the host.
• You need assistance to resolve a complex conflict or for an assisted installation (note: paid interventions require an order and submission of access via the secured customer area after payment).

Information to provide to support to speed up assistance

• WordPress and PHP version.
• List of active plugins and the theme in use.
• Copies of visible error messages and excerpts from PHP logs.
• Indication whether the installation was via the interface or by FTP.

Expected result after a successful installation

• The Securantis plugin is active and its administration page loads.
• Initial checks (HTTPS, PHP version, cron) are displayed and no critical blocking error is reported.
• Scheduled tasks for heartbeat and scan are present and communication with the Securantis API is possible.

If everything is verified, you may proceed to final license activation and configure scan and notification options from the plugin interface.

Security reminder

Securantis does not isolate, delete or restore any files automatically; any action on files identified as suspicious requires a human decision and confirmation.

End

If you need help with a specific step (error logs, verification of cron tasks, PHP compatibility check), prepare the items listed above before contacting support to speed up diagnosis.