For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

N__197982's avatar
N__197982
Icon for Nimbostratus rankNimbostratus
Sep 19, 2017

F5 certificate not working for all ports.

Folks, We have a wild card certificate configured on the F5 and this certificate caters to a VIP which listens to all ports. i.e. http://hostname.externaldomain.com:**.   For some reasons the cert...
application delivery
LTM
N__197982's avatar
N__197982
Icon for Nimbostratus rankNimbostratus
Sep 19, 2017

Attached is the output.....does this mean some SSL path issue? But that works fine if a static port is used. i.e. if I use 8110 only.

 

[root@dhcp-172-29-141-96 ~] curl -k https://noname-01.domain.com:8110 -v * About to connect() to noname-01.domain.com port 8110 (0) * Trying 1.2.3.10... connected * Connected to noname-01.domain.com (1.2.3.10) port 8110 (0) * Initializing NSS with certpath: sql:/etc/pki/nssdb * Unable to initialize NSS database * Initializing NSS with certpath: none * Unable to initialize NSS * NSS error -5925 * Closing connection 0 * Problem with the SSL CA cert (path? access rights?) curl: (77) Problem with the SSL CA cert (path? access rights?)

 

[root@dhcp-172-29-141-96 ~] curl -k https://noname-02.domain.com:8200 -v * About to connect() to noname-02.domain.com port 8200 (0) * Trying 1.2.3.10... connected * Connected to noname-02.domain.com (1.2.3.10) port 8200 (0) * Initializing NSS with certpath: sql:/etc/pki/nssdb * Unable to initialize NSS database * Initializing NSS with certpath: none * Unable to initialize NSS * NSS error -5925 * Closing connection 0 * Problem with the SSL CA cert (path? access rights?) curl: (77) Problem with the SSL CA cert (path? access rights?) [root@dhcp-172-29-141-96 ~]