• collapse_already@lemmy.ml
    ·
    24 days ago

    I am glad I have not kept a count of how many times I have broken ssh in my life. My reaction to this is visceral apprehension. "I've triple checked it, what could go wrong?"

    Advice: backup the file and set a cron to revert to the backup in an hour. If it still works, cancel the cron.

  • footfaults [none/use name]
    ·
    24 days ago

    Does nftables have something where you can apply the new config for a couple seconds then revert?

    Either that or a shell script where you apply the new config, sleep 60 seconds then apply the old config?

  • Chronicon [they/them]
    ·
    24 days ago

    ouch no backup way in? most hosts have a serial console or rescue image or something you can boot to to fix this kind of thing. onsite technicians fixing software problems is very 90s/early 2000s

    • TankieTanuki [he/him]
      ·
      24 days ago

      It's a dedicated server so the only way to boot a rescue OS is in-person (afaik).

      • Chronicon [they/them]
        ·
        24 days ago

        depends on the provider, but that may well be true for your provider yeah