I am currently out of town, and my server went down. All my services go through nginx, and suddenly started giving error 502. My SSH won’t let me in. I had my sister reboot the server, and it still doesn’t work. I apologize for the lack of details, but that is all I know, and I can’t access logs. I’ve cleared cache, and used a VPN in case fail2ban got me. I recently got a tp link router, so it could be something with that, but it was working for a while. I will have her do another reboot, and if that doesn’t work I will have her power off and unplug the server in case it was hacked.

Edit: I have absolutely no clue why, but it works now. I literally did nothing. As far as I know, my sister hasn’t touched it today. It just started working. Computers, man…

Edit 2: Actually she said she did something. Not sure what, but it works now.

  • ThrowawayOnLemmy
    link
    fedilink
    English
    1
    edit-2
    4 months ago

    I edited my original post right when you replied, my bad.

    I dunno if you can do that much remotely, honestly. I kinda feel like something might have corrupted? What kinda system are you using? Any more details you can provide?

    • @HumanPerson@sh.itjust.worksOP
      link
      fedilink
      English
      14 months ago

      I don’t think it is a hardware issue. I have decent hardware that’s fairly new. I unfortunately can’t say much, though another commenter let me know the SSH failure message is relevant. It see connection closed, which means that it is probably failing to boot. I think an update or something may have broken it, though it is debian stable, so Idk. I’m going to try to call my sister and see if I can get a picture of an error message or something.