<FQDN>
: tls.crt
<FQDN>
: tls.key
.intermediate.pem
.rootca.crt
.cert.pem
privkey.pem
.chain.pem
.<DEPLOYMENT-FQDN>
below.*.<DEPLOYMENT-FQDN>
: wildcard.crt
*.<DEPLOYMENT-FQDN>
: wildcard.key
DIY-SSL-CA/CA/pubCA.crt
in your unpacked installer assets.
<FQDN>
tls.crt
/ cert.pem
tls.key
/ privkey.pem
rootca.crt
, if applicableintermediate.pem
/ chain.pem
, if applicable<DEPLOYMENT-FQDN>
, or <FQDN>
if identical. Do not include an asterisk.wildcard.crt
if different; tls.crt
/ cert.pem
if identical.wildcard.key
if different; tls.key
/ privkey.pem
if identical.cacert.pem
. To download the latest version of the root CA trust file, run the command:
cacert.pem
per the instructions above. If you have a private root CA, append it to that file:
fullchain.pem
has already been provided for you.
certificates.yaml
, then add the following information to it:
certificates.yaml
file with an encoded version of the actual certificate and key. Run the commands that fit your environment:
If you have a single certificate with an intermediate, run the following commands:
certificates.yaml
file now contains the correct certificate and key by running the following command:
certificates.yaml
file has been successfully created.
If the command returns a message, re-verify the file name and its contents are correct, then run the command again.
gravity-certificates.yaml
, then add the following information to it:
gravity-certificates.yaml
file with an encoded version of the actual certificate and key by running the following commands:
gravity-certificates.yaml
file now contains the correct certificate and key by running the following command:
gravity-certificates.yaml
file has been successfully created.
If the command returns a message, re-verify the file name and its contents are correct, then run the command again.
gravity-certificates.yaml
file you created by running the command: