Create and Inspect a CSR in Webuzo or Legacy Bread Basket

A certificate signing request (CSR) contains a public key and requested identity details. It is not an issued certificate and does not include the private key. This guide updates the older Bread Basket instructions using Webuzo’s documented panel workflow, with safeguards for request review.

Create the request

Use the SSL/CSR area for the correct Webuzo user and domain. Older Bread Basket/Webuzo skins may place it under Security. Confirm that this is the panel actually managing your service; do not assume the historical interface is available on every plan.

1. List the exact hostnames the issuer should cover, including any required subject alternative names.
2. Select or generate the intended private key through the trusted panel. Keep it recoverable and private; a certificate issued for a different key will not match it.
3. Enter the issuer-required country and identity information accurately. A challenge/passphrase field in a CSR is not the panel login password or a substitute for private-key encryption. Do not reuse an account secret there.
4. Create the request, then review its names and public-key details before submitting it to the issuer. Request fields alone do not establish domain control or organization validation.

View and export an existing CSR

The older separate View CSR article is consolidated here. In the panel’s CSR list, select the intended request and use its view/show action. Copy the complete request block, not the private-key block or an already issued certificate. Keep identifying information out of unnecessary public screenshots.

If shell inspection is appropriate, a local request can be checked without displaying its private key:

openssl req -in example.com.csr -noout -text -verify

A valid request signature proves the request is internally signed by its key, not that a public CA approved it. Confirm the SAN list with the issuer rather than relying on Common Name alone.

After issuance

Retain the matching key securely and install the returned certificate and required intermediate chain through the actual hosting workflow. Reissuing a request with a new key does not magically make an existing certificate match. Test the public endpoint and plan renewal separately.

References: Webuzo CSR workflow; historical view action; OpenSSL request inspection.

Reviewed October 15, 2026. Local request inspection tested with synthetic files; no customer panel request was generated.