Hetzner Cloud Module

Connect WISECP to Hetzner Cloud to turn the provider catalogue into priced cloud products, provision and manage servers automatically, and expose controlled infrastructure tools to customers.

Reaching the Screen

Go to Products → Hosting Server → Hetzner Cloud: {admin}/hetznercloud

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 Virtualization category and then select Hetzner Cloud.
3. Under Connection Details, enter api.hetzner.cloud in Address, root in Username, and the token created in your Hetzner Cloud project in API Token.
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 Cloud menu now appears and {admin}/hetznercloud becomes available.

What the Module Does

Catalogue and product control

The plan grid compares provider hardware and traffic data with the corresponding WISECP product. Each imported row lets you change its public name, included traffic, network, fixed or automatic location, product category, monthly EUR sale price and active status. Import can add missing plans, refresh stored costs and reconcile locations without overwriting an existing sale price. Newly generated plans start inactive so they can be reviewed before publication.

Customer service tools

Depending on the feature switches, a customer can start, stop, restart or hard-power-off a server; reset its generated root password; reinstall an operating system; change hostname; use the web console or rescue mode; and inspect activity. Network tools cover an allow-list firewall, reverse DNS, bandwidth, and purchased floating IPs. Storage tools cover mounted ISOs, volumes, snapshots and automated backups. The overview has real CPU and outbound-bandwidth gauges plus allocated CPU, RAM, disk and traffic values; Hetzner does not supply live guest RAM or disk usage.

Automation and lifecycle

Product generation creates the operating-system requirement and optional user-data and SSH-key inputs, ensures the selected checkout add-ons exist, and rebuilds compatible upgrade paths. Provisioning records the provider server ID against the WISECP service. Suspension, reactivation and cancellation use that relationship; cancellation also removes module-managed billable resources so they are not left orphaned at the provider.

Before You Configure It

1. Use a Hetzner Cloud project that may create and manage the servers, networks, firewalls and optional resources you intend to sell, then create an API token for that project. Treat the token as a secret.
2. Enable the HetznerCloud server module and create an active server record for it. The module stores the token in that record; without the record this page is not routed into the menu.
3. Create and enable an EUR currency in WISECP. Catalogue costs and generated product prices use EUR, and generation/import is blocked when it is missing.
4. Confirm that the module license is available and that the provider account has enough quota and billing capacity for a controlled test server.

Settings and Product Controls

Installation and Operation

Prepare the provider credential

1. In the intended Hetzner Cloud project, create an API token whose access covers the resources enabled in this module.
2. Store the token in a password manager and do not reuse it in browser-side code or customer communications.
3. Keep the project selected for WISECP automation; the catalogue and every provisioned resource will be read from that project.

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, paste the token, set the default margin, stock and cost-sync policy, then select the images, ISOs, order steps and customer features to expose.
2. Use Test Connection directly below the credential field. This test may run before the license is active and can test the typed token without saving it.
3. After the connected indicator appears, click Save Settings in the window footer. The page can then load the live catalogue.

Import and reconcile the catalogue

1. In the top action bar below the page title, click the cloud-download Import from API button. In the window, choose at least one of Import New Plans, Update Cost Prices or Import Locations.
2. Click Start Import in the window footer. Missing plans are created inactive with the default margin; cost-only updates change stored cost, not the current sale price.
3. Review the result. A pinned location that no longer exists is reset to automatic, the operating-system list is synchronized for new plans, and compatible upgrade paths are rebuilt.

Review plans and pricing

1. For each imported row, check hardware, traffic, network and provider cost; then choose the public name, location policy and product category.
2. Enter the monthly EUR sale price and leave the status inactive until a real provisioning test succeeds.
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 the sale prices of all imported plans and generated add-ons.

Configure requirements and paid extras

1. Enable only the backup, volume, snapshot and floating-IP order steps you intend to sell; changing these switches applies the corresponding generated add-ons to module products.
2. Limit available images and ISOs, then review the generated operating-system, hostname, user-data and SSH-key requirements in the product editor.
3. Set add-on prices and quotas against provider costs. Checkout now collects only the selected resources and provisioning can create them with the server.

Verify with an inactive test product

1. Keep one reviewed plan inactive and create a controlled test order/service with a supported image and the smallest optional-resource selection needed for the test.
2. Run provisioning and confirm that a provider server ID, IP and hostname return to WISECP; test the enabled power, console, reinstall and network/storage tools.
3. Cancel the test service and confirm that its server and paid child resources are removed at Hetzner, then activate the product for sale.

Maintain prices, stock and choices

1. Run catalogue import after provider plan, location or cost changes; use cost synchronization when sale prices must remain under manual control.
2. Review out-of-stock visibility, pinned locations, image/ISO availability and add-on quotas before publishing catalogue changes.
3. Periodically provision and cancel a test service so credential scope, lifecycle cleanup and customer tools remain verified.

Things to Watch

Privileges

Product Operations (PRODUCTS_OPERATION) is required to configure the page, import plans and change prices. Customers receive only the service tools enabled in module settings.

Related Screens

• Servers
• Product Groups
• Server Modules