Certificates

Certificates are used to support secure HTTPS traffic. They help prove the identity of a domain and allow encrypted communication.

When to use Certificates

Use Certificates when you need to:

• view certificates configured in the gateway;
• add a certificate for a domain;
• update certificate details;
• remove a certificate that is no longer used.

Understand the Certificates list

The list shows Certificate ID, Status, SNIs, Expiry Date, Tags, Created, and available actions. Check status and expiry regularly; a saved certificate is not necessarily valid for the hostname or still within its validity period.

Add a certificate

1. Open Gateway Configuration.
2. Select Certificates.
3. Select Add Certificate.
4. Paste the public Certificate and matching private Key in PEM format.
5. Add an alternative certificate and key only when the approved TLS setup requires them.
6. Add the Server Name Indicators (hostnames) served by the certificate.
7. Add useful non-sensitive tags and save.

If you are not sure which certificate values to use, ask the person or team responsible for your domain or infrastructure.

Field guide

Field	Required	What to enter	Notes
Certificate	Yes	The public certificate text.	Usually starts with -----BEGIN CERTIFICATE-----.
Key	Yes	The private key that belongs to the certificate.	It must match the public certificate. Treat it as a secret.
Alternative Certificate / Key	No	A second approved certificate/key pair when required.	Supply both parts of the pair; do not mix keys between certificates.
Server Name Indicators	Yes	Hostnames that should present the certificate.	Example: api.example.com. The names must be covered by the certificate.
Tags	No	Optional labels.	Use tags to make records easier to search.

Update a certificate

Open the certificate from the list, replace the required certificate/key pair, review SNIs and tags, and select Save Changes. Plan renewal before expiry and verify the new chain and hostname coverage outside the portal before replacing a live certificate.

Certificate safety

Certificates can affect live traffic. An incorrect, expired, incomplete, or mismatched certificate/key pair may cause security warnings or prevent client systems from connecting.

Never paste a private key into email, chat, screenshots, tickets, or documentation. If a private key may have been exposed, follow your organisation's incident process and replace the certificate rather than merely deleting the message.

If HTTPS fails after an update, check the SNI hostname, certificate validity dates, intermediate chain, key match, and whether the client is reaching the expected gateway endpoint. Restore the previously approved certificate if the change window and recovery plan allow it.