> For the complete documentation index, see [llms.txt](https://help.jurisphere.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.jurisphere.ai/resources/errors-and-faqs/upload-failed-while-uploading-file.md).
# Upload Failed While Uploading File
In rare instances, while [uploading a file](/getting-started/browsing-files-on-jurisphere/uploading-files-and-folders.md), you might notice the upload bar turning red and displaying a message like “Upload failed”
Or a notification containing:
> `Failed to upload "[filename].docx". Please try again.`\
> *(with a red ❗ icon, indicating failure)*
This is different from an [upload that fails during processing](https://claude.ai/resources/errors-and-faqs/upload-failed-while-processing-file.md). If you're seeing this message, your file never reached Jurisphere's servers at all.
{% hint style="info" %}
**How to tell the two apart:** if the failure shows up as a red bar inside the upload window itself, it's an **upload** failure. If the file uploads successfully and a failure notification appears later from the bell icon, it's a [**processing** failure](https://claude.ai/resources/errors-and-faqs/upload-failed-while-processing-file.md) instead.
{% endhint %}
### **Why This Happens:**
1. **The file is too large** - Jurisphere allows files of up to **250MB** each. If your file is larger than this, the upload will fail with the red bar shown above.
* If this is the case, try compressing the file or splitting it into smaller parts before uploading again.
* See Uploading files and folders for the full list of supported file types, formats, and upload limits.
2. **Internet Security** - When you upload a file, it travels straight from your computer to our secure cloud storage. This keeps uploads fast, but it also means your company's internet security can sometimes get in the way before the file ever reaches us.
This usually comes down to your organization's network or security settings, often set up by your IT or security team, quietly blocking the upload. This is more common at companies with stricter security policies.
* **Corporate firewall or proxy blocking the request** - some networks allow standard web traffic but block or strip outbound requests to cloud storage domains like `storage.googleapis.com`.
* **DLP (Data Loss Prevention) rules** - many organizations, especially in regulated industries like finance, run DLP agents that block uploads to any cloud storage domain not on an explicit allowlist.
* **Blocked or mangled `PUT` requests** - some proxies allow `GET`/`POST` traffic through but block or interfere with the `PUT` method specifically, which is what the upload uses.
* **SSL-inspecting proxies** - if your network intercepts and re-signs HTTPS traffic, the re-signed request can be rejected by our storage provider due to a signature mismatch.
### **What to Do:**
1. **Check your file size.** If it's over 250MB, compress or split it and try again. ([See Uploading files and folders for more on file limits](/getting-started/browsing-files-on-jurisphere/uploading-files-and-folders.md))
2. **Retry the upload once**, ideally on a different network (for example, personal mobile hotspot) to confirm whether it's network related.
3. **Ask your IT team to allow outbound HTTPS (443) traffic to** `storage.googleapis.com` **(and ideally** `*.googleapis.com`**)**. This is the actual endpoint your browser sends the file to after Jurisphere hands it a secure upload link.
4. **Ask IT to check that your firewall/proxy isn't blocking or stripping the** `PUT` **method**, even if `GET` and `POST` requests are allowed through.
5. **Ask IT to check for DLP (Data Loss Prevention) rules** that may be blocking uploads to cloud storage domains not on an explicit allowlist — common at financial services and other regulated organizations.
6. **If your network uses an SSL-inspecting proxy**, ask IT to rule out signature mismatches on the re-signed request to our storage provider.
7. **For the fastest diagnosis**, open your browser's Developer Tools → **Network** tab, retry the upload, and filter for `storage.googleapis.com`. Note the status or error shown on that specific request (blocked, timeout, 403, etc.) and share it with your IT team or with us. This one detail tells us exactly which layer is blocking the upload, instead of guessing.
***
**If the issue persists after checking the above**, contact us:
* **Via the support group** on your onboarding channel
* **Or through the in-app support bot**
* **WhatsApp** - Message us directly at +91 91370 20567
* **Email** - Drop us a line at
When reaching out, please include your organization's email domain (for example - @yourcompany.com) and, if possible, the network request details from the DevTools Network tab above. This lets us confirm whether it's a whitelisting issue on your end and get you unblocked faster.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://help.jurisphere.ai/resources/errors-and-faqs/upload-failed-while-uploading-file.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
