Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Password still not working after 6.10.1 upgrade

Featured Replies

Hey everyone,

 

all the way back when RC-1 came out, I tried upgrading, but it was stopped in its tracks because I was unable to log in with my correct credentials.

 

I rolled back to 6.9.2 and everything worked fine again.

 

Now that 6.10 is released as stable, I tried again, and I still cannot log in with the WebGUI.

I tried downgrading to 6.9.2, setting the password to only letters, upgrading again, it still doesn't work.

 

I tried removing/renaming the shadow file, which prompts me to set a new password.

I set the password, press "logout", and I can not log back in again.

 

The shadow file is written to, there's a new hash in there, so this seems to have worked.

But it just won't let me access the WebUI?

SSH works fine.

 

The flash drive is fine, permissions are fine, there don't seem to be any corrupted files.

I have no idea how to proceed here.

 

This is the only thing that shows up in the log (I stay logged in after resetting the password until I log out again)

May 26 04:47:09 UMS webGUI: Unsuccessful login user root from 192.168.178.84

 

Edited by Spiritreader

  • Author

I figured it out. 

 

There seems to be an issue with how the WebGUI matches usernames.

I have a user called "rootshare" which exposes all shares via a custom smb config.

When this user account exists, unraid's WebUI attempts to match the password for "rootshare" instead of "root".

Using the password for the "rootshare" user then works for the "root" user.

 

Seems like an oversight? (username.startsWith() / username.Contains() or something?)

Edited by Spiritreader
clarification

I submitted a bug report internally for this a couple of hours ago.  

If it helps at all, I have this same issue. I also have a second user containing root in its name ("root-smb"). Using the password for smb-root with the actual root user allows me to log in.

 

Thanks for the workaround @JonathanM!!

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.