Guest Portal not working on 5.2

  • 4
  • Question
  • Updated 3 days ago
  • Answered
After upgrading our Virtual SmartZone and all AP Zones to 5.2, we ran into an issue with the Captive Portal on our Guest SSID's no longer working on R730's and R610's.  I don't know if any other model had the same issue, but after downgrading the AP firmware back to 5.1.2, Captive Portal was working again.  We had tried factory resetting the AP's, moving them to a different controller on same firmware, deleting and re-creating the SSID's, etc.

Support is working to replicate the issue, but wanted to make sure people knew what we ran into in case you see it as well.
Photo of Keith Gipe

Keith Gipe

  • 3 Posts
  • 1 Reply Like

Posted 6 months ago

  • 4
Photo of Liliia

Liliia

  • 20 Posts
  • 2 Reply Likes
Thank you for this info Keith! This was important to know. By the way, how often do you upgrade the APs? Can they be upgraded automatically by setting up a desired time for upgrade?
Photo of Keith Gipe

Keith Gipe

  • 3 Posts
  • 1 Reply Like
I typically go against the norm and run pretty bleeding edge.  We do have 2 separate controllers, so I will usually upgrade one within a week of new firmware being released, let it sit and then upgrade the other one within a week after that if no issues are found.  I upgrade the APs as soon as possible especially since we are running some of the new R730's and every new release has quite a few more features for the new AX AP's.

I don't know about scheduling a time for the upgrade, but one of the BEST improvements to 5.2 is you can now upgrade every AP Zone at the same time rather than going one Zone at a time!  That will save a LOT of time in the future.  Luckily we were able to keep the controller on 5.2 and just downgrade the AP firmware back to 5.1.2 for the time being.
Photo of Jeronimo

Jeronimo

  • 384 Posts
  • 49 Reply Likes
Do you mean Guest Access?
Photo of Jeronimo

Jeronimo

  • 384 Posts
  • 49 Reply Likes
After I did upgrade from 3.6.2 to 5.2, Guest accesss and WISPr works still good.
Photo of Keith Gipe

Keith Gipe

  • 3 Posts
  • 1 Reply Like
What model APs are you using?  We noticed it was only breaking on certain AP models for us.
Photo of Jeronimo

Jeronimo

  • 384 Posts
  • 49 Reply Likes
Here are R730 and R720
(Edited)
Photo of Liliia

Liliia

  • 20 Posts
  • 2 Reply Likes
Keith, this was important to know. Thanks for sharing your experience!
Photo of Giacomo

Giacomo

  • 2 Posts
  • 1 Reply Like
Hi Keith, we're having the same issue with our R510 and R310 access points and we worked around it by reverting the firmware to a 5.1 release too. Before we open a case, did support solve the problem?
Photo of Chris Foster

Chris Foster

  • 2 Posts
  • 1 Reply Like
Did you ever get to the bottom of this issue? I've recently upgraded our vSZ-H and suffering the same issue. We are running a mixture of R500, R720 and T300.

(Edited)
Photo of enas

enas

  • 2 Posts
  • 0 Reply Likes
I have a fresh install with vSZ 5.2 and R610 APs. The captive portal first works when we deploy it to a fresh added AP. After some time (days?) it does not work anymore.
We are still in development so I don't know exactly how much time it takes until it stops working. 

Once I could get it to work again when I redeploy the WiFi but this does not last long.
I'll revert to 5.1 as you suggested.

Bye Marco
Photo of enas

enas

  • 2 Posts
  • 0 Reply Likes
Can anyone give me a hint how I can downgrade the firmware?
Photo of Syamantak Omer

Syamantak Omer, Official Rep

  • 351 Posts
  • 126 Reply Likes

Hi Bye,

There are total thee ways to downgrade vSZ.

1st: If a cluster backup was created during last upgrade or before, then you can easily restore it and system will downgrade to previous version with all the settings.



2nd: If you don’t have cluster backup but a configuration backup was taken and available, then you can downgrade the vSZ using desired firmware or by deploying a new vSZ with desired firmware. Once this is done, upload the configuration backup and restore it.


3rd: If no cluster or configuration backup available then downgrading vSZ will factory reset its configuration and you have to reconfigure it from the scratch.

IMPORTANT NOTE: All 3 ways required downtime as system will restart or reconfiguration will be required.

Regards,

Syamanak Omer

Photo of Syamantak Omer

Syamantak Omer, Official Rep

  • 351 Posts
  • 126 Reply Likes
Hi Bye,

I forgot that it is a "fresh install with vSZ 5.2". In this case you cannot downgrade.

You have to spin-off a new instance on 5.1.2

Regards,
Syamantak Omer
Photo of Chris Foster

Chris Foster

  • 2 Posts
  • 1 Reply Like
That isn't my experience. I've literally 1 hour ago downgraded our vSZ-H using the below method.

Once logged into vSZ, navigate to "Access Points", from the Access Points dropdown menu, ensure that you change the View Mode to "ZONE"
then select the zone and from the "More" option select "Change AP Firmware"

Having completed downgrading all our zones from 5.2.0.0.699 to 5.1.2.0.373 our portal is now being received by the guest and are now able to continue to their desired web content.

Photo of Syamantak Omer

Syamantak Omer, Official Rep

  • 345 Posts
  • 123 Reply Likes
Hi Foster,

What you are referring is the AP Zone firmware change, which is different than vSZ downgrade.

You have explained it correctly though!

So if anyone wants to change just the AP version (AP Zone firmware), procedure given by you is correct. Or if want to downgrade entire controller, procedure given earlier by me is correct.

Thanks for highlighting!

Regards,
Syamantak Omer
(Edited)
Photo of Vineet Nejawala

Vineet Nejawala

  • 5 Posts
  • 1 Reply Like
Hi Everyone,

Did you get the update about the nature of the issue? This is a known defect on 5.2  build 699 with redirection issue on Guest/WisPr portal and is resolved in build 5.2.1 available at Ruckus website or you would need to disable lighttpd on the AP's by using AP CLI script. The command would be "set lighttpd disable".

If any concern or query please let me know. 

Best Regards
Vineet Nejwala
Photo of Jeronimo

Jeronimo

  • 387 Posts
  • 49 Reply Likes
Hi Vineet .

What is the command for?

Regards.


Photo of Vineet Nejawala

Vineet Nejawala

  • 5 Posts
  • 1 Reply Like
Hi Jeronimo,

The command is to disable Lighttpd i.e a light weight HTTP Server that will be providing all front end Web services in the AP. It was observed that in 5.2.0 lighttpd process was starting and stopping (crashing) as observed in the logs.

The usage of this command is as below, if you are having similar issue you can execute this command on one of the AP and test with a client :

rkscli: set lighttpd
Usage: set lighttpd {options}
-> {enable|disable}
-> debug {level}
-- set LIGHTTPD debug log level (0-2), or enabling/disabling lighttpd
0 = log disabled.
1 = basic debug log enabled.
2 = detail debug log enabled

rkscli: get lighttpd status
- Lighttpd status:
process state: running*
debug log level: 0
- server status/counters:

Best Regards
Vineet
Photo of Jeronimo

Jeronimo

  • 387 Posts
  • 49 Reply Likes
Thanks Vineet.

It's very helpful.
Photo of Vineet Nejawala

Vineet Nejawala

  • 5 Posts
  • 1 Reply Like
You're welcome Jeronimo. 

BR
Vineet
Photo of Giacomo

Giacomo

  • 2 Posts
  • 1 Reply Like
Hi Vineet,

I checked the release notes for 5.2.1 and there's an entry ER-8159 mentioning the guest access problem and the set lighttpd command, but it's in the Known Issues section, not in the Resolved Issues.

Does upgrading to 5.2.1 fix the problem on its own or both upgrading and using that command on each AP are needed?

Thank you,

Giacomo

Photo of Vineet Nejawala

Vineet Nejawala

  • 5 Posts
  • 1 Reply Like
Hi Giacomo,

Actually that is correct, you would have to wait for a week or two and there will be a patch available for 5.2.1 to fix this issue. So for now an AP script disabling the lighttpd on AP's is the only workaround available. 

Best Regards
Vineet
Photo of Andre Paiva

Andre Paiva

  • 5 Posts
  • 1 Reply Like
Hi, 
This seems to be a version inconsistency in version 5.2.
Follows:
1. Change the WLAN service to "Standard Usage";
2. Wait for the APs to change the status from "new-config" to "up-to-date";
3. Return the WLAN service to "Guest Access";
4. Wait for the APs to change the status from "new-config" to "up-to-date";
5. Test the Guest Portal.
Photo of Vineet Nejawala

Vineet Nejawala

  • 5 Posts
  • 1 Reply Like
Hi Everyone,

Since I am unable to edit my earlier comment let me rephrase. There is a known issue on 5.2.0 code related to redirection issue on Guest/WisPr portal and only available workaround is to disable lighttpd on the AP's by command "set lighttpd disable". This could be used in an AP script and pushed from controller to all connected AP's.

The command is to disable Lighttpd i.e a light weight HTTP Server that will be providing all front end Web services in the AP. It was observed that in 5.2.0 lighttpd process was starting and stopping (crashing) as observed in the logs.

NOTE : This issue still persist on 5.2.1 code though soon an AP patch (to resolve this issue) would be available for 5.2.1.

Best Regards
Vineet
(Edited)