Nginx certificate does not match common name

By: Hernan Quevedo user 18 Oct 2017 at 12:22 a.m. CDT

4 Responses
Hernan Quevedo gravatar
Hi. I think this is an easy one. Replication is working now for two nodes of Gluu and one Nginx balancer, I can login to the web console, everything seems to be working correctly. But, when the app tries to get scim response, the Nginx balancer passes through a certificate, from principal Gluu server with a different hostname than the nginx host. So I get: ``` SSLException: Certificate for <NGINX_FQDN> doesn't match common name of the certificate subject: GLUU_PRINCIPAL_SERVER_FQDN ``` I followed the steps of [manual clustering](https://gluu.org/docs/ce/3.0.2/installation-guide/cluster/), stuck on step 7.
CentOS 6.7
closed

Answers

By Chris Blanton user 18 Oct 2017 at 12:22 p.m. CDT

Copy
Chris Blanton gravatar
Hernan, What about step 7 is giving you problems? ``` SSLException: Certificate for <NGINX_FQDN> doesn't match common name of the certificate subject: GLUU_PRINCIPAL_SERVER_FQDN ``` All the certificates should have the FQDN of your NGINX server. Did you use the NGINX server FQDN as "hostname" when you ran setup.py on your first instance?

By Hernan Quevedo user 18 Oct 2017 at 2:27 p.m. CDT

Copy
Hernan Quevedo gravatar
Chris, thanks... Damn... I didn't. At this point, could I run setup.py again in principal server and fix this when exporting the certificate again?

By Chris Blanton user 18 Oct 2017 at 3:14 p.m. CDT

Copy
Chris Blanton gravatar
Hernan, No, that would probably break a lot of things, but if you know the process it shouldn't be too hard to do again. https://imgur.com/a/Cqu8E Note in the image that both my Gluu servers hostnames (The top bit) are NGINX.gluu. This is for certificate issues routing between the two.

By Hernan Quevedo user 18 Oct 2017 at 3:30 p.m. CDT

Copy
Hernan Quevedo gravatar
Chris, thanks so much. Yeah, I think I now know the process by heart. I'll let you know how it goes.

Post an answer