Skip to main content

Appliance IP address configuration

Native appliances running 0.4.20 or later support DHCP and static IPv4 for one Ethernet adapter. Sign in with a normal TestVibe account that has instance-administrator access. Workspace ownership alone does not grant this access.

Hosted TestVibe, Docker Compose and Kubernetes do not expose host-network configuration through this page. IPv6, multiple adapters and custom netplan configurations remain managed by your infrastructure administrator.

Before changing the address​

A new appliance still needs DHCP for initial setup. Open the address shown on the VM console, complete first signup, and then configure a static address.

Keep the VM's physical console available. Reserve an unused address with your network administrator and obtain its prefix length and, if needed, gateway. Check the VM's virtual switch and VLAN assignment before changing the address.

When leaving DHCP, do not rely on DHCP-provided DNS settings. Configure the DNS servers and search domains needed for your network in Network & DNS, and save DNS changes separately from the IP address apply/confirm action.

Review the application and artifact URLs under Administration > Addresses separately. Changing an IP address does not rewrite DNS records, URLs, certificates, reverse-proxy rules or identity provider callback URLs. See HTTPS and reverse proxies.

Accepted static values​

  • IPv4 address: four decimal octets, such as 192.168.10.50, without leading zeros or a /24 suffix. Use an address assigned for your network, outside loopback, link-local, multicast and other non-unicast ranges.
  • Prefix length: a number from 1 to 30. Enter 24 rather than a dotted subnet mask. The address must be a host address, not the subnet or broadcast address for that prefix.
  • Default gateway (optional): a different valid host address in the same subnet, such as 192.168.10.1 for the example above. Leave it blank only if the appliance does not need a default route to other subnets. External DNS, identity, email and model providers may need that route.

The appliance checks address format and subnet rules; it does not reserve an address or establish that no other device is using it. These addresses are examples; use your own network's assigned values. DHCP obtains the address automatically and does not require the static fields.

Apply and confirm​

  1. Open Settings > Administration > Network & DNS > IP address configuration.
  2. Select DHCP (automatic) or Static IPv4. For static addressing, enter the address, prefix and optional gateway.
  3. Choose Apply network change and accept the confirmation prompt. Your connection may be interrupted.
  4. Reconnect at the new application address. For DHCP, find the assigned address on the VM console. Sign in again if required and reopen Network & DNS.
  5. Choose Confirm connection and keep settings within the displayed two-minute confirmation window. Confirmation is available only after the appliance reports that the change has applied.
  6. Check the application and existing artifact links. Review any dependent DNS, public URL, certificate or sign-in configuration that also needs updating.

Use the same apply/confirm sequence when returning from static addressing to DHCP.

Cancel or recover connectivity​

Discard changes clears an unapplied form edit. Cancelling the browser's apply prompt also leaves the existing configuration in place. After submitting a change, Cancel and restore previous settings requests rollback.

If you do not confirm in time, the appliance restores its previous address configuration. Apply failures, interrupted apply operations and a reboot before confirmation also restore the previous configuration. Rollback takes additional time after the watchdog detects the timeout or the appliance starts again; allow it to finish before retrying. Reconnect at the previous address and refresh the page to review the result.

If the application cannot be reached, use Restore DHCP networking on the physical VM console and confirm the recovery action there. This restores automatic addressing and retains existing DNS overrides. A DHCP server must be available on the selected network for the appliance to receive an address.

If configuration is unavailable because the host has multiple adapters or custom network configuration, follow the displayed reason and consult your infrastructure administrator. See network troubleshooting.

Reboots and OS-disk upgrades​

Confirmed settings are stored on the DATA disk and restored during boot. An unconfirmed change is rolled back rather than retained after a reboot.

For an upgrade, shut down the VM and replace only the OS disk, retaining the existing DATA disk and installation configuration. Do not replace it with the empty DATA disk included for new installations. Keep the old disks and a matched backup for recovery. If the saved Ethernet adapter is unavailable after a hardware change, the appliance falls back to DHCP and the addressing needs review.

Follow the upgrade procedure, backup guide and 0.4.20 release notes. The release notes state the validation scope; a successful basic boot check does not establish live DHCP/static transition or customer hypervisor acceptance.