newtataDocumentation
VPS

Configure load balancers

Create a load balancer and manage targets, ports and health checks.

· 4 min read
Newtata management connected · creation with confirmed pricing
Guide contents

Before you begin

  • A real delivered Cloud VPS with management operations enabled.
  • A reachable service on target VPS and required ports allowed by their firewalls.
  • VPS belonging to your account and in the load balancer’s network zone.

Open management#

In VPS, open machine details, then Load balancers. Select a load balancer card; configuration is organised into Target servers, Services and ports, and Settings. Search filters by name, IP, plan or location.

Status refreshes every 30 seconds while the browser tab is visible. After an accepted operation, the portal verifies the new state. Synchronisation errors keep the last data visible and block changes until a successful read.

Create a load balancer#

  1. Click Create a load balancer and enter a name.
  2. Choose an offered plan and algorithm: Round robin distributes new connections in turn; Least connections favours the available target with the fewest active connections.
  3. Configure the first service: protocol, public port and target port. Location matches the opened VPS, which becomes the first target.
  4. Review health-check settings and displayed price excluding VAT. Accept the cost, then confirm creation.
  5. Wait for the load balancer to appear. If the response is uncertain, refresh and check existing resources before creating another.

Choose ports and protocol#

This interface configures HTTP and TCP. Certificate management and TLS termination on the load balancer are not offered. Existing HTTPS services are visible; arrange changes with support.

SettingUse in the portal
HTTPDistribute HTTP requests, for example public port 80 to VPS port 8080.
TCPForward a TCP service. For HTTPS through to the VPS, use 443 to 443, for example; the certificate stays managed on the VPS.
Public portLoad balancer incoming port, from 1 to 65535. It identifies the service to edit.
Target portApplication listening port on target VPS, from 1 to 65535.

Add and monitor targets#

This version uses target public IPs. An Available badge does not replace a full application check.

  1. Choose Target servers, then Add a VPS.
  2. Select an available machine in your account and confirm. The portal rechecks ownership and network zone.
  3. Read availability badges by port. Verifying means the result is not known yet; Unavailable requires checking application, port and firewall.
  4. To remove a target, click Detach, read the warning and confirm removal. The VPS itself is not deleted.

Manage services and health checks#

  1. In Services and ports, click Add a service or Edit beside an existing one.
  2. Existing settings are prefilled. When editing, public port stays fixed; add another service to use a new port.
  3. Health checks use the target port. Set interval, timeout and attempt count; timeout must be shorter than interval.
  4. For HTTP, enter a path starting with /, such as /health. The portal expects a 2xx or 3xx response.
  5. Save, then check target status. Removing a service requires confirmation and interrupts traffic on its public port.

Pricing, trial and deletion#

The form shows the customer price excluding VAT and excess traffic. The server rechecks pricing before creation. The current €10 excl. VAT/month combined trial limit includes VPS and services: exceeding it may block creation even when an offer is listed.

In Settings, deletion requires the exact load balancer name and permanent-operation confirmation. It stops distributed traffic but retains target VPS. Deleting a load balancer is different from cancelling a VPS.

Ready to get started?

Open my VPS ↗