Admin login details - not working via WebGUI, but works fine via SSH. Thoughts?

  • 1
  • Question
  • Updated 10 months ago
  • Answered
  • 1
Unable to login to SZ100 using admin login credentials. 
Photo of Skaap2.0

Skaap2.0

  • 30 Posts
  • 2 Reply Likes

Posted 1 year ago

  • 1
1 year ago
Photo of Martin

Martin, Official Rep

  • 310 Posts
  • 80 Reply Likes
For this please open a case with Ruckus support.

Do you have a recent configuration backup?


Kind regards
Martin

1 year ago
Photo of David Black

David Black

  • 71 Posts
  • 40 Reply Likes
Did you prefix the address with “https://“ and append the port number to the end “:8443” ? Example if the SZ address is 10.16.4.10, you need to enter https://10.16.4.10:8443
(Edited)
1 year ago
Photo of Skaap2.0

Skaap2.0

  • 30 Posts
  • 2 Reply Likes
Hi David, the WEB GUI loads fine. No issues there, just Admin login details doesn't seem to work. when trying to login.
1 year ago
Photo of Charles Sprickman

Charles Sprickman

  • 30 Posts
  • 10 Reply Likes
I'm not familiar with that device, but the login screen on some of the Ruckus products is totally broken in some browsers.  Specifically I've run into this on standalone APs. In Chrome, typing the correct password repeatedly results in a failed login (all extensions disabled). Switch to Firefox and in on the first try.

A long shot, but if it's the same frontend code, avoid chrome...
1 year ago
Photo of izagatsky

izagatsky

  • 3 Posts
  • 1 Reply Like
Could be this issue:  https://support.ruckuswireless.com/articles/000001909
I recently ran into this trying to log in into a factory defaulted AP.
1 year ago
Photo of David Black

David Black

  • 71 Posts
  • 40 Reply Likes
If the problem is with an additional admin account that you created after setup was complete, the issue could be that the account does not have an assigned role.  Provided that the super admin account that you created during the setup wizard still works, login and go to:
Administration
Admins and Roles
If needed, click the 2nd tab "Administrators" and create the new account (name, password, etc)
Next click the 1st tab "Create User Group"
Give the group a name (eg SZ Admins)
Assign the permission level (AP Admin, GuestPass Admin, Network Admin, Super Admin, etc...)
Assign the Resources that the group will have access to (SZ, APs, other admin accounts, etc)
Assign the new account that you created earlier to the group

The above is for newer versions (maybe 3.4 and later I think...).  If you're running an older version of SZ code (maybe 3.2 or earlier), the process is a little different.

1 year ago
Photo of Skaap2.0

Skaap2.0

  • 30 Posts
  • 2 Reply Likes
Hi David,

This is what seems to have happened, but i'm unable to login with the Super Admin details. a 2nd Admin account was created with read only rights. since then i've been told the Super Admin doesn't work. Is there away to delete the 2nd account via cli?
10 months ago
Photo of Michael Brado

Michael Brado, Official Rep

  • 3012 Posts
  • 425 Reply Likes
I've got it!  I filed ER-6965 with our Eng/QA team.  You can have special characters at the end of your Admin password, when you upgrade from SZ 5.0 to SZ 5.1 and it will still work.

If you change you password to have special characters at the end, after upgrading to SZ 5.1, WebUI will be broken, SSH still works.

Please change your Admin pw to NOT end in a special character (from SSH session), until this bug is fixed.
2018-12-19T21:57:32+00:00
Photo of Michael Brado

Michael Brado, Official Rep

  • 3012 Posts
  • 425 Reply Likes
Hello,

   Eng/QA have produced an engineering patch (.KSP) file to fix this issue.  Please open a ticket and ask the TSE to provide the .KSP from ER-6965.

This must be applied to each cluster node, and services restarted for it to take effect, but then test special character ending Admin passwords, and

let your TSE know so they can report back.
(Edited)
  • 1

Powered by Get Satisfaction