Use a valid certificate for the Webuzo panel hostname and for the mail or file-transfer service names clients actually use. Website certificates and service certificates are managed separately, so test each affected listener after deployment.
IN THIS ARTICLE
What you need before you begin
Use authorized administrator access and keep an existing administrative session or console available. Choose a stable hostname such as panel.example.com, ensure its public DNS is correct, and confirm the name is not an ordinary customer domain registered inside the panel.
01 Secure the Webuzo panel hostname
- Inspect Networking > Change Hostname and record the configured panel hostname. Plan a separate controlled change if the hostname itself is wrong.
- Open SSL/TLS > Manage Service Certificates. Select the intended Webuzo, mail or FTP service rather than assuming one selection covers every listener.
- Choose a supported certificate-authority workflow, an appropriate existing end-user certificate or a manual certificate as required. Check that the certificate names cover the actual client hostname.
- For manual installation, provide the matching private key, leaf certificate and required chain through the secure form. Never share the private key publicly or substitute another domain key.
- Apply the certificate and follow any service reload operation reported by the panel. Keep the previous working material protected until verification completes.
- Check renewal ownership and whether renewed certificates are deployed to the selected service. Add expiry monitoring for the hostname clients use.
Can I use a customer certificate for server services?
Only when it covers the service hostname and its lifecycle is reliable. A customer account removal or unrelated renewal change should not unexpectedly break administrative or mail access.
Confirm the expected result
Open the panel HTTPS address in a fresh connection and inspect the presented certificate. Test mail or FTPS listeners separately when changed. Confirm the certificate chain, hostname and expiry, then check that existing clients reconnect normally.
Troubleshoot unexpected results
If access fails after deployment, use the retained session or console to inspect the selected service and certificate. A name mismatch requires the correct hostname or certificate, not disabled client verification. Restore the prior valid configuration if the new deployment is incomplete.