Viewer error codes: what to do next
Find the code shown in the viewer. Each explanation tells you what happened and how to continue; payment does not repair a file.
Open the file viewerencrypted — the file needs decryption
Cause: the CMS container is encrypted rather than readable signed content. Opening it requires the intended recipient’s private key. UnwrapDoc never accepts private keys or decrypts these containers.
What to do: ask the sender for a signed copy that is not encrypted, or use the recipient’s appropriate decryption software on your device. Never send your private key, key password or document to support. Buying access cannot decrypt the file.
damaged — the structure could not be read
Cause: the file is empty, incomplete or has an unreadable structure. Broken CMS or base64 data can trigger this code. During preview or export, it can also mean the contained document or image could not be decoded. It does not by itself prove tampering.
What to do: save the attachment again from the original email, PEC message or portal and check that the download completed. Choose the untouched file; renaming it will not repair its bytes. If it still fails, ask the sender for another copy. If only a PDF copy fails, keep or download the original instead.
unsupported — this content is not supported
Cause: the viewer does not recognize the format or support this CMS content type. A familiar extension does not guarantee that the contents are supported. Some attachments can be listed and downloaded without a preview or PDF-copy renderer.
What to do: check you selected the intended P7M, P7S, FatturaPA, PDF, image, text or XML file. Use the original application for other formats, or ask the sender for a supported copy while keeping the signed original. Renaming an extension or paying does not add format support.
too_large — a processing limit was reached
Cause: the input exceeds the MiB limit shown in the viewer, or the unpacked content or attachment count exceeds a safety limit. Unpacked content is limited to 500 MiB on desktop and 100 MiB on phones, with at most 1,000 parts. The account’s input limit is separate from those limits.
PDF-copy generation also limits text to 1,048,576 characters and 15,000 wrapped lines. An export can therefore fail even after the file opened successfully.
What to do: choose a smaller file or ask the sender to split the source into separate signed files. Do not edit a signed file to shrink it: changing its bytes can break its checks. For a failed PDF copy, download the original; for phone memory limits, try a desktop. Payment alone does not remove the unpacking, attachment or PDF-copy limits.
too_deep — too many nested signed containers
Cause: the document is wrapped in more than five signed container layers, such as repeated P7M containers inside each other. This is a nesting limit, not a count of signers on a single layer.
What to do: ask the sender for a version with fewer nested layers, or use software that supports that structure. Retain the original container for its signatures. Payment does not raise this nesting limit.
timeout — processing took too long
Cause: a worker operation did not finish within 30 seconds and was stopped. A complex file or a device short of resources can trigger this; the code alone does not mean the signature is incorrect.
What to do: close other busy tabs and use Retry. If it repeats, try a desktop browser or ask for a smaller source file. Keep your original. Repeated retries or a purchase cannot guarantee that an unusually complex file will open.
cancelled — processing was stopped
Cause: opening stopped before completion, for example because you selected Cancel, closed the file or left the page. A cancelled batch may also contain files that were not processed.
What to do: choose the file again when you are ready. For a detached signature, select the P7S and then its original again. Cancellation is not a failed signature check and does not mean the file needs repair.
load_failed — the viewer could not complete an operation
Cause: part of the viewer could not load or an unexpected browser error interrupted opening, checking or export. A connection problem, unavailable script or browser restriction can cause this. It is not a signature verdict.
What to do: check your connection and try Retry where offered. If necessary, reload in an up-to-date browser and select the file again; reloading clears the current file. If it persists, report the error code, action, extension and browser version through the Help center. Do not send document content, signature files, passwords or private keys.