07-31-2025 08:01 PM
Hi, we setup foreign-anchor wireless network in our environment, but can't access anchor wlc mgmt IP via https, what is the possible cause? the engr who setup this wireless network already left. Now can still access anchor wlc via ssh, how to check whether https is enabled via cli? can someone please advise, thanks in advance. The wireless controller model is 5520.
Solved! Go to Solution.
07-31-2025 08:35 PM - edited 07-31-2025 08:36 PM
Anchor WLC is usually in DMZ of firewall so be mindful of that and make sure ports are allowed for services you are trying to access. via ssh run this command "show network summary" and confirm if you have these 2 services enabled
Web Mode.................................... Enable
Secure Web Mode............................. Enable
if its disabled, the enable them
config network secureweb enable
config network secureweb enable (this may require a reboot to take effect)
if enabled, then try different browser, incognito mode, check your firewall rules. Also make sure you are not on wireless network while trying to access controller via GUI
07-31-2025 08:24 PM
Can I have the output of 'show network summary' and 'show sysinfo' please.
07-31-2025 08:30 PM
what exactly do you get? HTTPS timeout, or certificate warning?
check running config for
config network secureweb enable
07-31-2025 08:35 PM - edited 07-31-2025 08:36 PM
Anchor WLC is usually in DMZ of firewall so be mindful of that and make sure ports are allowed for services you are trying to access. via ssh run this command "show network summary" and confirm if you have these 2 services enabled
Web Mode.................................... Enable
Secure Web Mode............................. Enable
if its disabled, the enable them
config network secureweb enable
config network secureweb enable (this may require a reboot to take effect)
if enabled, then try different browser, incognito mode, check your firewall rules. Also make sure you are not on wireless network while trying to access controller via GUI
07-31-2025 10:51 PM
Thanks @Haydn Andrews @Saikat Nandy @Saikat Nandy ! I found the root cause, it was blocked by the firewall. As you mentioned, anchor wlc is deployed in firewall dmz zone. Thanks a lot for your advice!
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide