Yunohost connection refused, including through SSH

I have searched the forum for similar issues

on

This category is for general issues regarding YunoHost, NOT apps.

on

This form is written in English :uk: but feel free to write in French :fr: if you’re more comfortable!

on

What type of hardware are you using

Raspberry Pi 3, 4+

What YunoHost version are you running

11.2.31

How are you able to access your server

The webadmin
SSH

Are you in a special context or did you perform specific tweaking on your YunoHost instance ?

no

Describe your issue

Hello!

Today, when attempting to access my yunohost server… I can’t.

When connecting to my server through the webpage, I get NS_ERROR_CONNECTION_REFUSED without an error code.

I have my yunohost statically set to port 192.168.1.196 in my local NAT. Directly entering that also gives me “refused to connect”. I can not connect from neither Edge nor Firefox.

I can not access via SSH, as I immediately get “connection closed by 192.168.1.196 port 22”. I do not allow SSH outside of my NAT, so this is all from the same building.

I have a separate yunohost instance that’s basically just for Immich, and it is up and connectable (through its IP / host file configurations, since it is typically behind a reverse proxy).

Restarting it is causing it to not appear on my network at all. I also restarted my router. I disabled the router-side static DHCP, and used angryipscanner, and it’s nowhere to be found. Can’t ping even.

Any ideas on what this could be? Where should I look for logs?

cf All services hosted by yunohost VM return 502 / connection refused ? (except I neither tried logging in, I have not touched the server in 24 hrs, and it is NOT behind a reverse proxy, though it does host a reverse proxy for a different server that seems to be working fine.)

I don’t have any good way to get physical access, but I’m sure I could find a microHDMI to HDMI cable + a spare monitor etc somewhere.

Share relevant logs or error messages

no access means no logs, sorry. If I am going to access logs, it will be through plugging its storage media into a different computer.

Images:
Screenshot 2024-10-24 113751

got a monitor and cable. Looks like it’s stuck at boot. Seeing the message
Read start4.elf bytes ... followed by a few numbers.
as well as
recover4.elf not found
recovery.elf not found

I’m assuming my installation is corrupted, the SSD/cable I was using is broken, the setup decided that it wanted to use more power all of a sudden, the RPI4 power cable decided it wanted to output less power all of a sudden, or my RPI is broken.

If this is a RPI issue, I apologize for polluting the forum.

Sorry for the pollution. The issue was that the raspberry pi’s bootloader committed suicide and regressed back to one from 2020. re-flashing it fixed it.

EDIT:

please disregard the above.

it worked first-try, had a kernel panic locked up, and has not worked since.

The bootloader did regress, but that was not the solution.

I think it was my choice of cabling. will update in a week.

EDIT2: SSD died. After half a year. Remote backups are important, and I learned that lesson just a bit too late.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.