Chrome doesn't like my Ruckus web admin SSL cert any more

[JSchlackman]

I've had a cert from my internal CA installed on my Ruckus controller ever since the controller was first installed. It used to work just fine. However, a couple of months ago, Google Chrome (and only Chrome) started complaining that the server name doesn't match when I try to access the web interface:

 

 

As you can see from the above error, it appears to be utter nonsense, because Chrome displays both the cert name and the server name in the message, and they are identical.

 

Firefox and IE don't have any problem with this cert; it is in date, and the CA is trusted. Chrome itself also used to have no problems with this cert.

 

Any ideas why this is happening?

[pete]

What does chrome think of your other .internal certs?

[JSchlackman]

No problems with any others issued by the same CA.