In this manual of TripleZero iT we cover Linux vulnerability CVE-2026-31431. A VPS is its own virtual server: you determine the operating system, the firewall and what runs. That gives freedom, but also maintenance.
We write based on the working method in our customer panel and the control panels that belong to your package (DirectAdmin, CyberPanel or Plesk). Follow the steps in order and test after each change.
Preparation
- Login for the TripleZero iT customer panel.
- Access to DirectAdmin, CyberPanel, Plesk, or the VPS console — depending on your product.
- A current backup or snapshot if you change something structurally.
- The exact hostname or IP you will be testing on.
Steps
- Open the customer panel of TripleZero iT and choose the VPS (status, IP, console).
- Check that the machine is running. Start or restart only when no snapshot is in progress.
- Log in via SSH (Linux) or RDP (Windows), or use the noVNC console if you have network problems.
- Make the change associated with this article and note the old setting.
- Test from another network: ping, HTTP/HTTPS, mail ports or RDP/SSH — as appropriate.
Check whether it was successful
- Does the service work from another network or 4G (no old DNS cache)?
- Do you not see any new 4xx/5xx or auth errors in logs?
- Is the time correct: DNS-TTL, Microsoft-verification or SSL-issuance may take minutes.
If things still go wrong
Reset the previous value if the change is clearly the culprit. Write down error texts literally (no paraphrase). Send in a ticket to TripleZero iT: product, domain/IP, timestamp and screenshot.
Can't figure it out after these steps? Open a ticket at TripleZero iT via the customer panel. Mention your domain name or VPS hostname, the time and what you have already tried.
Related: articles about snapshots, firewall, DNS to the VPS and managed versus unmanaged.