My Raspberry Pi 4 became inaccessible reddit / selfhosted ---------------------------------------------------------------------- Arimetix · 2023-10-15 07:06 Hi guys, I come in your help in dire need :( the thing is I was trying to create File Browser as docker container in my rpi server through windows cmd. The thing got stuck in a loop while deploying the container, so I closed the window. Then, when I tried to logging with passwordless ssh I got the message "Permission denied (publickey)". Now I can't log in with ssh keys or password because I disabled it long time ago (big mistake).. These are the docker lines I used to provoke this mess: docker run \\ \-v \~/:/srv \\ \-v /home/arimeberry/filebrowser/database/filebrowser.db:/database/fil ebrowser.db \\ \-v /home/arimeberry/filebrowser/config/settings.json:/config/settings .json \\ \-e PUID=$(id -u) \\ \-e PGID=$(id -g) \\ \-p 8080:80 \\ filebrowser/filebrowser:s6 If there is anything I can do to revert this I will be very grateful! Also, I should note I can still use portainer somehow. Thanks! ​ ---------------------------------------------------------------------- ixipaulixi · 2023-10-15 07:33 It's been a while since I've used a rpi, but it's just Linux, so you should be able to boot it into single user mode and reset the password. Here you go: https://forums.raspberrypi.com//viewtopic.php?t=127471 ---------------------------------------------------------------------- HeliumRedPocketsWe · 2023-10-15 07:56 What does it show when you plug it into a monitor? ---------------------------------------------------------------------- thekrautboy · 2023-10-15 08:08 Remove the memory card and mount it on another pc, edit the config files to make it boot or atleast accessible through ssh again. /r/raspberry_pi /r/linuxquestions Your Docker deployment has nothing to do with your SSH refusing a publickey login, and it has nothing to do with selfhosting. ---------------------------------------------------------------------- Other-Technician-718 · 2023-10-15 08:54 Plug your rpi to a monitor and keyboard. We can't guess any error logs from here without you providing them to us - we don't even know what OS you are running if everything is up to date, what other software / containers you have installed. An other way would be to access your sd-card and have a look at the logs and then accordingly adjust config files. And the third one: Restore the backup you took before you started deploying a new container.