I goto https://<controller-ip/via/ and receive the via login page. I am able to present my username and password, and I know it is verifying it because if I present a wrong password the login fails. If I present a correct password, I'm given a broken page that looks like the attached png (since the forum won't let me upload text that has xml in it)
Does your password have a semicolon?
Yes as a matter of fact it does. I guess I should try a user account that has a password that doesn't contain a semicolon? Is this a new problem that was introduced into 126.96.36.199? Same password didn't seem to be a problem in 188.8.131.52.
Fixed in 184.108.40.206
Thanks you've answered my question within a couple of minutes of posting. I have a ticket that I opened on friday and spent a couple of hours with support debugging before I declared I had chosen a day to open the ticket when I didn't have enough time available and we'd have to continue another day.
I hadn't seen that 220.127.116.11 was out yet, and I see that 18.104.22.168 is out too since the last time I looked. I see no mention of this bug being a known issue or resolved in 22.214.171.124. Would you expect that that means that 126.96.36.199 got the fix for this issue as well? We have some AP-515's on order, so I'll need to move to 8.4 to suport them. I'm contemplating whether I move to 188.8.131.52 now, and 8.4.0.x (maybe a newer release will be available by the time we recieve the 515's) as a second step, or go straight to 184.108.40.206.
It is possible the bug did not make it to the release notes in time, but I see every indication that it is fixed in 220.127.116.11.
Just like every 0.0 release, I would wait for the first set of patches before diving into 18.104.22.168 I would go to 22.214.171.124 since it would not present you with a ton of new unknowns.
I held off and didn't install 126.96.36.199. I finally this weekend installed 188.8.131.52 because we have some new AP515's that we need to start installing so we can finish installing them before our college summer break is over. After installing 184.108.40.206 I'm seeing behavior similar to what I saw with 220.127.116.11. My username can't log into a new via client, but was able to log into an existing one that was already set up until I deleted the profile there. Now that computer behaves like its a new computer and I fail to authenticate successfully. It's not a ; in the password this time, but could it be some other character? Anyone know of an issue that is along this line for 18.104.22.168?
It's hard to be happy using VIA as our VPN solution when I need to upgrade the controller for reasons that have nothing to do with VIA and then half of the times I upgrade via breaks......actually it's more than half of the time. Since we started using VIA I've upgraded 3 times. The first broke it, second fixed what the first broke, and now I suspect but haven't proven yet, that upgrade #3 broke it again.
At Aruba, we believe that the most dynamic customer experiences happen at the Edge. Our mission is to deliver innovative solutions that harness data at the Edge to drive powerful business outcomes.
© Copyright 2021 Hewlett Packard Enterprise Development LPAll Rights Reserved.