Invalid username and password on 1st web server login
I'm starting to set up my 2nd Tiny Pilot Voyager. The first one went fine, but on the 2nd one, I'm getting this error, when trying to log into the web server: Invalid username and password on 1st web server login
I logged in first through SSH, updated the unit, created another account, and changed the passwords. Next, I tried to log into the web server using: pilot/flyingsopi, and got this error. Any help would be appreciated.
- 3 replies
- Michael Lynch @michael2021-03-31 19:17:30.463Z
Sorry about that!
flyingsopiare the SSH credentials, but they're distinct from the credentials for the web interface.
When the user changes settings from the web interface to require username and password, they choose their own credentials. The credentials should be whatever credentials were specified at the time. If you've forgotten the credentials but you still have SSH access, you can reset the password with these commands:
sudo service tinypilot stop && \ pushd /home/tinypilot && \ sudo mv tinypilot.db tinypilot.db.old && \ popd && \ sudo service tinypilot start
Also, you mentioned two devices, so I recommend going to System > Change hostname to give the devices distinct hostnames. If they're on the same network and they both are named
tinypilot, it can cause networking issues.
Thanks Michael! I was able to recover, and set a new account/password. Also, I have renamed the hosts, since they will be on the same network, in a remote location. I plan to clone the Micro SD drives, and send an extra with each unit, in case something gets corrupted, since the only access to the units will be shipping them back and forth. From the FAQs, it looks like I should disable writing to the SDs, to protect them, once everything is set up the way I want. Am I reading that correctly?
- Michael Lynch @michael2021-04-01 18:19:45.127Z
From the FAQs, it looks like I should disable writing to the SDs, to protect them, once everything is set up the way I want. Am I reading that correctly?
It's not something I recommend to everyone, but it does reduce the chance of microSD corruption and decreases wear on the microSD.
The downside is that it increases maintenance complexity. You'll need to enable writes again before you make any changes you'd like to stay persistent (e.g., software upgrades, changing passwords).