Restore a backup if i can't access my server?

What type of hardware are you using: Other ARM board
What YunoHost version are you running: unsure
How are you able to access your server: Direct access via physical keyboard/screen

Describe your issue

hi ynh,

i have had unknown issues with my server for a while (things running extremely slow, if using web admin, repeated disconnection errors), and as of 4-5 days ago i can’t access it at all.

i have tried the dynDNS address, yunohost.local, and the IP on the local network, including via ssh, including enabling password access for SSH and trying that way.

it boots ok (sshd, etc. load ok), i can use an external screen to see it boot.

i am wondering if it is possible/advisable to restore a system backup that i have? but as i am unable to access ynh at all, i can’t use its backup restore functionality. is there another way i might do it? can i plug the hdd into my laptop and restore somehow? or is it better to obtain a USB keyboard and log in that way and restore?

i run ynh on a rock64, with /boot on the microSD card, and the rest of the install on an ext HDD.

as i never worked out the issue, i am unsure if the OS itself needs reinstalling, if the SD card should be flashed again, etc. (i doubt it, as it boots fine), or if the HDD itself is in trouble, but i thought to first try restoring a ynh system backup if possible.

a while back, when the slowness started, i ran fsck on the HDD, and it found and fixed numerous errors. i tried it again today and it reports no errors. it might ultimately be a disk issue, but i thought to try fixing it before starting from scratch on another disk.

any pointers appreciated, thanks.

Share relevant logs or error messages

n/a

i’m not totally sure, but i think the last i saw of my beloved ynh was attempting to login to the admin system via yunohost.local in the browser, after submitting credentials, the server errored, i think it suggested that yunohost itself was in a broken state.

since then i was unable to log in via SSH also, even after reboot. i would get denied (“publickey”) when trying to use key access, and Connection closed trying to use password access. this is very strange as i didn’t change anything related to SSH and never had any issues before.

You have direct access to the hardware, right ?
Could you plug it in a screen and see what’s happening, and maybe login in CLI ?

I do. I can see it boot cleanly. I currently don’t have a USB keyboard to log in though. I can try to obtain one.

Getting a USB keyboard is probably the most direct next step: since it boots cleanly and you have a screen, log in on the local console and check systemctl status ssh plus the SSH logs before restoring anything. If you can reach the YunoHost CLI there, yunohost backup list will show available backups and yunohost backup restore <name> can restore one. Plugging the HDD into a laptop is less straightforward because the backup is usually a YunoHost archive, not a bootable system; local console access also lets you inspect whether the HDD or services are failing first.

ok, thanks for sharing some details about how to proceed. I’ll try with a keyboard when I can get one and try your suggestions.

Before restoring, you probably should to check some basic things:

Have you some free space on all partitions (disk)

df -h

What’s the status of essential services like slapd, yunohost-api, sshd

systemctl status sshd
systemctl status slapd
systemctl status yunohost-api
systemctl status yunohost-portal-api

Are you able to run a yunohost command ?

yunohost user list

Have you a network issue ?

ping 185.15.58.224
ping -4 wikipedia.org
ping -6 wikipedia.org
ip -br a

Have you a /tmp in your fstab, if yes it could be recent bug

grep "/tmp" /etc/fstab

Are you in a broken apt state

apt update
apt full-upgrade

What the diagnosis says

yunohost diagnosis show

I hope this answer was helpful. Please keep in mind that most of YunoHost’s development is done by volunteers, including this answer. Some of them earn less than the minimum wage in their country. If you can afford it, please consider donating to the 2026 fundraising campaign to help us keep this project going without putting anyone at risk.

Hello.
And what should be done in that case?

So on the console, using a USB keyboard, it seems to hang after I enter my username and hit return, it doesn’t ask for password. I tried on various TTYs, and rebooted. (Perhaps this also what was happening via SSH.)

On one such time, I got “Login timed out after 60 seconds.” (After much more time than that.)

@ljf, thanks for your suggestions, i’ll go through them if i manage to log in.

i have a spare/empty HDD, i wonder if i am unable to log in, maybe i could restore a system back up to it?

i tried again after letting it sit for an hour or so, and how i can log in and ssh.

``grep "/tmp" /etc/fstab``

i have this /tmp in my fstab. i guess i just delete?

yunohost user list

this errors with a python backtrace and

ldap.SERVER_DOWN: {'result': -1, 'desc': "Can't contact LDAP server", 'ctrls': }

restarted slapd, nginx, postfix, all of which were failed (on boot).

i continue to get LDAP errors when trying to run sudo commands in the terminal, and also when i ran the diagnosis in the web UI.

`Failed to read info for $APP : {'result': -1, 'desc': "Can't contact LDAP server", 'ctrls': []}`

but the diagnosis successfully ran in the end.

everything runs extremely slowly, so the underlying issue is still there.

If you have /tmp into your fstab, you could run systemctl unmask tmp.mount and reboot. It’s a workaround for the bug, i am working on a good fix.

If everything is slow you should check if it’s not dns resolution (see the section network issue in my first answer).

Check also hardware health