Hetzner Robot Module

Connect Hetzner Robot to sell dedicated-server catalogue entries, automate server delivery and core lifecycle actions, and keep recurring and setup costs visible inside WISECP.

Reaching the Screen

Go to Products → Hosting Server → Hetzner Robot: {admin}/hetznerrobot

Activate the Module Menu

1. Open Products → Hosting Server and click Add New Server below the page title. On a narrow screen, first open Show Options to reach this button.
2. Under Server Automation Module, choose the Dedicated category and then select Hetzner Robot.
3. Under Connection Details, enter robot-ws.your-server.de in Address, your Hetzner Robot Web Service username in Web Service User, and its password in Web Service Password.
4. Click Test Connection. After the test succeeds, check the server name and required capacity fields, then click Add New Server at the bottom of the page.
5. The record is created as active. The Products → Hosting Server → Hetzner Robot menu now appears and {admin}/hetznerrobot becomes available.

What the Module Does

Catalogue and product control

The grid shows provider hardware and availability beside the generated product. Each row supports a public product name, fixed provider location, WISECP category, recurring EUR sale price, EUR setup price and active status. Import can create missing models or refresh stored recurring/setup costs; a cost-only refresh preserves existing sale prices.

Customer service tools

Customers can request a hardware restart, enter or leave rescue mode, reinstall from an allowed operating-system template, manage reverse DNS and view the additional IP list. The service dashboard shows server identity, hardware, location and status plus provider bandwidth data. Robot does not expose live CPU, RAM or disk utilization through this module.

Automation and lifecycle

Generated products receive operating-system, hostname, root-password and optional SSH-key requirements. Enabling the additional-IPv4 order step attaches a quantity add-on whose recurring and setup components can be priced with the module margin. The provider server number becomes the service relationship used by later lifecycle operations and cleanup.

Before You Configure It

1. Create a Hetzner Robot Web Service User and password with access to the dedicated servers and ordering functions WISECP will manage. The ordinary Robot panel login is not the intended credential.
2. Enable the HetznerRobot server module and create an active server record using that Web Service username and password.
3. Create and enable EUR in WISECP; catalogue recurring and setup amounts are processed in EUR.
4. Confirm the license and provider account capacity before placing a real dedicated-server test order.

Settings and Product Controls

Installation and Operation

Prepare Robot credentials

1. Create or select a dedicated Robot Web Service user for the automation account and give it only the provider access needed for the servers in scope.
2. Record its username and password securely; do not enter the normal interactive panel password by assumption.
3. Verify the same user can read the server catalogue before connecting it to WISECP.

Connect and test the module

1. On the module page, click the gear-shaped Settings button in the top action bar directly below the page title; on a narrow screen, reveal this bar with Show Options first. In the Module Settings window, enter the Web Service username and password, then set margin, automatic cost synchronization and the additional-IPv4 order step.
2. Use Test Connection directly below the credential fields. The test can use the typed credentials before saving and is not blocked by the commercial license gate.
3. After the connection succeeds, click Save Settings in the window footer. Blank credential fields on later saves retain the stored values.

Import dedicated models

1. In the top action bar below the page title, click the cloud-download Import from API button. In the window, select Import New Models, Update Cost Prices, or both.
2. Click Start Import in the window footer. Missing models become inactive products with margin-based recurring and setup prices; existing product sale prices remain unchanged during cost refresh.
3. Review the imported count and cost changes before editing the product rows.

Review models and commercial terms

1. For every imported row, verify hardware, location, recurring cost and setup cost; choose a clear public name and product category.
2. Set recurring and setup sale prices in EUR and keep the model inactive until its provisioning test passes.
3. Save the grid. If bulk repricing is required, enter the rate in Profit rate (%) on the right side of the top action bar and click Update Prices; this replaces all imported recurring and setup sale prices from current costs.

Configure requirements and additional IPv4

1. Review the generated operating-system, hostname, root-password and SSH-key requirements and restrict installation choices to supported templates.
2. Enable the additional-IPv4 order step only if customers should purchase that quota; check its recurring and setup price against the provider cost.
3. Confirm the add-on is attached to the intended products so the service tool cannot order beyond the purchased quantity.

Verify with an inactive test product

1. Create a controlled service from one inactive model using a supported operating system and test credentials.
2. Provision it and confirm the Robot server number, hostname and IP are stored; test restart, rescue, reinstall, reverse DNS and bandwidth visibility.
3. Cancel the test through WISECP, verify the dedicated resource and ordered extras are cleaned up as expected, then activate the product.

Maintain catalogue and costs

1. Refresh the catalogue after Hetzner changes model availability, recurring cost or setup cost.
2. Compare new costs with your sale margins before using the bulk rate action; cost synchronization alone is the safe choice when sale prices are curated manually.
3. Periodically retest credentials and a lifecycle operation so Robot access changes are detected before a customer order.

Things to Watch

Privileges

Product Operations (PRODUCTS_OPERATION) is required for settings, import and product pricing. Customer access remains limited to enabled service tools.

Related Screens

• Servers
• Product Groups
• Server Modules