Troubleshooting

Purpose

Use this page to:

• Resolve permission and access-denied errors.
• Explain why a navigation item is missing.
• Fix validation and form errors.
• Investigate failed asynchronous tasks.
• Address slow pages and timeouts.

Prerequisites

• Know your account context (root/home vs tenant) and your assigned roles.
• Permissions follow the category.module.action format, for example compute.vms.create.
• Have the exact error message, the page or action involved, and any related task ID.
• Viewing audit history requires platform.auditlog.read on a root account.

Resolve permission or access-denied errors

1. Open the page or action that failed and note the error.
2. Symptom: you are redirected to the Unauthorized page, or you can view a resource but cannot create or edit it.
3. Confirm you are signed in and in the correct account context.
4. Check your assigned roles and their effective permissions.
5. Verify the exact permission the action requires, for example compute.vms.create to create a VM.
6. Ask an administrator to grant the missing permission to your role.
7. Sign out and back in so the permission change takes effect.
8. Expected result: The action succeeds once the correct permission and context are in place.

Resolve a missing navigation item

1. Review the sidebar for the item you expect.
2. Symptom: an expected item or whole section is not visible.
3. Confirm the item's read permission is granted to your role, for example networking.vnets.read for Networks.
4. Remember that a section with no permitted items is hidden entirely.
5. For Platform items (Global VMs, Clusters, Cluster Monitoring, Syslog, Audit Log, Import VMs), confirm you are on a root account, because the whole section is hidden for non-root.
6. Expected result: The item appears once its permission is granted, and for Platform, on a root account.

Resolve validation or form errors

1. Open the form that will not submit.
2. Symptom: submission is blocked, or fields are highlighted with error messages.
3. Read the message and complete every required field.
4. Match the expected format for names, IP addresses, and ranges.
5. Choose unique names or identifiers where duplicates are rejected.
6. Confirm sufficient quota, and that any dependencies exist first.
7. Expected result: The form submits once all fields are valid.

Resolve async task failures

1. Return to the resource whose change did not take effect.
2. Symptom: a create, power, or backup action does not appear to complete.
3. Open Task Manager from the top bar and find the related task.
4. Check the task status and any error detail.
5. Confirm quota, dependencies, and configuration for the operation.
6. Retry the operation; the platform prevents duplicate tasks from a repeated request.
7. Expected result: The task reaches a completed state and the resource reflects the change.

Resolve performance or timeout issues

1. Return to the page or operation that was slow.
2. Symptom: pages load slowly, operations time out, or a task appears stuck.
3. Check your network connection and watch for the connectivity banner in the page header.
4. Use filters to reduce large result sets.
5. Let a busy cluster's load subside, then retry.
6. Clear the browser cache or try another browser if the UI is unresponsive.
7. Expected result: Pages and operations complete within normal time once connectivity and load are healthy.

Best Practices

• Record the exact error, account context, and any task ID before escalating.
• Reproduce with a second user or context to isolate permission issues.
• Check for recent role or configuration changes.
• Escalate when multiple users are affected or a backend error persists.