

crt is required for upload. A PEM-encoded certificate looks like this in notepad/text editor: Adminstrators are required to download CSRs and upload certificates for both Primary and Spare MX Appliances with the custom certs Primary | Spare tab only visible when the MX Appliance is in High Availability mode.ĭownloading CSR: Administrators can generate a certificate signing request (CSR), that can be signed by a public Certificate Authority.Ī PEM-encoded certificate like. Custom certs is supported in High Availability mode.Administrators will need to renew certificates manually in addition to managing their DNS record (to enable their hostname resolve to the MX IP on the Internet) Custom hostname certificates do not renew automatically.Requires MX firmware 16.11+ and needs to be enabled by the Meraki Support.
