Common Configuration Service problems and how to resolve them. For installer-side issues see Troubleshooting the Installer.
Cannot Sign In
Symptom: clicking Sign in with Single Sign-On loops back to the sign-in screen, or the identity provider shows an error.
Resolve:
- Wrong credentials: reset your password through your identity provider, then retry.
- A recent change in Platform > Authentication: the page validates the authority before it applies a change, and an authentication or certificate change reverts automatically if you do not confirm it. If the change locked you out, wait until the pending window reverts it, or sign in from another device and click Discard. If that does not help, contact Vizrt support, who can reset the settings with
vamctl. - Other causes, such as a missing
vam-adminrole, a redirect URI mismatch or clock skew: see Identity Provider Setup > Troubleshooting Sign-In.
Configuration Service Is Unreachable
Symptom: browsing to https://<vam-host>:30443/config shows a connection error, certificate error, or 502 / 503.
Resolve:
- DNS and network: confirm that the hostname resolves and that the IP is reachable from your client.
- An expired TLS certificate: a browser certificate warning that was not there yesterday suggests an expired or replaced certificate. Use
vamctlon the installer host to reissue it. - A service is down: run Health > Run Checks, or use
vamctlon the installer host if the UI is unreachable. If several services are down, the cluster itself may be unhealthy. See the Cluster view, or the Manage Existing Cluster workflow of the installer, which shows how many nodes are ready. - The ingress is down: if the cluster is healthy but the Configuration Service URL is unreachable, the ingress controller pod may have crashed. Contact Vizrt support. Restarting the ingress is risky, and Vizrt support has tooling for it.
Package Install Fails
Symptom: installing a package reports an error part-way through.
Resolve:
- Expand the failed step to read the diagnosis. Most failures are configuration-related (a required field with an invalid value, credentials that don't work).
- Fix the configuration on the package's install form and retry.
- If the error mentions missing dependencies, install the dependent packages first.
- If the error mentions the registry or an image pull, the cluster cannot fetch the package's container images. Confirm the cluster has network access to the configured registry. Check the registry settings under Platform > Container registry (Harbor) and click Test connection.
Package Shows Degraded or Unhealthy
Symptom: a package's status indicator is yellow or red on the Packages list.
Resolve:
- Click the package to open its detail view.
- Read the Overview status and the Diagnostics tab. They show the specific failing checks.
- Read the Logs tab (and the Pods tab) for relevant error messages.
- Common causes:
- The package depends on another that is down.
- The package's configuration references credentials that have rotated.
- A backing store (database, object store) is unhealthy.
If you cannot diagnose from the package logs alone, run Health > Run Checks for a coordinated view.
Configuration Save Fails with a Validation Error
Symptom: editing a package's configuration and clicking save shows a validation error.
Resolve: the package's configuration schema rejected a value. The error message points to the specific field. Fix the value and retry. If the message is unclear, the package's documentation (visible on its detail view) explains valid values.
Backup to Network Mount / External S3 Fails
Symptom: a backup whose target is Network mount (PVC) or External S3 / MinIO fails (the Download archive (small backups only) target is local and rarely fails).
Resolve:
- Network mount (PVC): confirm the SMB / NFS share is reachable from the cluster nodes (not just your workstation), the PV/PVC for the share exists (create it from the Backup screen if not) and the credentials have read+write. For SMB, the SMB CSI driver must be installed.
- External S3 / MinIO: confirm the endpoint URL is reachable from the cluster, the bucket exists and the access key has
s3:PutObject,s3:GetObjectands3:ListBucketon the bucket. - Verify on a completed backup checks only that its archive still exists on the target. It cannot check a network-mount backup.
Storage License Shows Expired / Invalid
Symptom: Platform > Storage license (AIStor) reports the AIStor license is expired, invalid, or has the wrong feature set (enterprise features such as replication are gated on it).
Resolve:
- Ask your Vizrt representative for a renewed or corrected license.
- Open Platform > Storage license (AIStor), click Update license, paste the license into Paste the AIStor license blob and click Apply.
- Confirm the entitlement (for example, ENTERPRISE) in the section header.
Getting Support
When opening a support case, include:
- The VAM version shown on the Vizrt Asset Management package card.
- A current Health > Run Checks result.
- The installer log files from the installer host, if relevant, see Troubleshooting the Installer > Collecting Logs for Support.
- A description of what you were doing when the issue occurred and what you've already tried.