A Shared CipherDrive Link Isn't Working

A CipherDrive™ shared link can fail because of the link itself, the source object, server-side access controls, transfer limits, browser behavior, or missing client-side key material.

1. Make sure you have the complete link

Encrypted sharing may use information in the full URL, including client-side key material in a URL fragment after #.

If the link was truncated by an email client, chat app, document, ticketing system, or manual copy-and-paste, the browser may be able to find the object but still be unable to decrypt it.

2. The owner may have revoked the link

A revoked Public Link can stop future access through CipherDrive even though the URL text still exists in an old message or browser history.

3. The source object may no longer exist

The owner may have:

deleted the file;
removed the share;
changed the object's state;
closed or lost access to the relevant account;
made the object unavailable to that sharing workflow.

4. The link may be restricted

Ackaia may restrict a Public Link because of:

security controls;
malware or abuse signals;
trust-and-safety enforcement;
copyright procedures;
valid legal process;
account restrictions;
other applicable policy reasons.

Restricting distribution does not require Ackaia to decrypt the file.

5. A transfer or rate limit may apply

Public Link downloads can be affected by bandwidth, transfer, request, or rate controls.

If the link reports a temporary quota or rate error, follow the reset or retry guidance shown by the product.

6. The browser may be modifying the link

URL-processing extensions, privacy tools, security software, link scanners, or third-party applications can sometimes transform complete links.

Try opening the original link in a current supported browser on a trusted device, without manually editing it.

7. The encrypted file loads but does not decrypt

If the object is served but the browser cannot decrypt it, the complete sharing key material may be missing or the object/key context may be invalid.

Ask the sender to create a fresh share rather than trying to guess or reconstruct missing key material.

What should the owner check?

If you created the link:

confirm the source file still exists;
confirm the share is active;
review transfer or rate-limit warnings;
create a fresh link if compromise or truncation is suspected;
test the link in a separate trusted browser context.

Never ask the owner to send you a master key, file key, vault passphrase, or recovery phrase to “fix” a broken share.