Rescue system
Repair a server that no longer boots or that you are locked out of.
The rescue system is a small Linux (based on Ubuntu 24.04) that your server boots instead of its own disk. Use it after a broken update, a full disk, a bad firewall rule inside the OS or a lost root password.
Enter rescue
In the console open the server's Rescue tab and choose Enable rescue, or call the API:
curl -X POST -H "Authorization: Bearer $ODX_TOKEN" https://api.odinex.cloud/v1/servers/42/actions/enable_rescueThe server restarts into the rescue system right away; it is reachable within about a minute on the same IP
addresses. The response contains a root_password, shown only once. Log in as root with that password, with
the SSH keys the server was created with, or through the browser console.
Work on the disk
Your server's disk is attached unmounted as /dev/sda; nothing on it changes until you change it.
rescue-mount # mounts the root file system on /mnt (LVM aware)
rescue-chroot # opens a shell inside your system, e.g. to run passwd or fix packagesChanges you make to the rescue system itself are discarded when you leave it; changes to /dev/sda stay.
Leave rescue
Choose Disable rescue (API: POST /servers/{id}/actions/disable_rescue). The server boots from its own disk again.
While rescue is enabled
Only leaving rescue and deleting the server are possible: power actions, rebuild, resize, password reset, snapshots,
volume and network changes are refused (409 rescue_enabled), and the daily backup skips the server. Billing and IP
addresses do not change.
The rescue system is not available for MikroTik RouterOS servers (409 rescue_unsupported).