SSH problems after update

I updated my dietpi install and now ssh isnt working. when i log in i just get this. I restarted my install just before logging out after the update. all services work except ssh.

im not sure if i have display enabled.. I’ll connect a display an just see if it shows anything..

don’t think this is related to the update. Can you try a different SSH client like Windows cmd tool. You can connect like

ssh root@<ip-address>
1 Like

cool :slight_smile: alrighty good thing. uhm why is putty doing that? i used powershell. I didn’t know that you could use it like this. guess i don’t need putty.. donkeys :slight_smile:

oh hmm weird its showing that i didnt update? it shows 9.0.2. hmm maybe another restart will clear it up?

EDIT: oh hmm i think i messed up something. i needed to update something else before the update apparently..

Support for Python 3.11.6 is being removed

This stops working in version 2024.4. Please address before upgrading.

how do i update python? did i mess it up?

This has nothing to do with DietPi. I guess you are using HA?

Any next time, pls fill the trouble shooting template as provided by the forum. Actually, we don’t know anything on your system

Required

  • DietPi version | cat /boot/dietpi/.version
  • Distro version | echo $G_DISTRO_NAME $G_RASPBIAN
  • Kernel version | uname -a
  • Architecture | dpkg --print-architecture
  • SBC model | echo $G_HW_MODEL_NAME or (EG: RPi3)

yes sorry sometimes my posts are not all there when i post them.. yes thats from HA. also remember i was only just able to log in.

DietPi version |G_DIETPI_VERSION_CORE=9
G_DIETPI_VERSION_SUB=0
G_DIETPI_VERSION_RC=2
G_GITBRANCH=‘master’
G_GITOWNER=‘MichaIng’

Distro version |bookworm

Kernel version |Linux DietPi 6.1.0-40-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.153-1 (2025-09-20) x86_64 GNU/Linux

Architecture |amd64

SBC model |Native PC (x86_64)

in this case it will not have any impact to the DietPi update as HA is using it’s own python environment that needs to be updated separately be reinstalling HA (don’t worry no data will be lost). However before taking a look into HA, you would need to update your old DietPi system to latest DietPi version.

i tried doing that last night lol that is when putty when bonkers and showed that stuff. i thought it was fully updated already before going into ssh connection. dietpi even has the “apt upgrade” in the remembered cmds on ssh connection.

EDIT: when reinstalling HA. do i just use the dietpi-software section to uninstall then reinstall?

simply run dietpi-update 1 the check the output, once finished, reboot your system

uhm HA says i need to do their update first thought. should i ignore that? sorry i made another reply instead of edit im kinda slow today. it says “This stops working in version 2024.4. Please address before upgrading.”

as long as you don’t update HA, nothing will happen to HA.
2024.4 is a HA version number and not a DietPi version or related to a DietPi version.
To be on save side, run dietpi-backup beforehand.

nope. as said, update DietPi as a first step. Otherwise you will not benefit from the adjustments done, as new HA python version depends on an updated dietpi-software script. HA is using an own python version that is hard code to our script. Continue running DietPi 9.0 will not offer any update for HA pyenv

using uninstall option will remove HA and all your projects

1 Like

what is backed up during a back up? just the os or everything in dietpi_userdata?

Depends where userdata is located

hmm looks like i left lots of old junk in the folders somewhere so its taking a little while to back up. or it could just be because its tons of tiny files and my ssd kind of is cheapo.

EDIT: is there a way to stop the backup?

please tell me how to stop it….i cant find how to anywhere…

You should not do any update without backup. Especially not on such old system like yours. You can keep it running or is there a reason to cancel?

because its a cheap ssd. meh nevermind its at 60% hehe

edit: this is very slow.. I wont be getting such a terrible drive for this purpose again…. >< this drive is a TEAMGROUP MP34. it is having a problem with all the small files i think..

this is taking to long.. how do i cancel it. it seems like its going to take 2 more hours. its been almost 2 hours..

would of been cool if u just told me how to cancel it.. :frowning: its still backing up. hopefully this doesnt ruin my ssd..

EDIT: backup failed 10 minutes ago. it tried backing up all drives to the one single drive…

can you share following

lsblk -o name,fstype,label,size,ro,type,mountpoint,partuuid,uuid
df -h
ls -la /mnt/

k ill try that in a few. the backup filled my ssd and bogged everything down till i deleted what it was able to back up..