OVH Dedicated Servers — Service Management

How dedicated-server services behave once the module is set up (see OVH Dedicated Servers — Setup).

Ordering and activation

Client orders run the OVH cart > checkout flow, auto-paid, including the mandatory Eco addons (RAM, storage, bandwidth) taken from the client's configurable-option choices or, failing that, the package defaults. Dedicated delivery takes minutes to hours; the service stays pending until the Check OVH Dedicated Server Orders cron task (every 5 minutes) sees it delivered, links the server, and — if OVH shipped it without an operating system — installs the package's Default OS Template automatically.

Importing an existing server

Add the service from the staff area and enter the server's OVH service name (e.g. ns1234567.ip-1-2-3.eu) in the module field; leave it blank to order new. Import spends no money and is the recommended way to test.

Service tabs

Staff and clients get the same management tabs:

Actions — reboot, OS reinstall, rescue-mode toggle.
KVM / IPMI — only present when Enable the KVM / IPMI console tab is checked on the OVH Account row (it is off by default; see OVH Dedicated Servers — Setup). Requests an IPMI/KVM-over-IP console session, which opens embedded in the tab (a fallback link opens it in a new window if the browser refuses to embed it). Shows not available on ranges without IPMI hardware (most Kimsufi and some other Eco plans) — that is expected, not an error.
IP Addresses — the server's IP addresses with editable reverse DNS.
Firewall — the OVH network firewall per IP and its rules.
Statistics — server details plus daily traffic.

Every OVH API call is recorded under Tools > Logs > Module. API keys are never written to the log, and KVM console URLs (which embed a one-time access token) are masked.

Suspend, unsuspend, cancel

Blesta action	What happens at OVH
Suspend	The server is rebooted into rescue mode — the client's OS goes offline but all data stays intact. The previous boot mode is remembered.
Unsuspend	The previous boot mode is restored and the server reboots back into the client's OS.
Cancel	Renewal is turned off (`deleteAtExpiration`) — the server lapses at its OVH expiry date.

Rescue-mode suspension keeps the hardware yours (and billable by OVH) while cutting the client off — appropriate for non-payment. Immediate termination cannot be done from Blesta: OVH emails a confirmation token to the account holder, so same-day deletion must be finished in the OVH Control Panel.

Heads-up: a cancelled server keeps costing you at OVH until its expiry date. Time client refunds and stock reuse accordingly — an imported, lapsing server can be re-linked to a new Blesta service via the import path.

Knowledge Base