Knowledge Base

Troubleshooting

Common issues across the three modules, roughly in the order you'll meet them.

The module row won't save

The row is only saved after a live OVH API call succeeds, so a save failure is a credentials problem:

  • Wrong endpoint for the token — tokens are endpoint-specific; a key minted on eu.api.ovh.com fails on ovh-ca/ovh-us.
  • Subsidiary doesn't match the endpoint (VPS/Dedicated) — e.g. US is only valid on ovh-us. See OVH API Credentials, Endpoints & Subsidiaries for the valid pairs.
  • Missing rights — re-mint the token with the full rights list for the module.
  • Wrong project ID (Public Cloud) — it must be the 32-character hex ID of a project the token can read.

Package fields are empty (no plans / flavors / images)

Package fields load live through a module row, so add the row before creating packages. If a row exists, check Tools > Logs > Module for the failing API call — an expired consumer key shows up here first.

New services sit "pending" forever

Activation is done by the 5-minute cron tasks (Check … Orders / Sync OVH Public Cloud Instances), so:

  1. Confirm the main Blesta cron runs (Settings > System > Automation).
  2. Confirm the module task is enabled under Settings > Company > Automation.
  3. Check Tools > Logs > Module for the order status OVH is reporting — dedicated delivery can legitimately take hours.

Auto-orders fail at checkout

The OVH account has no preferred payment method, or it was declined. Set one in the OVH Control Panel (Billing > Payment methods) and retry. Remember: auto-ordering spends real money — test packages with the import path (enter an existing service/instance name on the admin add-service form) before opening them for sale.

"Not available" on the KVM/IPMI tab (Dedicated)

Expected on ranges without IPMI hardware — most Kimsufi and some other Eco plans. It is not a module or credentials error.

Cancelling didn't delete the server (VPS/Dedicated)

By design: cancel turns renewal off (deleteAtExpiration) and the service lapses at its OVH expiry date. Immediate termination requires a confirmation token OVH emails to the account holder, so it must be completed in the OVH Control Panel. Until expiry, OVH keeps billing you. (Public Cloud is the opposite: cancel deletes the instance immediately and permanently.)

Configurable options look wrong or were hand-edited

The daily Sync … Option Prices task rebuilds each OVH VPS - {package} / OVH Dedicated - {package} group from the OVH catalog, overwriting manual edits. Adjust the package's Options Margin (%) instead, and let the next sync (or a manual cron run) reprice everything.

Where to look first

Every OVH API request and response is logged under Tools > Logs > Module (API keys are never written to the log, and console-access URLs are masked) — nearly every problem above leaves its explanation there.

Please rate this article to help us improve our Knowledge Base.

0 0