- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Content translations are temporarily unavailable due to site maintenance. We apologize for any inconvenience. Visit our blog to learn more.
02-06-2022 07:25 PM
When you generate the CSR it needs to be the name that you actually want to use for the server certificate going forward, as you will need to use that same name when you import the server certificate to "tie" the private key to the certificate in question. Your Root and Intermediate certificates it doesn't matter, you don't have a private key to associate with that so you're just doing a normal certificate import.
From your screenshot you didn't import the server certificate with the same name of the original CSR (Digi-RSA), so the firewall doesn't know to tie the private key to the imported server certificate. Re-import the server certificate with the exact same name as the original CSR. In your screenshot where you were "successful" in importing the certificate on the firewall is missing the private key because it wasn't imported with the proper name.