InterServer dedicated

The whole credential is a single API key, created under Account Security at my.interserver.net, the same key as the VPS line. There is no host to type and no fingerprint to read; the endpoint is fixed and carries a publicly trusted certificate.

A dedicated server is physical hardware, so it has no soft power switch the way a VM does. Provibr drives its power over IPMI: start switches the chassis on, stop pulls the plug, shutdown asks the operating system to close down (ACPI), and restart cycles the chassis off and on again.

Provibr ignores every server it has not been told about, so nothing appears on its own. Open the integration, import the machines you want to manage, and they join your server list.

Once a machine is imported, Provibr reads its status and network and drives its power over IPMI:

• Start, stop, shutdown and restart map onto the chassis actions: three of them are hard power events, so treat them the way you would the button on the machine itself.
• Power is confirmed by reading the chassis state back, so a power action takes a moment to settle. Provibr waits for the machine to reach the requested state.
• Cancelling ends the service. See below, because it does not work the way delete does everywhere else.

IPMI has no pause, and a powered-off dedicated server is billed exactly as a running one until the service is cancelled. Powering a machine off therefore costs the same and gains nothing.

Ordering a machine, the IPMI console, metrics, firewalls and reinstalling are all off. Ordering a dedicated server at InterServer opens a support ticket and takes hours, not minutes (a person provisions the hardware), so it belongs to a later release with an explicit decision, not a self-service button.