I have added a wildcard SSL cert for my custom domain with seperate cert and intermediate files; HOWEVER when I access the app it uses the *.mybluemix.net cert.
Is there something else I need to do? Is there any way of debugging? Is there a lag between uploading the cert and it becoming available?
Thanks for any help in advance!
Answer by Armakuni (139) | Oct 17, 2014 at 12:16 PM
Turns out there is a different IP for using [custom] SSL.
At time of writing it's: 75.126.81.68
That's good to know : ) I'm still getting errors at the bare domain though.
$ curl -sv https://domain.com/
* Hostname was NOT found in DNS cache
* Trying 75.126.81.68...
* Connected to domain.com (75.126.81.68) port 443 (#0)
* successfully set certificate verify locations:
* CAfile: none
CApath: /etc/ssl/certs
* SSLv3, TLS handshake, Client hello (1):
* SSLv3, TLS alert, Server hello (2):
* error:14077458:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 unrecognized name
* Closing connection 0
Hello @wamoyo , were you able to resolve this?
How to enable multiple Intermediate Certificates and a Root Certificate? 3 Answers
How to use custom SSL certificate for Liberty web app 1 Answer
How can I add a certificate into cacerts in Bluemix Liberty Runtime 1 Answer
dot (".") inside a subdomain name in Bluemix 0 Answers
SSL certificate for a specific subdomain on Bluemix 1 Answer