04-28-2016 01:49 PM
For about a year I've been running 6 Aruba 105's in my network. Since the initial install they have been working flawlessly. Because of that I haven't accessed the Virtual Controller via the webgui for about half a year now.
This evening I figured I checked the webgui again. Unfortunately I'm not able to login anymore. After entering the correct address in my browser, I get presented with the login screen of the VC. However, after providing the correct credential, the webgui begins to load but within a second I return to the login page again without an error showing on screen.
Strange thing is that I am able to login to the VC using SSH, so credentials must be correct.
Elsewhere on this forum I found someone having the same issue, but this issue was solved by configuring the correct date/time on the VC via CLI. I've checked this on mine an both date and time are exactly the same as on the pc I access the VC from.
Also rebooting the IPA didn't do the trick.
Any ideas on how to troubleshoot/solve this?
Solved! Go to Solution.
04-28-2016 02:52 PM
something similar happened to me a year ago. It was not working with Safari, IE or Firefox, but it was working with Chrome.
Have you tried different browsers?
04-28-2016 02:59 PM
Yes I tried them all (Chrome, Firefox, Firefox Portalbe, IE (different versions), Safari, Edge). Result is exactly the same in all browsers. Login screen loads, webgui is displayed for about 1 second, then disappears and I'm presented with the login screen again.
Aruba OS version is 184.108.40.206-4.1.1 by the way.
04-28-2016 03:46 PM
have a look onto this thread: http://community.arubanetworks.com/t5/Aruba-Instan
Apparently they had the same issue and when they disconnected the master, they were able to access the UI again. However, the version of code was older than yours.
04-29-2016 02:25 AM
Although the situation described in the topic you mentioned was indeed not exactly the same, it did point me to a solution for my issue.
Since I monitor the network remotely, I had configured a port-forwarding rule in the router. This rule made sure that port 4343 was forwarde to the IP-address of the master IAP. Based on the topic you pointed me to, I used the CLI to dig a bit deeper and discovered that somehow another master IAP (different IP-address) was appointed and that I was effectively trying to login to a slave IAP.
After changing the forwarding rule to make sure it was explicitely pointing to the IP-address of the master, the webGUI worked again.
I still don't understand why it is apparently critical to point to the actual master IAP (as far as I understood all the slave IAPs should forward request to the master IAP) but at least it solved my issue for now.