Login failed - Access denied

[vfricke]

After sucessful setup using Android app BerryLan a ssh login failed to the device. User pi password raspberry resulted in message "Access denied". BerryLan image is being used as base image. Any idea of the problem? Thanks

[nymea-jenkins]

Hi! Just out of my mind: BerryLan is a slightly modificated Rasperry OS Image. I think SSH has to be explicity enabled. User and password should be the same as any other Raspberry OS.

On 09.08.2023, at 17:11, Volker Fricke @.***> wrote:

After sucessful setup using Android app BerryLan a ssh login failed to the device. User pi password raspberry resulted in message "Access denied". BerryLan image is being used as base image. Any idea of the problem? Thanks

— Reply to this email directly, view it on GitHub https://github.com/nymea/berrylan/issues/84, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEUDTAGERG2J6OTLZRMJ45DXUOSB7ANCNFSM6AAAAAA3KFCDKE. You are receiving this because you are subscribed to this thread.

[vfricke]

Hi! Just out of my mind: BerryLan is a slightly modificated Rasperry OS Image. I think SSH has to be explicity enabled. User and password should be the same as any other Raspberry OS. … On 09.08.2023, at 17:11, Volker Fricke @.***> wrote: After sucessful setup using Android app BerryLan a ssh login failed to the device. User pi password raspberry resulted in message "Access denied". BerryLan image is being used as base image. Any idea of the problem? Thanks — Reply to this email directly, view it on GitHub <#84>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEUDTAGERG2J6OTLZRMJ45DXUOSB7ANCNFSM6AAAAAA3KFCDKE. You are receiving this because you are subscribed to this thread.

Correct. However BerryLan is designed for head-less operation. When you use Rasperry OS with SSH disabled it does not make much such. You want to have an image which provides you a head-less login with SSH enabled, right?

[mzanetti]

The plain BerryLan image is intentionally designed with minimal modifications to the upstream Raspberry pi OS image, that is, just adding the nymea-networkmanager and nothing else. User can then set up their services and then move the RPi between wireless networks easily.

Your argument is valid though, that without ssh it somewhat defeats the purpose of allowing to do the initial setup headless too.

[vfricke]

So, what is the solution to the problem? Will you update the standard image to allow ssh connections per default?

[mzanetti]

I'm still somewhat reluctant to change the default setup. As I said, it's intentional to have minimal changes there to give the people something they are familiar with and don't have ssh enabled with the default user/password without knowing it. We provide another image, with a full nymea setup which also has ssh enabled. I understand that using the nymea image may not be an option for everyone either.

The other option would be to use the Raspberry Pi Imager to flash the berrylan image (select custom image, pick from the hard drive) and then use the options of the imager to enable ssh:

Would that work for you?

[vfricke]

Yes. Thank you.