Switch from Dropbear to OpenSSH without other changes

Wanting to use SCP/SFTP, I attempted to switch my SSH server from Dropbear to OpenSSH using dietpi-software, however in doing so, it messed up my existing webserver setup (using apache2), so I reverted back to a recent image backup. Is there a way to switch from Dropbear to OpenSSH without changing any other software packages or other existing settings?

This is on a Raspberry Pi Zero W running headless, and running v146 of DietPi (yes I know it’s old).

I’m a newbie when it comes to linux, and my setup is based on a third party image created by Andreas Spiess using Peter Scargill’s “Christmas Script”, so I don’t personally know the specifics of the packages I currently have installed, however the apache2 setup I’m currently using is part of the image.



It’s okay. You can keep it and stay on it. It’s not the part of your problem.

Yes, I have hear of both of them. They do a lot IoT stuff.



Do a quick look into it.

If I read there:

They don’t use DietPi default apache2.conf that is part of your problem.

And Andreas Spiess has put in a “new” default user “pi” per special script and deleted user “dietpi”

How shall we support all done chances?
Can’t find any documentation and the “Peter Scargill’s” - “Christmas Script” is gone …

wget --no-check-certificate http://bit.do/the-script

As far as I can see, you can’t now use any “dietpi-*” without having problems.
Sorry to say this.
Perhaps Andreas Spiess will support his self build image.

What shall work, you can do this by “apt-get”.

apt-get purge dropbear
apt-get install openssh-server

and when disable dropbear startup services and make sure openssh is in startup services.

You have to google for it. e.g. https://blog.sleeplessbeastie.eu/2015/04/27/how-to-manage-system-services-on-debian-jessie/


Thanks for the reply!

I realized shortly after reading your reply that the backup image I had reverted to was made prior to making an important (to me) change that depended on a newer version of DietPi (I think it was v153 or so). That being the case, and not being able to update the v146 that I had on the image to the version I needed, I decided to download the newest image of DietPi (setting the default install to OpenSSH) and run Mr. Scargill’s script. The most recent version of the script is linked from the blog post at https://tech.scargill.net/the-script-step-by-step/. I ran the script today, and still have a few issues to work through, as there were a few things that didn’t install correctly. I’m assuming it may be because DietPi v6.2 is based on Stretch instead of Jessie (if my memory serves).


Hi Ben,

If you think, Debian Stretch is your problem , you can give Debian Jessie based Raspberry Pi version a try.


Hope it will help.

Interesting. I may have read it wrong, but I thought all the v6 images were based on Stretch. I downloaded the image you linked to, and I’ll give it a try when I get a chance in a few days. Thanks again for the reply.


For DietPi in general NO (for now).
All Odroid devices will stay on Jessie for the moment ( yet )
Why? Please seach forum or read on github.

For DietPi RPi builds YES and NO.
DietPi RPi Stretch build start about one ago. RPi Stretch status
But most people don’t notice, read, or follow this up.
Where are some “special” RPi builds, e.g. for AMIBerry or Allo, who take a little bit more time, to get it up and running with Debian Stretch as base.

You can get or download DietPi for RPi Wheezy | Support Ended (22nd June 2016) as well.
Sure, no DietPi updates, no fixes, no support by us any more, but it will work until now.
And it has Debian 7 “Wheezy” LTS until 31st May 2018 for security fixes by Debian.
Then we will take the link down.

To get it clear: