6.10.0 - Unable to Log in via Web GUI, Able to Log in via SSH

[gregoryn22]

Hi Friends,

 

I am experiencing an issue where (after upgrading to 6.10.0), I find myself unable to log in via the Web GUI using a known good password. I am able to use the same password to successfully log in via SSH, which I then use to remove my password from the shadow file. After rebooting, I am able to log in once when creating a new password, but subsequent attempts to log in fail. I am able to again log in via SSH, and the cycle continues.

 

So far, I have tried moving my OS to a brand new USB, in case a failing USB was the culprit - however this ultimately had no effect.

 

I have attached my diagnostic zip here.

 

Thanks as always for the help everyone!

 

Edit: As an update - downgrading to 6.9.2 make this issue stop occurring. I guess for the time being, I'm on 6.9.2.

 

tower-diagnostics-20220520-1322.zip

Edited May 20, 2022 by gregoryn22
Update to initial issue

[ljm42]

Sorry for the trouble, excellent troubleshooting BTW

 

It looks like you have an unraid.net certificate that you aren't using, let's delete that while you are in 6.9.2. Open a web terminal and type:

rm /boot/config/ssl/certs/certificate_bundle.pem

 

Use SSL is set to No, your Local TLD is "local", and your HTTP port is 85, so the two valid urls to access the system in 6.10.0 are:
  http://192.168.0.158:85 
  http://Tower.local:85
6.9.2 was a little less strict, where you using a different url there?

 

If you are up for trying again, please do the following:
* Grab diagnostics in 6.9.2, for comparison
* Do the upgrade
* Clear your browser's cache. Seriously, this could be the issue.
* Access one of the urls above and Sign In
* If it still fails, please use SSH to generate new diagnostics and upload both here

[gregoryn22]

Hi ljm42, sorry that it took me a few days to get back to this.

 

I followed the steps you specified, and still seem to be experiencing the same issue. I cleared my browser cache, as well as tried from a few devices (using Chrome incognito tabs to prevent any extensions or other things interfering). Luckily, my server is far from critical, so rolling back to 6.9.2 is no big deal to me.

 

I have attached both the diagnostics from 6.9.2 and the 6.10.1 update.

 

Hopefully this information is helpful and allows the folks who are smarter than me to take a look and make Unraid even better for everyone

tower-diagnostics-20220523-1713 (6.9.2).zip tower-diagnostics-20220523-1953 (6.10.1).zip

Edited May 24, 2022 by gregoryn22

[ljm42]

I'm sorry, but I really don't see any why you would not be able to login using either of these urls:

  http://192.168.0.158:85
  http://Tower.local:85

in Unraid 6.10.1 if those same urls work in 6.9.2. Thank you for testing multiple systems in incognito mode. 

 

The next release has a change that will potentially help people who are using the default ports of 80/443. But you don't need that change because you are using non-standard ports. At the moment I am somewhat stumped.

[ljm42]

Do you have a user starting with the name "root", like "rootshare"? If so that was the issue, it has been fixed in 6.10.2.

[gregoryn22]

On 6/6/2022 at 4:32 PM, ljm42 said:

Do you have a user starting with the name "root", like "rootshare"? If so that was the issue, it has been fixed in 6.10.2.

It looks like this was it! I did have an additional user with root in the name ("noroot", as a read-only user). It looks like everything seems to be in working order now! Thank you for following up