Skip to content

Knowledgebase

Issuing a website certificate in Webuzo

control-panels, security-ssl

Issue a website certificate through Webuzo Automatic SSL after the domain points to the intended service and can complete validation. A valid certificate protects the connection for its listed hostnames; it does not automatically secure every server service.

What you need before you begin

Confirm the domain is active in the account and that both A and any AAAA records reach the correct destination. Record the required hostnames and existing certificate. Check proxy, redirect and CAA settings that may affect the selected certificate authority.

01 Issue a website certificate in Webuzo

  1. Open SSL > Automatic SSL in the end-user panel. Select the exact domain instead of starting a bulk issuance for unrelated sites.
  2. Check the certificate authority configured by the administrator and the names selected for issuance. Include only hostnames you control and can validate.
  3. Start installation and inspect its SSL logs. For HTTP validation, ensure the challenge path is reachable externally through the actual public DNS route.
  4. After successful issuance, inspect the certificate names, issuer and expiry date. Test the site over HTTPS before enabling a forced redirect.
  5. Update application URLs and fix mixed-content references as required. Avoid applying HSTS to an untested domain or all subdomains before confirming their HTTPS readiness.
  6. Monitor renewal status and retain working validation conditions. A later DNS or proxy change can break renewal even when the current certificate still works.

Why is HTTPS still wrong behind a proxy?

The visitor may see a certificate installed at the proxy rather than the origin. Verify both connections and the proxy origin settings; installing one certificate does not configure the other endpoint.

Confirm the expected result

Use an external browser or TLS client to inspect the certificate presented by the public hostname. Confirm the chain is trusted, the name matches and the application has no redirect loop. Check www and other intended names separately.

Troubleshoot unexpected results

For failed issuance, use the log to distinguish unreachable validation, invalid domain, suspension, CAA restrictions and authority limits. Correct the cause before repeated retries. Do not remove a currently valid certificate merely because a replacement attempt failed.

Was this answer helpful?

Need a little more help?

Our support team can help you find the next step.

Contact support

Powered by WHMCompleteSolution