Navigate to https://uppy.io/examples/ and upload a test, non-sensitive .docx or .pdf file to the page.
​
​Note Hyperproof uses this same underlying upload component. If the file fails to upload here as well, your IT team should inspect your Data Loss Prevention (DLP) rules, antivirus or endpoint protection, and proxy filters that target Word or PDF MIME types. This is common in high-security or FedRAMP environments. If the upload succeeds on Uppy, the issue may be specific to Hyperproof; if it fails on both, the issue is likely rooted in your local network or endpoint security policies.

Capture a video clip showing the upload problem and the specific Hyperproof objects involved.

Collect a HAR file during a failed proof upload attempt. This will provide us with the network logs that were recorded when the upload failed.
To collect the HAR file:
Open your developer tools by pressing F12 on your keyboard.
Click the Network tab and leave this panel open. (Press the + sign to find the Network tab if you don't see it.)
In Hyperproof, try to upload your file.
When the upload fails, click the Export HAR button in developer tools (example below).
Download, save, and return the file to Support.

Provide steps detailing where you are pulling the files from. This will help the Support team try to reproduce the issue.

Tell Support the scope of the issue by identifying if it occurs with one user or many, and on one machine or all. This will help us confirm whether the issue is isolated to a specific user configuration or tied to a broader environment policy.

Send the HAR file, video clip, scope details, file source instructions, and test results to Hyperproof Support by emailing [email protected].