This WWKNOW guide covers security in the context of SolusVM 1. It is written as vendor-neutral operational guidance so you can apply it without relying on a specific upstream provider.
Before you begin
- Confirm which server, domain, account, or application you are changing.
- Make a current backup or export when the task can affect data, access, DNS, mail, or service availability.
- Keep the existing configuration values available so you can roll back if verification fails.
Recommended workflow
- Open the relevant SolusVM 1 interface or administrative shell using the least-privileged account that can complete the task.
- Locate the setting or resource related to security and review the current state before editing it.
- Apply one logical change at a time. Save or apply the change, then wait for the software to report success before continuing.
- Verify the result from the customer-facing side as well as the administrative side. For network or DNS work, test from an external connection where practical.
- If the result is not as expected, compare logs and recent configuration changes before retrying or rolling back.
Verification checklist
- The intended resource is reachable and responds normally.
- No unrelated domain, mailbox, database, site, or service was changed.
- Relevant logs do not show new repeated authentication, permission, network, or application errors.
- Backups and monitoring still cover the modified service.
Important notes
Interface names and exact options can vary by software version, operating system, service plan, and account permissions. Record the current configuration before changing production settings.
When to contact WWKNOW Support
If the control is unavailable, the service does not recover after rollback, or the task requires provider-level access, open a support request and include the service name, approximate time of the change, the exact error message, and the troubleshooting already completed. Do not send passwords or private keys in a public message.
