Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Password not being accepted after reboot. [20171003] #1165

Closed
crw opened this issue Oct 3, 2017 · 4 comments
Closed

Password not being accepted after reboot. [20171003] #1165

crw opened this issue Oct 3, 2017 · 4 comments

Comments

@crw
Copy link

crw commented Oct 3, 2017

Steps to reproduce (describing actions taken on two RPi3s):

  1. Updated (via the web-based update interface) to 20171003 on two RPi3 devices.
  2. Logged in as admin on web with previous password on both: success.
  3. Logged in as admin on ssh with previous password on both: success.
  4. RPi3 Working Great #1: rebooted to change a config setting (device name). After reboot, could no longer log in to web or ssh.
  5. RPi No email notifications after installing motioneyeOS #2: Changed password*. Rebooted. Could log in to web interface. Could no longer log in to SSH.
  6. RPi No email notifications after installing motioneyeOS #2: Disabled SSH, rebooted. Could no longer log into web interface.

* Changed to the same password. Since the password field only shows 5 dots, I thought this might be a problem.

Is there any way to regain access to these machines without reinstalling from scratch? Do you know if this is an issue with the new release, and should I wait before re-installing?

Note that I probably hadn't updated for around three to six months.

Thanks!

@crw crw changed the title Passwords no longer being accepted after reboot. [20171003] Password not being accepted after reboot. [20171003] Oct 3, 2017
@ccrisan
Copy link
Collaborator

ccrisan commented Oct 4, 2017

This looks like a duplicate of #1116. Although not clear yet, it might be caused by the use of an older (cached) version of the UI. If that is indeed the case, please try the following passwords:

  • sha1(""): da39a3ee5e6b4b0d3255bfef95601890afd80709
  • sha1("null"): 2be88ca4242c76e8253ac62474851065032d6833
  • sha1(<your admin password>)

You can obtain the corresponding sha1 digest using the Linux command line (echo -n "foo" | sha1sum) or you could use http://www.sha1-online.com/.

Please let me know if one of the password variants above matches so we can be sure it's a cache problem.

@ccrisan
Copy link
Collaborator

ccrisan commented Oct 6, 2017

After further investigation, it looks like it's indeed a browser cache problem and the password is set to either ***** or 133e3d6b775613651eaedbf7e609d244f2f852af.

@ccrisan ccrisan closed this as completed Oct 6, 2017
@ccrisan
Copy link
Collaborator

ccrisan commented Oct 6, 2017

And yes, this is indeed a duplicate of #1116.

@mrnoda
Copy link

mrnoda commented Oct 11, 2017

Just experienced this issue, 133e3d6b775613651eaedbf7e609d244f2f852af worked fine for me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

3 participants