Common Symptoms
| Symptom | Check |
|---|---|
| Encoded PHP fails to load | Web/CLI PHP target, compatible ionCube Loader, package integrity and PHP read permissions. |
| Test Connection fails | Assigned NAS hostname, port, parent dataset, API permissions, routing and trusted certificates. |
| Web works but cron fails | CLI PHP/Loader, CA trust, permissions and consistent server identity. |
| Connection fails after IP addition | Actual source address after NAT, selected account, firewall and global protocol daemon. |
| Password change refused | Supported NAS version, closed protocols, no active sessions and owned resource state. |
| Snapshot restore refused | Ownership, bundle completeness and session/protocol requirements. |
Preserve Recovery Evidence
For an uncertain operation, record the timestamp, exact message and service identity. Keep recovery journals and avoid repeated destructive requests. Do not change NAS ownership metadata or remove journals to force a success.
TLS And Licensing
Correct CA trust or certificate configuration rather than disabling verification. An issuer outage is subject to the existing signed cache and expiry limits; it does not authorize bypassing licensing or resetting installation identity.
Escalate
Stop on unexpected cross-account effects, ownership mismatches or inconsistent file/block restore results. Use the support checklist and sanitize all screenshots.