Troubleshooting • Re: Connection Refused Error

Since your configuration is just a point-to-point network with only 2 nodes, perhaps there is no device to assign the IP addresses?

I'm not at all convinced we're talking about a point to point, DHCPless network. I'd expect the error to be different if that were the case.

Pi5 implies Bookworm. Bookworm implies Network Manager. Unless things have changed in the last week or so NM doesn't like DHCPless networks and won't bring up the interface on the Pi.

In which case I'd expect a failure in name resolution (e.g. Could not resolve hostname foo.local: Name or service not known) rather than "permission denied".

To me, at least, "permission denied" (or perhaps more specifically "Permission denied, please try again.") implies that connection to an ssh server has succeeded but login is failing.

@OP:

The usual reasons for that are:

• Connecting to the wrong server
• Using the wrong password
• Using the wrong username
• Using both the wrong username and the wrong password.

It also depends somewhat on the ssh client in use and on its invocation.

ssh raspberrypi.local will not prompt for a username. Instead it will use the name of the currently logged in user on the machine running that command. If the local user is foo that's the username passed to the Pi.

ssh bar@raspberrypi.local also will not prompt for a username but will use bar instead of the local username.

Graphical clients vary but most will result in a prompt for both username and password if only a hostname is provided.

For clarity, if you want to specify both user and server the syntax is user@host e.g. pi@raspberrypi.local

Note: the above assumes Raspberry Pi OS. Other OS may do something else.

[edit]Don't try clicking those links. For some reason the forum software thinks they're email addresses.[/edit]

Statistics: Posted by Makify — Wed Nov 20, 2024 3:01 pm