By default mapping the certs to the domains is not necessary, BitNinja does this automatically, however in case the automatism that should gather the certs fail or get the wrong cert we have provided this workaround.
Since version 3.7.7 you can manually add each domain’s SSL cert’s location if necessary.
In this guide, we will walk you through manually setting up cert mapping. You’ll need to locate the cert and key files to get started.
Wildcard SSL Certificates like *.example.com are not supported yet.
If you have a combined certificate, you need to use the location of the combined certificate for both the certificate file and the key file.
Not every domain has a chain file. However if one of the domains has a chain file, it must be included in the mapping as:
Not every domain has a chain file. However if one of the domains has a chain file, it must be included in the mapping as:
| --chainFile=<chainFile>- Open the Configuration menu on your BitNinja dashboard.
- Select the setting level on the left side. (server-level, server group-level, account-level)
- Turn off the Config parser module: Advanced Modules -> Protection on HTTPS
- Map the certificate’s location to the domain with this command:
bitninjacli --module=SslTerminating --add-cert --domain=<domain> --certFile=<certFile> --keyFile=<keyFile>
Chained certificates can be also added with the following parameter| --chainFile=<chainFile> - Finally run our recollect command:
bitninjacli --module=SslTerminating --force-recollect