I dont think there is anything to do now, except manually interact with your server.
For next time, I suggest buying a smart plug, smart outlet, whatever you call it, and configure your server bios to always come back on after power comes back to it.
Though, if you fucked the network settings of your machine, that wouldn't fix anything about it.
What I have is a Raspberry Pi with a wireguard vpn on it, so in the worst case, I can ssh into it, then SSH into a server in the same local network.
But again, if the network settings are so fucked that it doesn't even connect to the local network anymore, there is nothing much to do except going to the server and fixing it there.
Unless you have a PiKVM (Its a raspberry pi with an HDMI In/Out that can interact with your computer even if its off), an IMPI/ILO/iDRAC (its a chip on server motherboards that can power on/power off/show screen of the server even if it's off).
I dont think there is anything to do now, except manually interact with your server.
For next time, I suggest buying a smart plug, smart outlet, whatever you call it, and configure your server bios to always come back on after power comes back to it.
Though, if you fucked the network settings of your machine, that wouldn't fix anything about it.
What I have is a Raspberry Pi with a wireguard vpn on it, so in the worst case, I can ssh into it, then SSH into a server in the same local network.
But again, if the network settings are so fucked that it doesn't even connect to the local network anymore, there is nothing much to do except going to the server and fixing it there.
Unless you have a PiKVM (Its a raspberry pi with an HDMI In/Out that can interact with your computer even if its off), an IMPI/ILO/iDRAC (its a chip on server motherboards that can power on/power off/show screen of the server even if it's off).
Good luck for your adventures