Webuzo Certificates: Upload, Assign, Inspect and Retire Safely

Uploading a certificate, selecting it for a website and checking the served HTTPS endpoint are different steps. This Webuzo guide replaces the older Bread Basket create, view, upload and delete fragments while keeping those tasks distinct.

Prepare matching material

Confirm the correct domain, its required names, the issued certificate and the matching private key. Obtain the intermediate chain from the issuer. Keep the current setup recoverable and store keys outside public web directories. Never paste a private key into a public decoder, comment or ordinary support message.

Upload and assign

1. Open the intended user’s SSL/certificate area. Older Webuzo/Bread Basket releases use Security > Certificate; current labels depend on the installed version.
2. Choose the relevant domain and paste the complete issued certificate or upload the format the panel accepts. The historical interface documents .crt uploads; changing an extension does not convert a DER, PEM or PKCS#12 file.
3. Associate the matching key and supply the required intermediate chain through the trusted panel’s separate controls.
4. Confirm installation/assignment to the website, not merely addition to a certificate repository. Test every required hostname without bypassing warnings.

Create is not public-CA validation

A local Create action with identity fields does not demonstrate that a trusted issuer validated the domain. Inspect issuer and trust before using the result publicly. For normal public websites, use a supported automatic issuer or an issued certificate rather than telling visitors to ignore self-signed warnings.

View before changing

Select the intended entry and use its show/view action to inspect names, issuer and validity. Compare that information with the certificate visitors actually receive; a proxy or another virtual host can present a different certificate. A readable certificate file is not evidence that its matching key is installed correctly.

Delete only after checking dependencies

Do not delete an active certificate or matching key as routine renewal troubleshooting. Determine which names/services use it, arrange replacement or deliberate endpoint retirement, and retain an authorized recovery copy first. A certificate can cover several names. Check the deletion confirmation and re-test affected endpoints; automation may restore coverage if it still manages the domain.

Assign a renewal owner and monitor expiry. Uploading once does not establish an automatic renewal process.

References: Webuzo create/upload/delete documentation; historical view workflow. These sources inform the panel actions, not a claim that the installed customer version was tested.

Reviewed October 15, 2026. No customer certificate, private key or website assignment was uploaded or deleted.