Security

Use these precautions when installing the addon or managing a VPS. Available security controls depend on the installed release and hosting provider. Ask your provider about its access, logging and privacy practices rather than assuming a guarantee from a feature name.

Account Access

• Use a unique, strong password and protect access to your email account.
• Enable additional authentication controls when your panel offers them.
• Grant only the permissions needed for each person's work.
• Avoid sharing administrator accounts or granting administrator access for routine VPS use.
• Remove access that is no longer needed.

Administrators should give installation credentials only the privileges required by the documented setup. Do not broaden permissions just to suppress an unexplained error.

Secrets

Keep passwords and service credentials in secure storage, not public notes or screenshots. Only public SSH keys belong in the panel; private keys must stay on your own device. See SSH Access for key selection and login guidance.

Treat console links and clipboard contents as sensitive. If credentials are exposed, change or revoke the affected credentials through the appropriate service and contact your provider. Deleting a public post is not a substitute for replacing an exposed secret.

TLS Validation

Use HTTPS for the panel and keep certificate validation enabled for configured connections. If a browser or setup step reports a certificate error, check the hostname, certificate and trust configuration. Ask the hosting provider or administrator to correct the problem instead of bypassing validation. Do not enter credentials through a connection with an unexplained certificate warning.

Guest Security

Keep the operating system and applications updated. Expose only the services you need, with management access restricted where practical. Use trusted installation media and check publisher-provided checksums when available. Maintain separate backups and test that important data can be restored.

Tenant Isolation

Manage only instances, networks and storage you are authorized to use. Do not share account access to let another person reach a single resource; use supported scoped permissions where available. Private networking does not replace authentication, encryption or firewall rules.

If another customer's information appears unexpectedly, stop accessing it and report the issue privately to your provider. Do not probe other accounts or publish the exposed information.

Private Diagnostics

Before sharing logs or screenshots, remove passwords, private keys, credentials, connection links and unrelated personal data. Share only the smallest relevant excerpt through a private support channel. Do not publish full configuration files or diagnostic archives.

Useful details include the time, affected instance, installed version if known, attempted action and redacted error text. For ordinary failures, start with Troubleshooting. Report security concerns through your hosting provider's private support channel, or the addon's supplied support contact if you administer the installation.