New answers tagged csr
The other answers all seem to be correct but they may be missing the point. It seems to me that the real answer is don't do that. I can't imagine a use case that requires you to secure an arbitrary IP address; it seems like a bad idea for all the good reasons mentioned in the other answers. You lose the flexibility of decoupling the name from the IP address ...
You cannot generally get SSL certificates issued with an IP address as a subject name. Firstly, you have no basis with which to get such a certificate issued unless the IP block is delegated to you (from an RIR, for example). This means that unless you are listed and named in the whois information for that IP block, you will not get a certificate. ...
The Common Name must be the FQDN of the domain you want to request the certificate for. E.g. www.example.com It cannot be an IP address.
Top 50 recent answers are included