Bare Metal / Management
Lock and unlock a server
Protect a server from accidental management changes and unlock it when maintenance is needed.
Lock a server after setup to prevent accidental changes from the cloud console or API automations. The server keeps running while locked.
Lock the server
- Open Baremetal Servers in the cloud console and select your server.
- Under Settings, open General.
- Turn on Lock service.
- Confirm Lock service and wait for the success message. The server now shows Locked.
The lock applies after confirmation; it does not require a reboot or a separate Save changes action.
What the lock protects
The lock blocks these management actions:
| Action | While locked |
|---|---|
| Power on, shutdown, restart, and BMC reset | Blocked |
| OS deployment, reinstallation, and hardware tests | Starting or cancelling these operations is blocked |
| Interface and bond changes; attaching or detaching Virtual Networks | Blocked |
| Server deletion | Blocked |
Locking does not stop an operation already running. It also does not suspend billing or revoke SSH and RDP access: changes inside the operating system remain possible.
Boot settings and remote-console access remain available while the server is locked.
Unlock for maintenance
Return to Settings → General, turn off Lock service, and confirm Unlock service. Wait for the success message, carry out the planned change, then lock the server again.
See Power controls and Deploy a server for common maintenance tasks, or Bare metal API concepts for the API's lock behavior.
Canadian and 
Dutch
