Error Codes¶
Every customer-facing error carries a stable public code PC-<PREFIX>-<NNN> and an opaque support id (PC-YYYYMMDD-XXXXXX). Unknown errors map to PC-SYS-000 and never include a stack trace. A code is stable: once published its meaning never changes.
Codes are the single source of truth defined in the diagnostics error catalog. Use php artisan pterocloud:error PC-XXX-### to print one, or pterocloud:error:id <support-id> to resolve a support id.
How to read this reference¶
- Code — the stable public identifier shown to the customer.
- Title / Meaning — a plain-language summary. Customer text is intentionally non-technical.
- Sev —
critical,errororwarning. - Causes — the common conditions that produce it.
- Fix — the recommended checks or operator action.
- Retry — whether re-running the operation can succeed without a change.
Infrastructure is never collateral: a licensing or control-plane error never deletes or powers off customer VMs, disks, backups or IPs.
Index¶
- Installation & System — 11 codes
- Licensing — 20 codes
- Providers — 24 codes
- Hypervisors & Native KVM — 12 codes
- Agent — 4 codes
- Provisioning — 13 codes
- Scheduler & Queue — 23 codes
- Networking — 10 codes
- IP Address Management — 4 codes
- Storage — 10 codes
- Images — 7 codes
- Console & SSH — 9 codes
- Backups & Snapshots — 9 codes
- Migration & Evacuation — 30 codes
- High Availability — 5 codes
- Security — 13 codes
- Tenancy & Add-ons — 8 codes
- Tasks — 16 codes
- Database — 4 codes
- Queue — 7 codes
- Internal — 4 codes
Installation & System¶
| Code | Title | Sev | Meaning | Common causes | Fix | Retry |
|---|---|---|---|---|---|---|
PC-SYS-001 |
Blueprint version mismatch | ERROR | The installed Blueprint version is incompatible. Please contact support. — The Blueprint package version does not match the required version. | Outdated Blueprint; Manual modification | Reinstall the matching Blueprint version | YES |
PC-SYS-002 |
Cache path not writable | ERROR | A cache directory is not writable. Please contact support. — The cache directory is not writable. | Incorrect permissions | Check the cache directory permissions | CONDITIONAL |
PC-SYS-003 |
Clock drift detected | WARNING | The server clock appears incorrect, which can affect sessions and licensing. — System clock differs significantly from the expected time. | NTP not running; Timezone misconfiguration; VM clock drift | Synchronise the system clock (NTP) | YES |
PC-SYS-009 |
Frontend/backend version mismatch | WARNING | The panel assets are out of date. Please contact support. — The compiled frontend assets do not match the backend version. | Assets not rebuilt after upgrade | Rebuild the frontend assets | YES |
PC-SYS-010 |
Installation credential missing | ERROR | The cloud control plane is missing a required credential. Please contact support. — A required installation credential is absent. | Environment variable removed; Secret store unavailable | Verify the environment configuration | CONDITIONAL |
PC-SYS-011 |
Installation is incomplete | ERROR | The cloud control plane is not fully installed. Please contact support. — One or more installation steps did not complete. | Installer interrupted; Missing migration; Incomplete deployment | Run the installer verification; Check pending migrations | YES |
PC-SYS-030 |
First-VPS setup incomplete | ERROR | The cloud control plane is not fully configured. Please contact support. — One or more core setup dependencies are missing. | No provider; No hypervisor; No image; No plan; No IP pool | Run pterocloud:setup:verify | YES |
PC-SYS-031 |
Storage path not writable | CRITICAL | The cloud control plane cannot write to its storage. Please contact support. — A required storage path is not writable by the panel user. | Incorrect permissions; Disk full; Read-only mount | Check directory permissions and free space | CONDITIONAL |
PC-UPD-001 |
Compatibility mismatch | WARNING | A component version is incompatible. Please contact support. — A component does not match the supported compatibility matrix. | Outdated component | Upgrade to a supported version | NO |
PC-UPD-003 |
PHP version unsupported | ERROR | The PHP version is not supported. Please contact support. — The running PHP version is outside the supported range. | Outdated PHP | Upgrade PHP | NO |
PC-UPD-004 |
Pterodactyl version unsupported | ERROR | The Pterodactyl version is not supported. Please contact support. — The panel core version is outside the supported range. | Outdated panel | Upgrade Pterodactyl | NO |
Licensing¶
| Code | Title | Sev | Meaning | Common causes | Fix | Retry |
|---|---|---|---|---|---|---|
PC-LIC-001 |
License cache tamper detected | CRITICAL | The license store appears to have been modified. Please contact support. — The persisted lease failed an integrity re-check. | Manual edit of the lease file; Rollback of the store | Re-activate the license | NO |
PC-LIC-002 |
License clock anomaly | WARNING | The server clock moved unexpectedly, which affects licensing. — A backwards or excessive clock jump was detected. | Clock rollback; NTP correction | Synchronise the system clock | YES |
PC-LIC-003 |
License expired | ERROR | The license has expired. Existing servers keep running. Please contact support. — The signed lease reports an expired subscription. | Subscription lapsed | Renew the license | CONDITIONAL |
PC-LIC-004 |
License expiring soon | WARNING | The license is expiring soon. Please renew to avoid interruption. — The signed lease is within the expiring window. | Subscription nearing expiry | Renew the license | NO |
PC-LIC-005 |
License installation limit reached | ERROR | The license installation limit has been reached. Please contact support. — The license permits no more installations. | Too many clones | Deactivate an unused installation | CONDITIONAL |
PC-LIC-006 |
License bound to another installation | CRITICAL | This license is bound to a different installation. Please contact support. — The lease installation id does not match this installation. | Cloned installation; Copied storage directory | Activate a license for this installation | CONDITIONAL |
PC-LIC-007 |
License integrity check failed | CRITICAL | A licensing integrity check failed. Please contact support. — The signed release manifest check failed for critical license files. | Modified license files; Missing manifest | Reinstall the extension from the official release | NO |
PC-LIC-008 |
License lease expired | ERROR | The license lease has expired and could not be refreshed. — The cached lease window elapsed and the server was unreachable. | Licensing server unreachable; Network partition | Check connectivity to the licensing server; Refresh the license | YES |
PC-LIC-009 |
License not configured | WARNING | Licensing is not configured for this installation. — No product is configured; enforcement is disabled. | KRAPPLE_PRODUCT unset | Configure licensing if required | NO |
PC-LIC-010 |
License product mismatch | ERROR | The license is for a different product. Please contact support. — The lease product claim does not match pterocloud. | Wrong product key | Activate a PteroCloud license | CONDITIONAL |
PC-LIC-011 |
License required | ERROR | A valid license is required to manage cloud resources. Existing servers keep running. — No usable signed lease is present; the control layer is locked. | License not activated; License key missing | Activate or refresh the license | YES |
PC-LIC-012 |
License restricted | ERROR | The requested action is not permitted by the current license. — The license action was denied. | Feature not entitled; Limit reached | Review the license entitlements | CONDITIONAL |
PC-LIC-013 |
License revoked | CRITICAL | The license has been revoked. Please contact support. — The licensing server reports the license as revoked. | License revoked | Contact support | NO |
PC-LIC-014 |
Licensing server unavailable | WARNING | The licensing server could not be reached. A valid lease keeps the product running. — The licensing server is unreachable; the cached lease is still valid. | Network outage; Firewall | Check connectivity to the licensing server | YES |
PC-LIC-015 |
License signature invalid | CRITICAL | The license could not be verified. Please contact support. — The signed lease signature failed verification. | Tampered lease; Wrong public key; Corrupted store | Re-activate the license; Check the trusted key configuration | CONDITIONAL |
PC-LIC-016 |
Licensing subsystem missing | CRITICAL | The licensing subsystem is unavailable. Please contact support. — The licensing services are not registered in the container. | Incomplete install; Removed package | Reinstall the extension | NO |
PC-LIC-017 |
License suspended | ERROR | The license is suspended. Please contact support. — The licensing server reports the subscription as suspended. | Billing issue | Contact support | NO |
PC-LIC-018 |
License not verified | ERROR | The license has not been verified yet. — No lease has been verified for this installation. | Fresh install | Activate the license | YES |
PC-LIC-019 |
License does not cover this version | ERROR | The current version is not covered by the license. Please contact support. — The installed version is not included in the license entitlement. | Version newer than license | Renew or upgrade the license | NO |
PC-LIC-020 |
PteroCloud license required | ERROR | A PteroCloud license is required. Existing servers keep running. — The request was blocked by hard license enforcement. | License locked; Lease expired | Refresh the license | YES |
Providers¶
| Code | Title | Sev | Meaning | Common causes | Fix | Retry |
|---|---|---|---|---|---|---|
PC-PROV-003 |
Provider capability missing | ERROR | The provider is missing a required capability. Please contact support. — A required provider capability is not advertised. | Feature unavailable | Choose a capable provider | NO |
PC-PROV-004 |
Provider resource conflict | WARNING | A conflicting operation is already in progress. Please wait and retry. — The provider reported a lock or conflicting task. | Concurrent operation | Wait for the running task to finish | YES |
PC-PROV-005 |
Provider disabled | WARNING | This provider connection is disabled. — The provider connection is disabled and will not be used. | Admin disabled it | Re-enable the provider if intended | NO |
PC-PROV-006 |
Provider error | ERROR | The infrastructure provider returned an error. Please contact support. — An unclassified provider API error occurred. | Provider fault | Review the provider diagnostics | CONDITIONAL |
PC-PROV-007 |
Provider has dependencies | WARNING | The provider cannot be removed while it has dependent resources. — The provider connection has dependent resources. | Mapped nodes or instances | Remove dependencies first | NO |
PC-PROV-008 |
Provider configuration invalid | ERROR | The provider configuration is invalid. Please contact support. — The provider connection configuration failed validation. | Malformed endpoint; Bad port | Correct the provider configuration | NO |
PC-PROV-009 |
Provider node not imported | ERROR | A provider node has not been imported. Please contact support. — The provider node is not imported into the panel. | New node added | Import the node | YES |
PC-PROV-010 |
Provider mapping missing | ERROR | A required provider mapping is missing. Please contact support. — No provider mapping exists for the requested resource. | Sync not run; Resource not imported | Run a provider sync; Import the resource | YES |
PC-PROV-011 |
Provider operation unsupported | WARNING | This operation is not supported by the provider. Please contact support. — The provider driver does not implement the operation. | Older provider | Use a supported path | NO |
PC-PROV-012 |
Provider permission denied | ERROR | The provider denied a required permission. Please contact support. — The provider token lacks a required privilege. | Restricted API token | Grant the required provider permissions | CONDITIONAL |
PC-PROV-013 |
Provider is read-only | WARNING | This provider is configured read-only. — Mutating provider operations are blocked by the read-only flag. | Read-only enabled | Disable read-only to allow changes | NO |
PC-PROV-014 |
Provider resource not found | ERROR | The expected infrastructure resource was not found. Please contact support. — The provider reported the resource as absent. | Deleted outside the panel; Renamed | Reconcile the resource | CONDITIONAL |
PC-PROV-015 |
Provider sync stale | WARNING | The provider data is out of date. Please contact support. — The last successful provider sync is older than the stale window. | Sync job failing; Provider slow | Run a provider sync; Check the sync job | YES |
PC-PROV-016 |
Provider task timed out | WARNING | An infrastructure task took too long. Please try again or contact support. — A provider task did not reach a terminal state within budget. | Slow storage; Large clone | Retry the task | YES |
PC-PROV-017 |
Provider request timed out | WARNING | The provider did not respond in time. Please try again. — A provider API call exceeded its timeout. | Slow provider; Network latency | Retry the operation | YES |
PC-PROV-018 |
Provider unavailable | ERROR | The infrastructure provider is currently unavailable. Please try again later. — The provider API is unreachable. | Provider outage; Network issue; Maintenance | Check provider status; Retry the connection test | YES |
PC-PROV-019 |
Provider unsupported | ERROR | This provider is not supported. Please contact support. — The provider type is not supported by this version. | Unknown provider type | Use a supported provider | NO |
PC-PROV-023 |
TLS fingerprint mismatch | CRITICAL | The provider TLS fingerprint does not match the pinned value. Please contact support. — The pinned certificate fingerprint no longer matches. | Certificate rotation; Man-in-the-middle | Verify the new fingerprint out of band | NO |
PC-PROV-024 |
TLS certificate untrusted | ERROR | The provider TLS certificate could not be trusted. Please contact support. — The provider presented an untrusted certificate. | Self-signed certificate; Expired certificate; Wrong CA | Install the correct CA certificate or pin the fingerprint | CONDITIONAL |
PC-PROV-025 |
TLS validation failed | ERROR | A TLS connection could not be validated. Please contact support. — TLS validation failed while connecting to the provider. | Certificate problem; Protocol mismatch | Fix the certificate chain — never disable verification | CONDITIONAL |
PC-PVE-003 |
Provider authentication failed | ERROR | The provider rejected our credentials. Please contact support. — The provider API rejected the configured token or user. | Rotated token; Wrong credentials | Re-enter the provider credential; Verify the API token permissions | CONDITIONAL |
PC-PVE-004 |
Proxmox API error | ERROR | The Proxmox API returned an error. Please contact support. — The Proxmox API returned a non-success status. | Provider fault; Invalid parameters | Review the Proxmox task log | CONDITIONAL |
PC-PVE-005 |
Proxmox task failed | ERROR | A Proxmox task failed. Please contact support. — The Proxmox UPID task reached a failed terminal state. | Storage error; Config conflict | Review the Proxmox task output | CONDITIONAL |
PC-PVE-006 |
Proxmox-only operation | WARNING | This operation is only available for Proxmox providers. — The operation requires a Proxmox provider driver. | Native provider selected | Use a Proxmox provider | NO |
Hypervisors & Native KVM¶
| Code | Title | Sev | Meaning | Common causes | Fix | Retry |
|---|---|---|---|---|---|---|
PC-KVM-001 |
Compute inventory stale | WARNING | The host compute inventory is out of date. — The compute inventory sync timestamp is older than the stale window. | Agent not reporting | Refresh the agent capabilities | YES |
PC-KVM-002 |
Compute topology not synced | WARNING | The host compute topology has not been synced. — No compute topology report is available for the host. | Agent has not reported topology | Refresh the agent capabilities | YES |
PC-KVM-003 |
CPU topology not synced | WARNING | The host CPU topology has not been synced. — No CPU topology report is available for the host. | Agent has not reported topology | Refresh the agent capabilities | YES |
PC-KVM-004 |
CPU virtualisation unavailable | ERROR | CPU virtualisation is not available on this host. Please contact support. — The host CPU does not advertise vmx/svm. | Bare-metal without VT-x/AMD-V | Use a host with CPU virtualisation | NO |
PC-KVM-005 |
Configuration drift detected | WARNING | Configuration drift was detected on a host. Please contact support. — The actual provider state differs from the panel record. | Out-of-band change | Reconcile the resource | YES |
PC-KVM-006 |
Hypervisor in maintenance | INFO | This host is in maintenance. — The hypervisor is in maintenance mode. | Planned maintenance | No action required | NO |
PC-KVM-007 |
Hypervisor overcommitted | WARNING | The host is over-committed. Performance may be affected. — Allocated resources exceed the configured overcommit ratios. | Too many allocations | Add capacity or migrate instances | NO |
PC-KVM-008 |
IOMMU disabled | WARNING | IOMMU is disabled, so device passthrough is unavailable. — The IOMMU is disabled on the host. | BIOS setting; Kernel parameter missing | Enable IOMMU if passthrough is required | CONDITIONAL |
PC-KVM-009 |
KVM unavailable | ERROR | Hardware virtualisation is unavailable on this host. Please contact support. — The /dev/kvm device is not available to the agent. | Nested virtualisation disabled; KVM module missing; No permissions | Enable KVM on the host | CONDITIONAL |
PC-KVM-010 |
libvirt unavailable | ERROR | The virtualisation service is unavailable on this host. Please contact support. — libvirt is not running or unreachable. | libvirtd stopped; Socket permissions | Start and enable libvirtd | CONDITIONAL |
PC-KVM-011 |
Nested virtualisation disabled | WARNING | Nested virtualisation is disabled on this host. — The nested virtualisation capability is unavailable or disabled. | Kernel module option; CPU feature | Enable nested virtualisation if required | CONDITIONAL |
PC-KVM-012 |
QEMU unavailable | ERROR | The virtual machine engine is unavailable on this host. Please contact support. — QEMU is not installed or not usable. | QEMU missing | Install the supported QEMU version | CONDITIONAL |
Agent¶
| Code | Title | Sev | Meaning | Common causes | Fix | Retry |
|---|---|---|---|---|---|---|
PC-AGT-001 |
Agent heartbeat stale | WARNING | The host agent heartbeat is delayed. Please contact support. — The last agent heartbeat is older than the degraded window. | Agent overloaded; Network jitter | Check the agent service | YES |
PC-AGT-002 |
Agent offline | ERROR | The host agent is not responding. Existing instances keep running. Please contact support. — The hypervisor agent has not heartbeated within the offline window. | Agent stopped; Host unreachable; Firewall | Check the agent service and network path | YES |
PC-AGT-003 |
Agent protocol mismatch | ERROR | The host agent protocol version is incompatible. Please contact support. — The agent protocol version is outside the supported range. | Outdated agent; Panel upgraded | Upgrade the agent to a supported version | NO |
PC-AGT-004 |
Agent version mismatch | WARNING | The host agent version is out of date. Please contact support. — The agent version differs from the recommended version. | Outdated agent | Upgrade the agent | NO |
Provisioning¶
| Code | Title | Sev | Meaning | Common causes | Fix | Retry |
|---|---|---|---|---|---|---|
PC-PROV-001 |
Image mapping missing | ERROR | A required image mapping is missing. Please contact support. — No provider mapping exists for the image. | Mapping not created | Create the image mapping | YES |
PC-PROV-002 |
Password reset unsupported | WARNING | The password cannot be changed because the guest agent is not running. — The QEMU guest agent did not respond so the password cannot be applied. | Guest agent offline; Instance stopped | Start the instance and the guest agent | YES |
PC-PROV-020 |
Provisioning failed | ERROR | Provisioning a server failed. Please contact support. — The provisioning pipeline failed. | Provider error; Resource exhaustion | Review the task timeline | CONDITIONAL |
PC-PROV-021 |
Provisioning rollback failed | CRITICAL | A failed provisioning could not be fully rolled back. Please contact support. — Provisioning rollback left residual resources. | Provider error during cleanup | Reconcile the orphaned resources | CONDITIONAL |
PC-PROV-022 |
Provisioning step timed out | ERROR | Provisioning a server timed out. Please contact support. — A provisioning pipeline step exceeded its budget. | Slow provider; Storage latency | Retry provisioning; Review the task timeline | YES |
PC-PROV-026 |
Custom user data disabled | WARNING | Custom startup scripts are disabled for this plan. — The plan policy forbids custom startup scripts. | Plan policy DISABLED | Choose an allowed preset | NO |
PC-PROV-027 |
Startup script empty | WARNING | The startup script is empty. — The script body is empty. | Empty content | Provide script content | NO |
PC-PROV-028 |
Startup script forbidden | WARNING | The selected startup script does not belong to you. — The script is owned by another tenant. | Foreign script | Choose your own script | NO |
PC-PROV-029 |
Preset startup script required | WARNING | This plan only allows preset startup scripts. — The plan policy is PRESET_ONLY and the script is not an admin template. | Plan policy PRESET_ONLY | Choose an admin preset | NO |
PC-PROV-030 |
Startup script too large | WARNING | The startup script exceeds the 64 KB limit. — The script body is larger than the 64 KB cap. | Oversized content | Shorten the script | NO |
PC-PROV-031 |
Startup script type invalid | WARNING | The startup script type is not supported. — The script type is outside the supported set. | Unknown type | Choose a supported type | NO |
PC-PROV-032 |
Startup variable invalid | WARNING | A startup variable value is invalid. — A variable value failed the safe-substitution allow-list. | Unsafe characters | Use a plain scalar value | NO |
PC-PROV-033 |
Startup variable unknown | WARNING | The startup script was given an undeclared variable. — A variable was supplied that the script did not declare. | Undeclared variable | Declare the variable on the script | NO |
Scheduler & Queue¶
| Code | Title | Sev | Meaning | Common causes | Fix | Retry |
|---|---|---|---|---|---|---|
PC-SCH-001 |
Compute pool in use | WARNING | The compute pool is still in use. — Active allocations reference the pool. | Active allocations | Release allocations first | CONDITIONAL |
PC-SCH-002 |
Compute pool reserved for system | WARNING | The compute pool is reserved for system use. — The pool is flagged reserved for the system. | Reserved pool | Choose another pool | NO |
PC-SCH-003 |
Dedicated CPU not available | WARNING | The requested dedicated CPU capacity is not available right now. — The CPU allocator cannot satisfy the dedicated allocation. | Pool exhausted; Pool disabled; Reserved | Retry later or choose another plan | YES |
PC-SCH-004 |
Device already assigned | WARNING | The requested device is already assigned. — The PCI device is not AVAILABLE. | Assigned elsewhere | Choose another device | CONDITIONAL |
PC-SCH-005 |
Device is host-critical | WARNING | The device is host-critical and cannot be assigned. — The device is marked host-critical. | Boot/management device | Choose another device | NO |
PC-SCH-006 |
Device not allowlisted | WARNING | The device is not allowlisted for passthrough. — The PCI device is not allowlisted. | Not approved | Allowlist the device | NO |
PC-SCH-007 |
Device not assignable | WARNING | The device cannot be assigned. — The PCI device is not assignable. | IOMMU grouping | Review IOMMU grouping | NO |
PC-SCH-008 |
Invalid CPU allocation request | WARNING | The CPU allocation request is invalid. — The CPU allocation request failed validation. | Zero cores; Pool mismatch | Correct the request | NO |
PC-SCH-009 |
No assignable device | WARNING | No passthrough device is currently available. — No allowlisted, available PCI device matches the request. | All devices assigned | Free a device or adjust the request | CONDITIONAL |
PC-SCH-010 |
No assignable GPU | WARNING | No GPU is currently available for passthrough. — No allowlisted, available GPU exists on the candidate nodes. | All GPUs assigned; Not allowlisted | Free a GPU or allowlist one | CONDITIONAL |
PC-SCH-011 |
No device pool capacity | WARNING | The device pool has no capacity. — No device in the pool is available. | Pool exhausted | Add devices or wait | YES |
PC-SCH-012 |
No hugepage capacity | WARNING | The host cannot satisfy the requested hugepage allocation. — The hugepage allocator cannot satisfy the request. | Reserved pages; Fragmentation; Wrong NUMA node | Reserve more hugepages or relax the policy | CONDITIONAL |
PC-SCH-013 |
No nested-capable node | WARNING | No host currently supports the requested nested virtualisation. — No candidate hypervisor advertises a schedulable nested capability. | All nodes lack nesting | Enable nesting on a node | CONDITIONAL |
PC-SCH-014 |
No single NUMA node available | WARNING | The requested allocation cannot fit on a single NUMA node. — No single NUMA node satisfies the strict allocation. | NUMA fragmentation | Relax the NUMA policy | YES |
PC-SCH-015 |
No single NUMA node has enough free cores | WARNING | The requested CPU count cannot fit on a single NUMA node. — No single NUMA node has enough free cores for a strict allocation. | NUMA fragmentation; Strict policy | Relax the NUMA policy or free cores | YES |
PC-SCH-016 |
Schedule action invalid | WARNING | The scheduled action is not supported. — The schedule requested an action outside the semantic allow-list. | Unknown action | Choose a supported action | NO |
PC-SCH-017 |
Schedule expression invalid | WARNING | The schedule expression is invalid. — The cron expression failed validation. | Malformed cron | Correct the schedule expression | NO |
PC-SCH-018 |
Schedule weekdays required | WARNING | A weekly schedule needs at least one weekday. — No weekdays were selected for a weekly schedule. | Missing weekdays | Select at least one weekday | NO |
PC-SCH-019 |
Schedule execution locked | INFO | The schedule was skipped because another run was in progress. — The distributed schedule lock was contended. | Concurrent run | Wait for the next occurrence | YES |
PC-SCH-020 |
Scheduled task failed | WARNING | A scheduled task failed. Please contact support. — One of the scheduled semantic actions failed. | Provider error; Instance locked | Review the schedule run | YES |
PC-SCH-021 |
Schedule timezone invalid | WARNING | The schedule timezone is invalid. — The timezone is not a recognized identifier. | Unknown timezone | Choose a valid timezone | NO |
PC-SCH-022 |
Schedule time invalid | WARNING | The schedule time is invalid. — The run-at time is not a valid HH:MM value. | Malformed time | Correct the run time | NO |
PC-SCH-023 |
Shared CPU capacity exhausted | WARNING | Shared CPU capacity is exhausted on the candidate hosts. — No candidate host has shared CPU headroom. | Overcommit reached | Add capacity or reduce allocations | YES |
Networking¶
| Code | Title | Sev | Meaning | Common causes | Fix | Retry |
|---|---|---|---|---|---|---|
PC-NET-001 |
Bandwidth speed limit reached | WARNING | The bandwidth speed limit for this server has been reached. — The provider-side rate limit is throttling the instance. | Speed limit configured | Adjust the speed add-on | YES |
PC-NET-002 |
Bandwidth quota exceeded | WARNING | The monthly transfer quota has been exceeded. — The instance exceeded its monthly bandwidth allowance. | Quota reached | Wait for the next cycle or adjust the quota | YES |
PC-NET-003 |
Cannot remove primary IP | WARNING | The primary IP address cannot be removed. — Removing the primary address is not permitted. | Primary address | Promote another address first | NO |
PC-NET-004 |
Firewall rule limit reached | WARNING | The firewall rule limit has been reached. — The maximum number of firewall rules is reached. | Too many rules | Remove unused rules | NO |
PC-NET-005 |
Network mapping missing | ERROR | A required network mapping is missing. Please contact support. — No network provider mapping exists for the bridge. | Sync not run | Run a provider asset sync | YES |
PC-NET-006 |
Network profile degraded | WARNING | A network profile is degraded. Please contact support. — The network profile health is degraded. | Bridge missing; VLAN mismatch | Review the network profile | YES |
PC-NET-007 |
No network profile | ERROR | No network profile is available for this host. Please contact support. — No enabled network profile exists for the hypervisor. | Profiles not synced | Create/sync a network profile | YES |
PC-NET-009 |
Reverse DNS unsupported | WARNING | Reverse DNS is not available for this address. — The pool or provider does not support PTR updates. | Provider unsupported; No reverse zone | Configure an rDNS provider | NO |
PC-NET-010 |
Reverse DNS update failed | ERROR | Updating reverse DNS failed. Please contact support. — The authoritative PTR update failed. | Provider API error; Zone mismatch | Check the rDNS provider | YES |
PC-NET-011 |
VLAN unavailable | WARNING | The required VLAN is unavailable on the target. — The target host does not carry the required VLAN. | VLAN not trunked | Add the VLAN to the target | CONDITIONAL |
IP Address Management¶
| Code | Title | Sev | Meaning | Common causes | Fix | Retry |
|---|---|---|---|---|---|---|
PC-IPAM-001 |
Duplicate IP assignment | CRITICAL | A duplicate IP address assignment was detected. Please contact support. — The same canonical IP is assigned to more than one resource. | Race condition; Manual edit | Resolve the duplicate manually — do not auto-reassign | NO |
PC-IPAM-002 |
IP limit reached | WARNING | The IP address limit for this server has been reached. — The per-instance IP limit is reached. | Plan limit | Release an address or upgrade | NO |
PC-IPAM-003 |
IP pool empty | WARNING | An IP pool is empty. Please contact support. — An IP pool has no free addresses. | Pool exhausted | Add capacity | YES |
PC-IPAM-004 |
No IPv4 address available | ERROR | No IPv4 address is available for this location. Please contact support. — No free IPv4 address exists for the hypervisor location. | Pool exhausted | Add a pool or expand the CIDR | YES |
Storage¶
| Code | Title | Sev | Meaning | Common causes | Fix | Retry |
|---|---|---|---|---|---|---|
PC-STO-001 |
Boot order invalid | WARNING | The requested boot order is not valid. — The boot order is not a supported provider-neutral value. | Unknown device | Choose disk, cdrom or network | NO |
PC-STO-002 |
LVM metadata usage high | WARNING | LVM metadata usage is high. Please contact support. — The LVM volume group metadata usage is above the warning threshold. | Many LVs; Metadata autoextend disabled | Expand LVM metadata capacity | NO |
PC-STO-003 |
No storage backend | ERROR | No storage backend is available for this host. Please contact support. — No enabled storage backend is bound to the hypervisor. | Backends not synced | Add/sync a storage backend | YES |
PC-STO-004 |
Storage backend offline | ERROR | A storage backend is offline. Please contact support. — The storage backend is not online. | Pool unavailable; Network storage down | Check the storage backend health | YES |
PC-STO-005 |
Storage drain failed | ERROR | Draining a storage backend failed. Please contact support. — The storage drain could not complete. | Migration failures | Review the drain items | CONDITIONAL |
PC-STO-006 |
Storage full | CRITICAL | A storage backend is full. New servers cannot be created. Please contact support. — The storage backend has no free space. | Disk full; Thin pool exhausted | Free space or expand the backend | YES |
PC-STO-007 |
Storage space low | WARNING | A storage backend is running low on space. Please contact support. — The storage backend is below the warning threshold. | Growth; Snapshots | Plan a capacity expansion | NO |
PC-STO-008 |
Storage mapping missing | ERROR | A required storage mapping is missing. Please contact support. — No storage provider mapping exists. | Sync not run | Run a provider asset sync | YES |
PC-STO-009 |
Storage tier unavailable | WARNING | The requested storage tier is unavailable. — No storage backend matches the requested tier. | Tier missing | Choose another tier | CONDITIONAL |
PC-STO-010 |
Volume attach failed | ERROR | Attaching a volume failed. Please contact support. — The volume attach operation failed. | Provider error; Backend full | Review the task | YES |
Images¶
| Code | Title | Sev | Meaning | Common causes | Fix | Retry |
|---|---|---|---|---|---|---|
PC-IMG-001 |
Image artifact missing | ERROR | A required image artifact is missing. Please contact support. — No READY native image artifact exists. | Import incomplete | Re-import the image artifact | YES |
PC-IMG-002 |
Image checksum mismatch | CRITICAL | An image failed its checksum verification. Please contact support. — The image artifact checksum does not match the manifest. | Corrupted transfer; Tampering | Re-import the image and re-verify | YES |
PC-IMG-003 |
Image revision missing | WARNING | The requested image revision is missing. — No revision record exists for the image. | Not imported | Import the revision | YES |
PC-IMG-004 |
Image revision not ready | WARNING | The selected image is not ready for provisioning. — The image revision is not in a READY state. | Revision importing; Revision failed | Wait for the revision to become ready | YES |
PC-IMG-005 |
Image unavailable | ERROR | The requested image is unavailable on the target host. — The image has no usable mapping/artifact on the host. | Artifact not ready | Sync the image to the host | YES |
PC-IMG-006 |
ISO unavailable | WARNING | The requested ISO is unavailable. — No usable ISO mapping exists. | Not imported | Import the ISO | YES |
PC-IMG-007 |
No image available | ERROR | No operating system image is available. Please contact support. — No enabled image is available for the request. | No images enabled | Enable or import an image | YES |
Console & SSH¶
| Code | Title | Sev | Meaning | Common causes | Fix | Retry |
|---|---|---|---|---|---|---|
PC-CON-001 |
Console agent missing | WARNING | The host does not support console sessions. Please contact support. — The agent does not advertise console capability. | Agent too old; Console disabled | Upgrade the agent or enable console | NO |
PC-CON-002 |
Console gateway down | ERROR | The console service is unavailable. Existing servers keep running. Please contact support. — No healthy console gateway has heartbeated. | Gateway stopped; Network issue | Start the console gateway | YES |
PC-CON-003 |
Console gateway protocol mismatch | WARNING | The console gateway protocol is incompatible. Please contact support. — The console gateway protocol version is unsupported. | Outdated gateway | Upgrade the console gateway | NO |
PC-CON-004 |
Console gateway unhealthy | WARNING | The console service is degraded. Please contact support. — The console gateway heartbeat is stale or its capacity is exhausted. | Overloaded; Stale heartbeat | Check the gateway | YES |
PC-CON-005 |
Console unavailable — instance offline | INFO | The console is unavailable because the server is not running. — The instance is not running so no console session exists. | Instance stopped | Start the instance | YES |
PC-CON-006 |
Console origin rejected | WARNING | The console connection was rejected. Please contact support. — The console origin was rejected by the gateway allow-list. | Origin misconfiguration | Correct the allowed origins | NO |
PC-CON-007 |
Console provider session failed | WARNING | The provider could not open a console session. Please contact support. — The provider rejected or failed the console session. | Provider API error | Check the provider | YES |
PC-CON-008 |
Console session failed | WARNING | Opening the console failed. Please try again or contact support. — A console session could not be established. | Provider session failure; Instance offline; Token expired | Retry the console session | YES |
PC-CON-009 |
Console token expired | INFO | The console session token expired. Please reload the console. — The console session token has expired. | Token TTL elapsed | Re-open the console | YES |
Backups & Snapshots¶
| Code | Title | Sev | Meaning | Common causes | Fix | Retry |
|---|---|---|---|---|---|---|
PC-BAK-001 |
Backup destination full | CRITICAL | A backup destination is full. Please contact support. — The backup destination has no free space. | Full destination | Prune old backups or expand | YES |
PC-BAK-002 |
Backup destination unreachable | ERROR | A backup destination is unreachable. Please contact support. — The backup destination cannot be reached. | Network issue; Credentials | Check the destination connection | YES |
PC-BAK-003 |
Backup failed | ERROR | A backup failed. Please contact support. — The backup operation failed. | Storage error; Provider error | Review the backup task | YES |
PC-BAK-004 |
Backup quota exceeded | WARNING | The backup quota has been exceeded. — The backup destination quota is exhausted. | Quota reached | Prune or expand | NO |
PC-BAK-005 |
Backup running | WARNING | A backup is already running. — A backup operation is in progress. | Concurrent operation | Wait for completion | YES |
PC-BAK-006 |
Backup verification failed | ERROR | A backup failed verification. Please contact support. — The backup verification did not pass. | Corrupted backup; Checksum mismatch | Re-run the backup | YES |
PC-BAK-007 |
Restore failed | ERROR | A restore failed. Please contact support. — The restore operation failed. | Corrupted backup; Provider error | Review the restore task | CONDITIONAL |
PC-BAK-008 |
Restore running | WARNING | A restore is already running. — A restore operation is in progress. | Concurrent operation | Wait for completion | YES |
PC-BAK-009 |
Snapshot failed | ERROR | A snapshot failed. Please contact support. — The snapshot operation failed. | Storage error | Review the snapshot task | YES |
Migration & Evacuation¶
| Code | Title | Sev | Meaning | Common causes | Fix | Retry |
|---|---|---|---|---|---|---|
PC-MIG-001 |
Migration cleanup failed | WARNING | Migration cleanup failed. Please contact support. — Residual source resources could not be cleaned up. | Provider error | Reconcile the residuals | YES |
PC-MIG-002 |
Migration commit failed | ERROR | Committing the migration failed. Please contact support. — The migration commit failed. | Database error | Recover the migration | YES |
PC-MIG-003 |
CPU profile incompatible | WARNING | The CPU profile is incompatible with the target. — The target CPU does not satisfy the instance CPU profile. | Different CPU model | Choose a compatible target | NO |
PC-MIG-004 |
Dedicated CPU unavailable on target | WARNING | Dedicated CPU is unavailable on the target. — The target cannot satisfy the dedicated CPU allocation. | Pool exhausted | Choose another target | YES |
PC-MIG-005 |
Migration disk verify failed | ERROR | The migrated disk failed verification. Please contact support. — The target disk verification failed. | Corrupted transfer | Do not cut over; recover the migration | CONDITIONAL |
PC-MIG-006 |
GPU is host-bound | WARNING | This instance uses a GPU bound to its host and cannot be migrated automatically. — A GPU passthrough binding prevents migration. | GPU passthrough | Manual recovery is required to move the instance | NO |
PC-MIG-007 |
Hardware passthrough is host-bound | WARNING | This instance uses a passthrough device and cannot be moved freely. — A PCI passthrough device binds the instance to its host. | GPU/PCI passthrough | A cold migration with device re-attachment is required | NO |
PC-MIG-008 |
Hugepages unavailable on target | WARNING | The target cannot satisfy the hugepage requirement. — The target lacks hugepage capacity. | Reserved pages | Reserve pages or choose another target | YES |
PC-MIG-009 |
Instance locked | WARNING | The instance is locked by another operation. — An exclusive lock is held on the instance. | Concurrent operation | Wait for the lock to expire | YES |
PC-MIG-010 |
Insufficient CPU on target | WARNING | The target host does not have enough CPU. — The target lacks CPU capacity for the instance. | Capacity | Free capacity or choose another target | YES |
PC-MIG-011 |
Insufficient memory on target | WARNING | The target host does not have enough memory. — The target lacks memory capacity. | Capacity | Free capacity or choose another target | YES |
PC-MIG-012 |
Insufficient storage on target | WARNING | The target host does not have enough storage. — The target lacks storage capacity. | Capacity | Free capacity or choose another target | YES |
PC-MIG-013 |
IP not portable | WARNING | The IP address cannot be moved to the target host. — The address is not portable across the source and target. | Different network | Migrate with a new address or a floating IP | NO |
PC-MIG-014 |
Nested virtualisation unsupported | WARNING | The target does not support nested virtualisation. — The target cannot provide nested virtualisation. | Nesting disabled | Enable nesting or choose another target | NO |
PC-MIG-015 |
Migration network prepare failed | ERROR | Preparing the target network failed. Please contact support. — The target network preparation failed. | Network error | Recover the migration | YES |
PC-MIG-016 |
Network unavailable on target | WARNING | The required network is unavailable on the target. — The target does not provide the required network. | Bridge/VLAN missing | Prepare the target network | YES |
PC-MIG-017 |
NUMA requirement unmet | WARNING | The NUMA requirement cannot be met on the target. — The target cannot satisfy the NUMA policy. | Fragmentation | Relax the policy or choose another target | YES |
PC-MIG-018 |
Migration preflight failed | ERROR | Migration preflight failed. Please contact support. — The migration preflight did not pass. | Blockers present | Resolve the blockers | YES |
PC-MIG-019 |
Private network locality | WARNING | The instance is attached to a private network local to its host. — A private network attachment prevents a cross-host move. | Private network | Use a shared network or accept the constraint | NO |
PC-MIG-020 |
Migration recovery required | CRITICAL | The migration needs manual recovery. Please contact support. — The migration is in a state that requires operator recovery. | Interrupted migration | Follow the migration recovery runbook | CONDITIONAL |
PC-MIG-021 |
Migration reservation failed | ERROR | The migration reservation failed. Please contact support. — The target reservation could not be created. | Capacity race | Retry | YES |
PC-MIG-022 |
Migration rollback failed | CRITICAL | Rolling back the migration failed. Please contact support. — The migration rollback failed. | Provider error | Manual recovery is required | NO |
PC-MIG-023 |
Snapshot state unsupported | WARNING | The instance snapshot state prevents migration. — The instance has snapshots that block migration. | Snapshots present | Remove snapshots or use a cold move | CONDITIONAL |
PC-MIG-024 |
Migration source stop failed | ERROR | Stopping the source failed. Please contact support. — The source instance could not be stopped. | Provider error | Recover the migration | YES |
PC-MIG-025 |
Target host in maintenance | WARNING | The migration target is in maintenance. — The target hypervisor is in maintenance mode. | Planned maintenance | Exit maintenance or choose another target | YES |
PC-MIG-026 |
Target host offline | WARNING | The migration target is offline. — The target hypervisor is not online. | Target down | Bring the target online | YES |
PC-MIG-027 |
Target provider incompatible | ERROR | The target provider is incompatible with this move. — The target provider driver cannot host the instance. | Cross-provider move unsupported | Use a compatible target | NO |
PC-MIG-028 |
Migration target start failed | ERROR | Starting the target failed. Please contact support. — The target instance could not be started. | Provider error | Recover the migration | YES |
PC-MIG-029 |
Migration target verify failed | ERROR | The target verification failed. Please contact support. — The target instance failed verification. | Boot failure | Recover the migration | CONDITIONAL |
PC-MIG-030 |
Migration transfer failed | ERROR | The disk transfer failed. Please contact support. — The migration disk transfer failed. | Network/storage error | Recover or retry the migration | CONDITIONAL |
High Availability¶
| Code | Title | Sev | Meaning | Common causes | Fix | Retry |
|---|---|---|---|---|---|---|
PC-HA-001 |
Evacuation failed | ERROR | Evacuating a host failed. Please contact support. — The hypervisor evacuation did not complete. | Migration failures | Review the evacuation items | CONDITIONAL |
PC-HA-002 |
HA fencing unavailable | WARNING | Automatic failover is unavailable because fencing is not configured. Existing servers keep running. — No fencing mechanism is configured; automatic recovery is disabled. | No power fencing; No STONITH | Configure fencing before enabling automatic failover | NO |
PC-HA-003 |
HA quorum lost | ERROR | The HA cluster has lost quorum. Please contact support. — The HA cluster cannot establish quorum. | Node failures; Network partition | Restore quorum | YES |
PC-HA-004 |
HA recovery failed | CRITICAL | HA recovery failed. Please contact support. — The HA recovery action failed. | Fencing/migration error | Manual recovery is required | NO |
PC-HA-005 |
HA split-brain risk | CRITICAL | A split-brain condition was detected. Please contact support immediately. — More than one node believes it owns a resource. | Fencing failure; Network partition | Fence the stale owner manually — do not auto-resolve | NO |
Security¶
| Code | Title | Sev | Meaning | Common causes | Fix | Retry |
|---|---|---|---|---|---|---|
PC-SEC-001 |
Cross-tenant device request | ERROR | The requested device belongs to another tenant. — A hardware allocation crossed a tenant boundary. | Shared pool | Assign a device within the tenant | NO |
PC-SEC-002 |
Security audit failure | ERROR | A security audit failed. Please contact support. — The security audit could not complete. | Permission error | Review the audit | YES |
PC-SEC-003 |
Authorization component missing | CRITICAL | PteroCloud authorization could not be verified. Please contact support. — A protection component declared by the signed release manifest is missing, modified or from another release. | Incomplete install; Modified protected files; Mixed release files | Reinstall from the official signed release; Run the repair action | NO |
PC-SEC-004 |
Corrupted installation | ERROR | The installation appears damaged. Please contact support. — A protected file or the release manifest is missing/corrupt (not necessarily tampering). | Interrupted upgrade; Failed extraction; Disk damage | Run the official repair/reinstall | YES |
PC-SEC-005 |
Security event delivery failed | WARNING | A security event could not be delivered yet. It is queued locally. — The security event outbox has pending deliveries. | Licensing server unreachable; Endpoint misconfigured | Check connectivity to the licensing server | YES |
PC-SEC-006 |
Insecure configuration | WARNING | An insecure configuration was detected. Please contact support. — A configuration weakens security. | TLS verification disabled; World-writable path; Default credentials | Restore the secure configuration — never weaken TLS or permissions | NO |
PC-SEC-007 |
Release integrity degraded | WARNING | A release integrity check is degraded. Please contact support. — The integrity state is WARNING/UNVERIFIED or an update is in progress. | Update in progress; Missing manifest | Re-run the integrity check after the update | YES |
PC-SEC-008 |
Release integrity failure | CRITICAL | A release integrity check failed. Please contact support. — The signed release manifest check failed for one or more protected files. | Modified protected files; Swapped manifest | Reinstall from the official signed release | NO |
PC-SEC-009 |
Installation security locked | CRITICAL | PteroCloud is temporarily unavailable pending a security review. Existing servers keep running. — The local SECURITY_LOCKED lock is engaged; protected operations are denied. | Confirmed integrity failure; Server security suspension | Complete the security recovery procedure | NO |
PC-SEC-010 |
Release manifest signature invalid | CRITICAL | The release manifest could not be verified. Please contact support. — The signed release manifest failed Ed25519 verification. | Swapped manifest; Wrong trusted key | Reinstall from the official signed release | NO |
PC-SEC-011 |
Security signal raised | WARNING | A security signal was raised. Please contact support. — A security signal was recorded. | Anomalous activity | Review the security signals | NO |
PC-SEC-012 |
Security subsystem missing | CRITICAL | The security subsystem is unavailable. Please contact support. — The commercial security services are not registered in the container. | Incomplete install; Removed package | Reinstall the extension from the official release | NO |
PC-SEC-013 |
Security tamper detected | CRITICAL | A tamper condition was detected. Please contact support immediately. — An integrity or tamper check failed. | Modified files; Replayed request | Review the security events immediately | NO |
Tenancy & Add-ons¶
| Code | Title | Sev | Meaning | Common causes | Fix | Retry |
|---|---|---|---|---|---|---|
PC-TEN-001 |
Add-on assignment requires an admin | WARNING | Resource add-ons can only be assigned by an administrator. — The actor is not an administrator. | Non-admin actor | Ask an administrator | NO |
PC-TEN-002 |
Add-on inactive | WARNING | The selected add-on is not available. — The add-on definition is inactive. | Definition disabled | Choose an active add-on | NO |
PC-TEN-003 |
Add-on not resizable | WARNING | This add-on cannot be assigned with a custom quantity. — The definition does not allow quantities other than one. | Not resizable | Assign a single unit | NO |
PC-TEN-004 |
Add-on entitlement exhausted | WARNING | The tenant does not have enough entitlement for this add-on. — The tenant entitlement for the add-on is exhausted. | Entitlement exhausted | Grant more entitlement first | NO |
PC-TEN-005 |
Entitlement exceeded | WARNING | You have reached your plan limit. Please contact support to upgrade. — The tenant entitlement would be exceeded. | Plan limit reached | Upgrade the entitlement | NO |
PC-TEN-006 |
Entitlement scope mismatch | WARNING | The requested resource is outside your entitlement scope. — The entitlement does not cover the requested scope. | Wrong location/plan | Choose a covered scope | NO |
PC-TEN-007 |
Tenant isolation violation | CRITICAL | A tenant isolation violation was detected. Please contact support immediately. — A cross-tenant data access was attempted or detected. | Authorization bug; Misconfiguration | Investigate immediately | NO |
PC-TEN-008 |
Tenant quota exceeded | WARNING | A tenant quota has been exceeded. — The tenant quota is exhausted. | Quota reached | Upgrade the quota | NO |
Tasks¶
| Code | Title | Sev | Meaning | Common causes | Fix | Retry |
|---|---|---|---|---|---|---|
PC-SYS-012 |
Instance mutation in progress | WARNING | Another operation is already running on this server. Please wait for it to finish. — A mutually exclusive instance mutation lock is held. | Rebuild in progress; Migration in progress; Rescue transition | Wait for the current operation to finish | YES |
PC-SYS-017 |
Rebuild confirmation required | WARNING | Rebuilding requires an explicit REINSTALL confirmation. — The typed REINSTALL confirmation was missing. | Missing confirmation | Confirm with the REINSTALL keyword | YES |
PC-SYS-018 |
Rebuild failed | ERROR | Rebuilding the server failed. Please contact support. — The rebuild pipeline failed. | Provider error; Image mapping missing | Review the rebuild task | YES |
PC-SYS-021 |
Rescue already active | INFO | Rescue mode is already active for this server. — An active rescue session already exists. | Session already open | Exit the current rescue session first | YES |
PC-SYS-022 |
Entering rescue failed | ERROR | Entering rescue mode failed. The original boot configuration is unchanged. — The rescue entry flow failed before completing. | Provider error | Retry or check the provider | YES |
PC-SYS-023 |
Exiting rescue failed | ERROR | Exiting rescue mode failed. Please contact support. — The rescue exit flow could not complete. | Provider error | Check the provider | YES |
PC-SYS-024 |
Rescue medium not approved | WARNING | The selected rescue medium is not available for this server. — The ISO is not an approved, mapped rescue medium. | ISO not flagged rescue; No provider mapping | Choose an approved rescue medium | YES |
PC-SYS-025 |
No active rescue session | INFO | Rescue mode is not currently active for this server. — No active rescue session exists. | No session | Enter rescue mode first | YES |
PC-SYS-026 |
Rescue recovery required | CRITICAL | Rescue mode could not restore the original boot configuration. Please contact support. — The original boot configuration could not be proven restored. | Provider error during restore | Reconcile the boot configuration manually | NO |
PC-SYS-027 |
Rescue mode unsupported | WARNING | Rescue mode is not available for this server. Please contact support. — The provider or instance cannot enter rescue mode. | Provider unsupported; Instance not provider-mapped | Use a supported provider | NO |
PC-SYS-028 |
Stale reservation | WARNING | A stale resource reservation was detected. — A reservation has expired but was not released. | Worker crash | Release the reservation | YES |
PC-SYS-032 |
Task failed | ERROR | A background task failed. Please contact support. — The task reached a failed terminal state. | Provider error; Validation error | Review the task events | CONDITIONAL |
PC-SYS-033 |
Task lock held | WARNING | A background operation is holding a lock. — An exclusive task lock is currently held. | Long-running task | Wait for the lock to expire | YES |
PC-SYS-034 |
Orphaned resource found | WARNING | An orphaned resource was detected. Please contact support. — A provider resource exists without a panel record. | Rollback incomplete; Manual creation | Reconcile manually — never auto-delete | NO |
PC-SYS-035 |
Task stuck | WARNING | A background task appears stuck. Please contact support. — The task has exceeded its class-specific stuck threshold. | Provider hung; Worker crashed; Lock held | Wait, retry, or reconcile safely | CONDITIONAL |
PC-SYS-036 |
Task timed out | WARNING | A background task timed out. Please contact support. — The task exceeded its timeout budget. | Slow provider | Retry the task | YES |
Database¶
| Code | Title | Sev | Meaning | Common causes | Fix | Retry |
|---|---|---|---|---|---|---|
PC-SYS-004 |
Database slow | WARNING | The database is responding slowly. — Database query latency is above the warning threshold. | Load; Missing indexes | Review database performance | NO |
PC-SYS-005 |
Database unreachable | CRITICAL | The cloud control plane cannot reach its database. Please contact support. — The database connection failed. | Database down; Network issue; Bad credentials | Check the database service | YES |
PC-SYS-006 |
Database migrations pending | ERROR | Pending database migrations were detected. Please contact support. — There are pending migrations. | Upgrade not completed | Run pending migrations | YES |
PC-UPD-002 |
Database version unsupported | ERROR | The database version is not supported. Please contact support. — The database server version is outside the supported range. | Outdated database | Upgrade the database | NO |
Queue¶
| Code | Title | Sev | Meaning | Common causes | Fix | Retry |
|---|---|---|---|---|---|---|
PC-SYS-014 |
Queue backlog | WARNING | The job queue has a backlog. — Pending queue depth is above the warning threshold. | Insufficient workers | Add queue workers | YES |
PC-SYS-015 |
Queue failed jobs | WARNING | Some background jobs failed. Please contact support. — The failed-jobs table contains recent entries. | Job exception; Worker issue | Review and retry the failed jobs | YES |
PC-SYS-016 |
Queue worker not running | ERROR | Background jobs are not being processed. Some actions may be delayed. — No queue worker has processed jobs recently. | Worker not running; Supervisor stopped; Queue connection misconfigured | Start the queue worker; Check the queue connection | YES |
PC-SYS-019 |
Redis read/write failed | ERROR | The cloud cache failed a read/write check. Please contact support. — A Redis round-trip failed. | Memory pressure; Read-only replica | Check the Redis service | YES |
PC-SYS-020 |
Redis unreachable | ERROR | The cloud cache is unavailable. Please contact support. — The Redis connection failed. | Redis down; Bad credentials | Check the Redis service | YES |
PC-SYS-029 |
Task scheduler not running | ERROR | Background maintenance is not running. Some actions may be delayed. — The Laravel scheduler has not run recently. | Cron not installed; Scheduler disabled | Verify the cron entry for schedule:run | YES |
PC-UPD-005 |
Redis version unsupported | WARNING | The Redis version is not supported. Please contact support. — The Redis server version is outside the supported range. | Outdated Redis | Upgrade Redis | NO |
Internal¶
| Code | Title | Sev | Meaning | Common causes | Fix | Retry |
|---|---|---|---|---|---|---|
PC-SYS-000 |
Internal error | ERROR | An internal error occurred. Please contact support and quote the support id. — An unclassified internal error occurred; no stack trace is exposed to customers. | Unexpected exception | Review the diagnostic error event for the support id | CONDITIONAL |
PC-SYS-007 |
Diagnostic run cancelled | INFO | The diagnostic run was cancelled. — The diagnostic run was cancelled by an operator. | Operator cancellation | No action required | YES |
PC-SYS-008 |
Diagnostic check timed out | WARNING | A diagnostic check timed out. Partial results are shown. — A single diagnostic check exceeded its per-check timeout. | Slow dependency | Re-run the diagnostics | YES |
PC-SYS-013 |
Internal timeout | WARNING | An internal operation timed out. Please try again. — An internal operation exceeded its time budget. | Slow dependency | Retry the operation | YES |