Controller 4100 management via Mozilla-Firefox

[ERWIN STAELENS]

Hi

Does anyone of you use Mozilla-Firefox to control the Controller 4100?

This because I get an error whenever I try to connect to a second controller via https.

I already have a tab page with one controller via https, now I want to open a second tab page to another controller via https too.

Then Mozilla show me the next pop-up:

Your certificate contains the same serial number as another certificate issued by the certificate authority. Please get a new certificate containing a unique serial number.

Indeed, all Cisco controllers are having the same serial number.

Is there some kind of workaround?

Internet explorer doesn't have this problem.

[frankzehrer]

Hi Erwin,

try to clear out the certificate for the WLC in your browser

1. Open Firefox

2. From the top menu, click "Tools > Options".

3. Click the "Advanced" icon.

4. Click the "Security" tab.

5. Click "View Certificates" button and then the "Web Sites" tab.

6. Click on the first website listed and click "Delete". Repeat this process till all are removed.

7. Click "OK".

I hope that helps.

Best regards,

Frank

[ERWIN STAELENS]

Hi Frank

thanks for your reply.

I have done the actions stated in your answer and I don't see any website's listed. The space is blank.

I'm running Firefox version 1.5.0.7

During https connection I get the pop-up and there I can only choose the option 'accept this certificate temporarily for this session'.' I can not accept this certificat permanently.

Erwin

[Stephen Rodriguez]

It has to do with how the tabbed broswing works in Firefox. I have the same issues as well. The two workaround I know of is to close the browser entirely, or enable http to the controllers, and then you will not get the certificate issues.

[ERWIN STAELENS]

Hi all

I just got confirmation from Cisco that Mozilla is not a supported browser yet. Only IE is supported...

[andrewhoyos]

I had this same issue - Once I upgraded to 179.8, and recreated the certificates on the controller, the issue went away.

[tcorey]

I have the same problem on two 4404 controllers. The core problem is that the controllers always use the same serial number for the self generated certificate. Of stated another way both controllers use the same serial number for the certificate.