If a CipherDrive™ file will not download or decrypt, determine whether the failure happens before the encrypted bytes arrive or after decryption begins.
Possible causes include:
expired session;
revoked or invalid Public Link;
account restriction;
subscription or entitlement problem;
transfer or rate limit;
object no longer available;
security or trust-and-safety restriction.
These are access or service-state problems, not cryptographic failures.
Check:
network stability;
VPN or proxy behavior;
available transfer allowance;
browser stability;
device sleep or tab suspension;
available disk space where the browser needs it.
This can happen if:
the file key cannot be unwrapped;
the device no longer has the required vault material;
the wrong sharing key or vault context is being used;
encrypted data is incomplete or corrupted;
AES-GCM authentication fails for one or more chunks;
the current client cannot process the object or protocol correctly.
CipherDrive uses authenticated encryption where documented. If ciphertext, IVs, keys, or authenticated context do not match correctly, decryption should fail rather than silently returning data that appears valid.
If the file works on another existing trusted device, the problem may be local key state or client compatibility on the failing device.
Do not clear the working device's data until you have restored or backed up the file.
Clearing local site data can remove wrapped key material or remembered vault state and cause an otherwise healthy encrypted object to become inaccessible on that device until the vault is unlocked again.
If every other file works, collect the object's error information. A single-file failure may indicate an object-specific integrity, transfer, or key problem.
For a shared file, make sure:
you have the complete link;
the link has not been revoked;
the source object still exists;
the full URL was not truncated;
the recipient browser is not modifying the link;
transfer controls are not blocking access.
If the sharing protocol uses URL-fragment key material, a truncated link can remove information needed for decryption.
Tell support which of these is true:
download never begins;
download starts but stops;
encrypted bytes arrive but decryption fails;
only one file is affected;
only one device is affected.
If Ackaia does not possess the missing cryptographic key, support may be unable to decrypt the file on your behalf.