Firefox collects certificates and will compare incoming certificates. If these certificates match but come from different sources Firefoxs throws the annoying certificate conflict message.
The HTTPS certificate on the WLC lives at MANAGEMENT-->HTTP-->CURRENT CERTIFICATE
Where the problem arrives, controllers shipped in batches appear to have the same identical certificates. This could be because they “blast” the firmware on the boxes in the manufacturing process.
An example of a factory provided certificate is below. First noticed there is no CN information and the validation date is way off. This same certificate was on all the controllers in the batch.
The first controller you log into Firefox would accept and store this certificate. However, any controller you attempted to log into afterward would receive a certificate conflict.
So, how do we fix this issue? It's very simple …
After you configure your WLC with an IP address. Simply go to MANAGEMENT-->HTTP and click on regenerate certificate. It will fill in a proper validation date and more specific CN information giving the certificate its true identity. However, this does require a controller reboot. So schedule accordingly. Below is a regenerated certificate.
Thats it! It should work now! Enjoy ....