# Web access to the Cisco WLC 2504
**URL:** https://forum.networklessons.com/t/web-access-to-the-cisco-wlc-2504/58832
**Category:** Wireless
**Created:** [August 5, 2026, 3:14pm UTC](https://forum.networklessons.com/t/web-access-to-the-cisco-wlc-2504/58832 "2026-08-05T15:14:34Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@mar.jaeger](https://forum.networklessons.com/u/mar.jaeger)
#### Post date: [August 5, 2026, 3:14pm UTC](https://forum.networklessons.com/t/web-access-to-the-cisco-wlc-2504/58832/1 "2026-08-05T15:14:35Z")
Hello,
I would like to access the Cisco WLC 2504 via the web interface.
In the Firefox browser, I receive a message stating that the Cisco WLC does not support TLS.
How can I install TLS on the WLC?
Or can I change something in the browser settings?
Thank you
---
### Author:  [@lagapidis](https://forum.networklessons.com/u/lagapidis)
#### Post date: [August 6, 2026, 5:57am UTC](https://forum.networklessons.com/t/web-access-to-the-cisco-wlc-2504/58832/2 "2026-08-06T05:57:54Z")
Hello Mar
TLS is not installed separately on a Cisco WLC. It is part of the AireOS software. The most likely problem is that the 2504 is running an old AireOS release that supports only obsolete TLS versions or cipher suites that modern Firefox versions reject.
To check what is actually running on the device, connect through SSH or the console and check the software and HTTPS settings using these commands:
```auto
show sysinfo
show network summary
```
If your AireOS release supports it, enable the stronger HTTPS cipher option:
```auto
config network secureweb enable
config network secureweb cipher-option high enable
save config
reset system
```
Cisco documents this option for both web administration and web authentication. It disables TLS 1.0 and enables the controller to use stronger HTTPS settings.
If the command is unavailable or the connection still fails, the controller probably needs an AireOS upgrade. The 2504 supports the AireOS 8.5 train, but you should verify that the connected AP models are supported before upgrading.
The alternative you can use as a temporary measure, is to enable ordinary HTTP from the CLI:
```auto
config network webmode enable
```
Then connect using `http://WLC-address` (not HTTP **S** ), perform the necessary upgrade or configuration, and disable HTTP again.
This should not be done permanently on a production network for security reasons. Only do this from a trusted, isolated management network because HTTP is unencrypted.
Also keep in mind that the Cisco 2504 reached its final support date on April 30, 2023, so a replacement should be considered for any production environment where security is an issue.
I hope this has been helpful!
Laz