# "Error: Connection errored out" during processing

**URL:** </static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Ferror-connection-errored-out-during-processing%2F23439%3E%5C
**Category:** Spaces\
**Created:** [September 21, 2022, 12:53pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Ferror-connection-errored-out-during-processing%2F23439 "2022-09-21T12:53:07Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![gigant](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/gigant/32/20755_2.png) [@gigant](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2Fgigant)%5C
**Post date:** [September 21, 2022, 12:53pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Ferror-connection-errored-out-during-processing%2F23439%2F1 "2022-09-21T12:53:07Z")

</div>

Hi,

I have written a gradio app that processes videos. When launched in Colab (with CPU or GPU) it works, but when I host the app on Spaces, I have a “Connection errored out” error ~4 / 5 seconds after it starts to process the video.

 ![image](https://us1.discourse-cdn.com/hellohellohello/original/2X/8/873bde601fb268a3f0c39263a33a9ba2d8f07b14.jpeg)

In the forum, I saw similar problems being resolved by setting “cache\_examples=False” but this option doesn’t seem to exist for gradio.Blocks

url of the Space: [Slideshow Extraction - a Hugging Face Space by gigant](https://huggingface.co/spaces/gigant/slideshow_extraction)

Thanks

---

<div class="post-metadata">

**Author:** ![chris-rannou](https://avatars.discourse-cdn.com/v4/letter/c/7feea3/32.png) [@chris-rannou](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2Fchris-rannou)%5C
**Post date:** [November 23, 2022, 9:09am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Ferror-connection-errored-out-during-processing%2F23439%2F2 "2022-11-23T09:09:33Z")

</div>

The issue does not appear in Colab because it is linked to the queue that is enabled by default when running in Spaces.

Here is the associated issue to fix this bug: [Using `gr.File` as an input fails with large files when the queue is activated · Issue #2700 · gradio-app/gradio · GitHub](https://github.com/gradio-app/gradio/issues/2700).  
Fix is included in Gradio release 3.11.

---

<div class="post-metadata">

**Author:** ![englert](https://avatars.discourse-cdn.com/v4/letter/e/5f8ce5/32.png) [@englert](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2Fenglert)%5C
**Post date:** [November 23, 2022, 9:29am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Ferror-connection-errored-out-during-processing%2F23439%2F3 "2022-11-23T09:29:53Z")

</div>

Updated requirements.txt to include gradio==3.11. Still getting the same error

---

<div class="post-metadata">

**Author:** ![greendra](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/greendra/32/46012_2.png) [@greendra](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2Fgreendra)%5C
**Post date:** [November 23, 2022, 11:44pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Ferror-connection-errored-out-during-processing%2F23439%2F4 "2022-11-23T23:44:49Z")

</div>

> [@englert](#):
>
> gradio==3.11

to set a specific version, you need to set it like `sdk_version: 3.11` in the readme file