Standard PI install on Pi3B
Changed password to a very complex one after install
Login to web front end is fine using new password
Added SSH file to the /boot dir
SSH requests password and always returns login incorrect / permission denied.
Expected Behaviour:
Expected that login would be u/n: pi p/w C0mpl3xp@ssword and that access would be granted
Actual Behaviour:
Tried every username I know of and this password yet login still fails.
Can anybody confirm that the username is pi and whether this should have a different password by default than the one I have set.
As mentioned there's nothing unusual about this build - it is totally stock following the website instructions.
As far as I know that password has never been changed and does not work!
When I log in directly via the console (with monitor plugged in) it just logs me in.
How do I figure what the password is ???
As far as I know the ssh password is the same for your user as the one you use to login via console.
If you normally login with pi:yourpassword
it should work with ssh pi@IP_of_your_Pi using yourpassword
I still don't know where you set C0mpl3xp@ssword. If you set it for pihole's web interface via pihole -a -p it will only work there and not for user login/ssh.
So you don't know the password of the pi user?
If you never changed it, it should still be raspberry. As password are stored in hashed form, there is no way to "recover" it.
You can reset it as decribed here:
As I'm not using raspbian, I've never tried it myself. If you change it, it is likely the auto login won't work instant but need to be reconfigured.
I had the same issue, my keyboard layout was set to UK instead of US, so my password was wrong when I typed in on the RPi, after changing the keyboard layout on the RPi to US and doing a passwd everything worked like it should
pi@ph5:~ $ sudo passwd pi
New password:
Retype new password:
passwd: password updated successfully
This worked perfectly - again another step that is not documented.
Live and learn.
Many thanks to everyone concerned for their help!
As a non-linux guru (I'm a cisco network engineer) that means absolutely nothing to me!
All I can tell you is that on raspbian with a standard build that your instructions fixed the issue.
This is one of my problems with Linux. As much as I love it nothing is standardised. It's different for Fedora, different for RedHat, different again for Suse, you can YUM in this distro but this one does it totally differently...etc etc
Headache to get anything done - even the simplest tasks require forum support and googling which may or may not be the correct way to do things for that distro.
To that end I'll continue to rely upon the helpful goodwill of people such as yourselves on the specific forum, so thank you.
Are you RPI connected by ethernet first or in wifi.
Because first time you had to have ethernet connection and a SSH empty file in the main SD or SSD.
If on ethernet did you try ssh pi@xxx.xxx.xxx.xxx
First time ask you a choice.
And after password.
If ok do
sudo raspi-config to go on wifi configuration
Are you RPI connected by ethernet first or in wifi.
Ethernet with WiFi disabled
Because first time you had to have ethernet connection and a SSH empty file in the main SD or SSD.
Not true. I didn't - I have done since and can now SSH to it. There is no instruction to add the SSH file to the /boot folder in the setup instructions. I discovered this since with some help from this forum. You do not need to have an SSH file to connect with a local Keyboard and mouse to configure. I assumed that I'd be able to SSH by default but that is not the case.
If on ethernet did you try ssh pi@xxx.xxx.xxx.xxx
Yes. It didn't work or I wouldn't have raised a query on the forum.
First time ask you a choice.
And after password.
If ok do
sudo raspi-config to go on wifi configuration
I think I understand what you're saying (although the english doesn't make any sense) but I've already resolved and accepted a solution. Thank you for your input.
For someone who battles that big spaghetti wired monster lurking in the server room, with only a laptop, telnet and a serial cable, the transition shouldn't be that hard sudo just elevates permissions to the privileged root user.
And the root user doesnt have to enter previous password when changing password for a user.
But as sudo can be configured in many ways, this solution is not always possible.
Also for an outsider, it may look like there are many differences between the different distro's, but most of the times the toolstacks used underneath are still the same: iproute2 for IP stuff; iw for WiFi; bluez if it concerns Bluetooth; openssh for SSH; openssl for SSL/TLS; systemd for services; cron to schedule things; udev for plug and pray;
ALSA and Puslaudio for sound;
and oc the Linux kernel.
Arent there allot of similarities between IOS and Linux distro's ?
