Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


Shells Virtual Desktop
BMail.ag - Secure Email Service
Server.net
CPLicense.net
VPS Server
Buy VPN
Vultr
VMs for AI
HostDare
ReliableSite White-Label Dedicated Hosting for Resellers
InterServer VPS
BMail.ag - Secure Email Service
Best VPN
High-Performance Bare Metal Server Solutions
Karvl.com
Server Mania Cloud Hosting
DataWagon Hosting
AlphaVPS Hosting
Evoxt.com
Clouvider
VPS Hosting with NVMe
Residential IPs in the US & 4G Mobile Proxies in EU & US with Unlimited Bandwidth
ReliableSite White-Label Dedicated Hosting for Resellers
Rabisu - Hosting Solutions
Shells Virtual Desktop
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

KS-LE-B - Can't log in even in rescue mode

fuqetfuqet Member
edited December 2025 in Help

Hi,

Has anyone experienced a similar problem? My server stopped working today, and I can’t connect to it via SSH. I have tried using rescue mode, but there was no response from the server.

Thanks for any advice.

Comments

  • Cooked

    Ask OVH

  • I'm assuming you already tried requesting a reboot through the management console after changing the netboot to customer rescue system? If that didn't work, enable monitoring with interventions if you haven't already, use live chat to contact support, and be prepared to wait several hours for a resolution. I had one that wouldn't boot due to a bad BIOS option and it took them like 4 hours to return the server to my control after clearing the CMOS. I suspect they ran some sort of hardware diagnostic. If your server has faulty hardware, you may need to wait up to 48 hours for it to be repaired.

  • I had a similar issue once with my KS-LET-1 and it just suddenly disappeared from the internet. Logged into the control panel and requested a reboot and it still didn't appear. Then requested reboot into recovery so I could investigate and it never happened.

    Got an e-mail about 10 minutes later (unprompted) saying they were investigating why the recovery boot didn't happen and triggered an internal watchdog. About half an hour later, got a follow up e-mail saying the power supply had failed, they'd replaced it and everything was up and running again.

    So, if you don't have the auto monitoring stuff on, try interacting with it in the control panel to see if it's still alive. It could well be some kind of hardware issue. Or could just be routing to whatever DC / rack you're in.

  • Thank you for the answers. I've already contacted OVH and I am waiting for a support to answer.

  • @ralf said:
    I had a similar issue once with my KS-LET-1 and it just suddenly disappeared from the internet. Logged into the control panel and requested a reboot and it still didn't appear. Then requested reboot into recovery so I could investigate and it never happened.

    Got an e-mail about 10 minutes later (unprompted) saying they were investigating why the recovery boot didn't happen and triggered an internal watchdog. About half an hour later, got a follow up e-mail saying the power supply had failed, they'd replaced it and everything was up and running again.

    So, if you don't have the auto monitoring stuff on, try interacting with it in the control panel to see if it's still alive. It could well be some kind of hardware issue. Or could just be routing to whatever DC / rack you're in.

    That's the reason I always keep the monitoring enabled. Had a few similar problems, always fixed within 30 minutes at max.

    @fuqet said:
    Thank you for the answers. I've already contacted OVH and I am waiting for a support to answer.

    Yea, waiting for support can take ages. Did you create a ticket yourself or did you went to live chat? Live chat is in my experience much faster.

  • It is well cooked chicken, but hopefully not too burned.

  • conceptconcept Member
    edited December 2025

    Yup monitoring with intervention enabled will help a lot in these situations. They fixed it before I even realized it was down

Sign In or Register to comment.