Skip to main content

Troubleshooting and recovery

Use the application login​

  • Open the application address shown on the VM console. First access presents Welcome to TestVibe; choose Create an account.
  • The VM console is for recovery and service diagnostics. You do not need an operating-system login to set up TestVibe.

No network address​

  • Check the VM network adapter, virtual switch, DHCP and VLAN assignment. Confirm the appliance has both disks attached.
  • Use the recovery menu’s network information to inspect assigned addresses.

Application does not open​

  • Allow startup and database migrations to finish. Check that the host can reach the appliance address and that your firewall permits the application port.
  • For Compose, inspect docker compose ps and docker compose logs migrate web. For Kubernetes, inspect pod readiness and the migration job.

Host recovery​

  • There is no shared default password. If you have not claimed a fresh installation, create an account in the normal application.
  • On an appliance, use the physical VM console recovery menu to list users, grant administrator access, reset an administrator password, repair a public address, or restart an allowlisted service.
  • With Compose, use docker compose run --rm --no-deps --entrypoint dotnet web /opt/testvibe/recovery/testvibe-recovery.dll users. Replace users with grant USER_ID to appoint an existing active account.
  • To reset an administrator, run the same command with reset USER_ID in an interactive terminal. Sign in with the displayed temporary password and choose a new password. Do not capture it in logs.
  • With Kubernetes, temporarily enable recovery.enabled using your existing chart values and secrets. Execute the same dotnet recovery command inside the recovery pod using kubectl exec -it, then disable recovery.enabled.
  • Recovery still requires the database and its configuration. Restore missing mounts or database connectivity before attempting account recovery.
docker compose run --rm --no-deps --entrypoint dotnet web \
  /opt/testvibe/recovery/testvibe-recovery.dll users

# Replace USER_ID with an existing active user from the list.
docker compose run --rm --no-deps --entrypoint dotnet web \
  /opt/testvibe/recovery/testvibe-recovery.dll grant USER_ID

# Run interactively; a temporary password appears only in your terminal.
docker compose run --rm --no-deps --entrypoint dotnet web \
  /opt/testvibe/recovery/testvibe-recovery.dll reset USER_ID

Missing data disk​

  • Attach both disks for a new appliance. For an upgrade, attach the new OS disk and your retained data disk.
  • Do not attach two disks labeled testvibe-data. Preserve the disk containing your installation, and remove the new empty data disk from the VM configuration.

VirtualBox will not boot​

  • Enable EFI in the VM settings before booting the OVA. Check disk attachment and the boot order.

Hyper-V will not boot​

  • Use a Generation 2 VM. Select the Microsoft UEFI Certificate Authority Secure Boot template for Linux, or disable Secure Boot if necessary.

Artifacts or traces do not load​

  • Check Administration → Addresses. The Artifact URL must be reachable by the user’s browser, not only by the server.
  • Confirm the artifact service and its proxy are reachable, and that the signing key has not changed independently of stored configuration.

Verification or password reset email is missing​

  • First-administrator signup does not need email. Subsequent verification and password-reset messages require a working email provider.
  • Check Email configuration and Send test email. Check the recipient, relay logs and junk folder.

Email delivery fails​

  • Confirm the relay hostname and port, sender address, authentication and TLS requirements. Use a trusted CA certificate for a private relay CA.
  • Save changes before sending a test email. If the configuration is host-managed, update the deployment setting.

Installation is read-only​

  • Open Administration → License. Apply a valid license for this installation or update the host-managed license.
  • A new installation normally has 14 days of grace. A restart does not renew it.

A workload was interrupted​

  • Check recent runs, generations, runner leases and audit entries under Administration → Operations and activity.
  • Request cancellation for a stuck workload and inspect the corresponding service logs before retrying.

Withdrawn appliance versions​

  • Appliance versions 0.4.0 and 0.4.1 shipped shared generated secrets. Do not use those images for a new installation.
  • For an affected existing installation, preserve a backup and contact support about rotating credentials and migrating data. Replacing only the OS disk does not rotate keys on the retained data disk.

Container images do not pull​

  • Authenticate to testvibe.azurecr.io with your subscription registry credentials. Confirm the requested version exists in the portal.
  • Take the new release’s Compose file before pulling: its image tags are pinned. A pull alone does not advance the version.

Share a useful diagnostic​

  • Record the installed version, deployment type, failed action and time, and the displayed error. Include relevant service or migration logs after removing secrets.
  • Never include account passwords, registry credentials, private keys or unredacted connection strings.