WLC 5508 suddenly unable to access GUI (443)

[Alan.A]

Browser management access is working fine until one day I cannot anymore access it via browser (443). Access to CLI is working fine and telnet to 443 is open. what are the possible reason for this kind of issue?

[Tyson Joachims]

Check out this older community article and see if any of those suggestions work for you

https://community.cisco.com/t5/wireless/wlc-5520-no-https-web-gui/td-p/3189146

[Alan.A]

Thank you.. I will read it.

[Leo Laohoo]

What firmware is the WLC running on?

[Alan.A]

Hi Leo, This is the firmware.

Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 8.3.150.5

[Leo Laohoo]

---

@Alan.A wrote:

Product Version.................................. 8.3.150.5

---

Contact Cisco TAC. 

The controller is running an Engineering Release Special.  They are the only ones who know how this specific version behaves.  

[Alan.A]

Update:

1. tried to enable the webmode (port 80) but still unable to access.

2. Issued the command redundancy force-switchover and I am able to access the Gui again.

[craig.beck]

Most likely the switchover caused your browser to complain about the self-signed certificate on the standby WLC. Switching back made your browser recognise the cert so allowed you to see the GUI again.

[Scott Fella]

You have an issue with the one controller then that you can’t access using port 80 http. You should check to see if the controllers failed over to verify if that one controller took over as active or was already active prior to you being unable to access the UI. When you failed to the other controller, things worked, so again, you might have an issue with the one that is standby now. You should try to fail over again and see if the problem comes back. A force failover will bounce the controller and maybe that fixed the issue. If not, then maybe move off the code you are running or rebuild the broken controller to make sure it works or not. This way if you factory reset the broken controller and just setup basic connectivity using the startup wizard, you can test to see if https and http works. If not, then you need to RMA that controller.