github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-05-07 11:28:35 -05:00
Code Issues 1.3k Packages Projects Releases 126 Wiki Activity

[GH-ISSUE #15023] refac: make file upload process async (w/ polling) #56108

New Issue
Closed
opened 2026-05-05 18:43:09 -05:00 by GiteaMirror · 14 comments
GiteaMirror commented 2026-05-05 18:43:09 -05:00
Owner
Copy Link

Originally created by @tjbck on GitHub (Jun 16, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/15023

Originally assigned to: @tjbck on GitHub.

Originally created by @tjbck on GitHub (Jun 16, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/15023 Originally assigned to: @tjbck on GitHub.
GiteaMirror commented 2026-05-05 18:43:13 -05:00
Author
Owner
Copy Link

@kns-12 commented on GitHub (Jul 16, 2025):

@tjbck is there currently any planning on when this feature is going to be added?
And maybe a short term solution via environment variable which increases the Gateway Timeout?

<!-- gh-comment-id:3077374165 --> @kns-12 commented on GitHub (Jul 16, 2025): @tjbck is there currently any planning on when this feature is going to be added? And maybe a short term solution via environment variable which increases the Gateway Timeout?
GiteaMirror commented 2026-05-05 18:43:15 -05:00
Author
Owner
Copy Link

@rgaricano commented on GitHub (Jul 16, 2025):

@tjbck is there currently any planning on when this feature is going to be added? And maybe a short term solution via environment variable which increases the Gateway Timeout?

https://docs.openwebui.com/getting-started/env-configuration#aiohttp-client

& setting in reverse proxy if you use it.

<!-- gh-comment-id:3077529976 --> @rgaricano commented on GitHub (Jul 16, 2025): > [@tjbck](https://github.com/tjbck) is there currently any planning on when this feature is going to be added? And maybe a short term solution via environment variable which increases the Gateway Timeout? https://docs.openwebui.com/getting-started/env-configuration#aiohttp-client & setting in reverse proxy if you use it.
GiteaMirror commented 2026-05-05 18:43:16 -05:00
Author
Owner
Copy Link

@kns-12 commented on GitHub (Jul 16, 2025):

@tjbck is there currently any planning on when this feature is going to be added? And maybe a short term solution via environment variable which increases the Gateway Timeout?

https://docs.openwebui.com/getting-started/env-configuration#aiohttp-client

& setting in reverse proxy if you use it.

@rgaricano is that related to the 30 seconds Gateway Timeout for document Uploading/Embedding?
According to the docs, the default is already set to 300 seconds.

How would a reverse proxy tackle the internal timeout of Open WebUI?

<!-- gh-comment-id:3077544186 --> @kns-12 commented on GitHub (Jul 16, 2025): > > [@tjbck](https://github.com/tjbck) is there currently any planning on when this feature is going to be added? And maybe a short term solution via environment variable which increases the Gateway Timeout? > > https://docs.openwebui.com/getting-started/env-configuration#aiohttp-client > > & setting in reverse proxy if you use it. @rgaricano is that related to the 30 seconds Gateway Timeout for document Uploading/Embedding? According to the docs, the default is already set to 300 seconds. How would a reverse proxy tackle the internal timeout of Open WebUI?
GiteaMirror commented 2026-05-05 18:43:18 -05:00
Author
Owner
Copy Link

@rgaricano commented on GitHub (Jul 16, 2025):

maybe? https://github.com/open-webui/open-webui/discussions/11345#discussioncomment-12423102

I don't know if you are using proxy to access, just a suggestion for check.
(any console log? )

<!-- gh-comment-id:3077630502 --> @rgaricano commented on GitHub (Jul 16, 2025): maybe? https://github.com/open-webui/open-webui/discussions/11345#discussioncomment-12423102 I don't know if you are using proxy to access, just a suggestion for check. (any console log? )
GiteaMirror commented 2026-05-05 18:43:19 -05:00
Author
Owner
Copy Link

@kns-12 commented on GitHub (Jul 16, 2025):

maybe? #11345 (comment)

I don't know if you are using proxy to access, just a suggestion for check. (any console log? )

Nope, I am not using any proxy to access it.
I described my situation here: https://github.com/open-webui/open-webui/issues/15758 but it has been closed in favour of this current issue.
I am just getting a Gateway Timeout after exactly 30 seconds each time I try to upload a large file.
Concerning the Open WebUI logs, it just keeps embedding the document, after removing it from the chat due to the Gateway Timeout.

<!-- gh-comment-id:3077803949 --> @kns-12 commented on GitHub (Jul 16, 2025): > maybe? [#11345 (comment)](https://github.com/open-webui/open-webui/discussions/11345#discussioncomment-12423102) > > I don't know if you are using proxy to access, just a suggestion for check. (any console log? ) Nope, I am not using any proxy to access it. I described my situation here: https://github.com/open-webui/open-webui/issues/15758 but it has been closed in favour of this current issue. I am just getting a Gateway Timeout after exactly 30 seconds each time I try to upload a large file. Concerning the Open WebUI logs, it just keeps embedding the document, after removing it from the chat due to the Gateway Timeout.
GiteaMirror commented 2026-05-05 18:43:20 -05:00
Author
Owner
Copy Link

@rgaricano commented on GitHub (Jul 16, 2025):

follow on your opened thread

<!-- gh-comment-id:3077842355 --> @rgaricano commented on GitHub (Jul 16, 2025): follow on your opened thread
GiteaMirror commented 2026-05-05 18:43:20 -05:00
Author
Owner
Copy Link

@avmturo commented on GitHub (Aug 1, 2025):

maybe? #11345 (comment)

I don't know if you are using proxy to access, just a suggestion for check. (any console log? )

Nope, I am not using any proxy to access it.
I described my situation here: https://github.com/open-webui/open-webui/issues/15758 but it has been closed in favour of this current issue.
I am just getting a Gateway Timeout after exactly 30 seconds each time I try to upload a large file.
Concerning the Open WebUI logs, it just keeps embedding the document, after removing it from the chat due to the Gateway Timeout.

Marked as duplicate but my understanding is there is actually a couple of separate issues here. To yours specifically, I don't not think the timeout is coming from the OWUI server or config. I have the exact same issues, 504 gateway timeout in the file uploads, when the embedding takes more than 1minute, the POST to files from the frontend times out. For me this timeout comes from my ALB idle timeout. If it is 30 seconds for you it is coming from some other gateway/api/proxy that you have.

This issue thread should fix this by adding the polling, to keep that timeout from idling and is a general improvement. But you could fix it by increasing wherever this timeout is coming from.

I'm on mobile now but will take a proper look when I'm home this weekend.

<!-- gh-comment-id:3144588470 --> @avmturo commented on GitHub (Aug 1, 2025): > > maybe? [#11345 (comment)](https://github.com/open-webui/open-webui/discussions/11345#discussioncomment-12423102) > > > > I don't know if you are using proxy to access, just a suggestion for check. (any console log? ) > > Nope, I am not using any proxy to access it. > I described my situation here: https://github.com/open-webui/open-webui/issues/15758 but it has been closed in favour of this current issue. > I am just getting a Gateway Timeout after exactly 30 seconds each time I try to upload a large file. > Concerning the Open WebUI logs, it just keeps embedding the document, after removing it from the chat due to the Gateway Timeout. Marked as duplicate but my understanding is there is actually a couple of separate issues here. To yours specifically, I don't not think the timeout is coming from the OWUI server or config. I have the exact same issues, 504 gateway timeout in the file uploads, when the embedding takes more than 1minute, the POST to files from the frontend times out. For me this timeout comes from my ALB idle timeout. If it is 30 seconds for you it is coming from some other gateway/api/proxy that you have. This issue thread should fix this by adding the polling, to keep that timeout from idling and is a general improvement. But you could fix it by increasing wherever this timeout is coming from. I'm on mobile now but will take a proper look when I'm home this weekend.
GiteaMirror commented 2026-05-05 18:43:20 -05:00
Author
Owner
Copy Link

@avmturo commented on GitHub (Aug 1, 2025):

maybe? #11345 (comment)

I don't know if you are using proxy to access, just a suggestion for check. (any console log? )

Nope, I am not using any proxy to access it.
I described my situation here: https://github.com/open-webui/open-webui/issues/15758 but it has been closed in favour of this current issue.
I am just getting a Gateway Timeout after exactly 30 seconds each time I try to upload a large file.
Concerning the Open WebUI logs, it just keeps embedding the document, after removing it from the chat due to the Gateway Timeout.

Marked as duplicate but my understanding is there is actually a couple of separate issues here. To yours specifically, I don't not think the timeout is coming from the OWUI server or config. I have the exact same issues, 504 gateway timeout in the file uploads, when the embedding takes more than 1minute, the POST to files from the frontend times out. For me this timeout comes from my ALB idle timeout. If it is 30 seconds for you it is coming from some other gateway/api/proxy that you have.

The proper issue I think is about why the POST request hangs, while the embedding is happening. The issue does not persist when the embedding is bypassed.

I'm on mobile now but will take a proper look when I'm home this weekend.

@kns-12 - Quick Look shows GCP and Heroku have some default timeouts of 30 seconds - here is my understanding of what's going on for you:

  1. Frontend Posts to files endpoint (begin timer)
  2. Server file endpoint calls process_file
  3. File processing take more then 30seconds
  4. Your request from the frontend timeout (unrelated to the owui server), due to some config from the above mentioned
<!-- gh-comment-id:3144622369 --> @avmturo commented on GitHub (Aug 1, 2025): > > > maybe? [#11345 (comment)](https://github.com/open-webui/open-webui/discussions/11345#discussioncomment-12423102) > > > > > > I don't know if you are using proxy to access, just a suggestion for check. (any console log? ) > > > > Nope, I am not using any proxy to access it. > > I described my situation here: https://github.com/open-webui/open-webui/issues/15758 but it has been closed in favour of this current issue. > > I am just getting a Gateway Timeout after exactly 30 seconds each time I try to upload a large file. > > Concerning the Open WebUI logs, it just keeps embedding the document, after removing it from the chat due to the Gateway Timeout. > > Marked as duplicate but my understanding is there is actually a couple of separate issues here. To yours specifically, I don't not think the timeout is coming from the OWUI server or config. I have the exact same issues, 504 gateway timeout in the file uploads, when the embedding takes more than 1minute, the POST to files from the frontend times out. For me this timeout comes from my ALB idle timeout. If it is 30 seconds for you it is coming from some other gateway/api/proxy that you have. > > > The proper issue I think is about why the POST request hangs, while the embedding is happening. The issue does not persist when the embedding is bypassed. > > I'm on mobile now but will take a proper look when I'm home this weekend. @kns-12 - Quick Look shows GCP and Heroku have some default timeouts of 30 seconds - here is my understanding of what's going on for you: 1. Frontend Posts to files endpoint (begin timer) 2. Server file endpoint calls process_file 3. File processing take more then 30seconds 4. Your request from the frontend timeout (unrelated to the owui server), due to some config from the above mentioned
GiteaMirror commented 2026-05-05 18:43:21 -05:00
Author
Owner
Copy Link

@kns-12 commented on GitHub (Aug 5, 2025):

maybe? #11345 (comment)
I don't know if you are using proxy to access, just a suggestion for check. (any console log? )

Nope, I am not using any proxy to access it.
I described my situation here: #15758 but it has been closed in favour of this current issue.
I am just getting a Gateway Timeout after exactly 30 seconds each time I try to upload a large file.
Concerning the Open WebUI logs, it just keeps embedding the document, after removing it from the chat due to the Gateway Timeout.

Marked as duplicate but my understanding is there is actually a couple of separate issues here. To yours specifically, I don't not think the timeout is coming from the OWUI server or config. I have the exact same issues, 504 gateway timeout in the file uploads, when the embedding takes more than 1minute, the POST to files from the frontend times out. For me this timeout comes from my ALB idle timeout. If it is 30 seconds for you it is coming from some other gateway/api/proxy that you have.
The proper issue I think is about why the POST request hangs, while the embedding is happening. The issue does not persist when the embedding is bypassed.
I'm on mobile now but will take a proper look when I'm home this weekend.

@kns-12 - Quick Look shows GCP and Heroku have some default timeouts of 30 seconds - here is my understanding of what's going on for you:

  1. Frontend Posts to files endpoint (begin timer)
  2. Server file endpoint calls process_file
  3. File processing take more then 30seconds
  4. Your request from the frontend timeout (unrelated to the owui server), due to some config from the above mentioned

Hi,
it seems like the timeout happens internally in open-webui during the file upload/embedding.
The embedding still continues and finishes after the file gets removed from the chat in my case.
Also the upload to s3 as well as my own vector storage works.
I am not using GCP or Heroku and the remote server isnt timeouting either.
Having the async upload like described in this issue would resolve that most likely.
There is no possibility to extend the timeout in open-webui afaik

<!-- gh-comment-id:3154305977 --> @kns-12 commented on GitHub (Aug 5, 2025): > > > > maybe? [#11345 (comment)](https://github.com/open-webui/open-webui/discussions/11345#discussioncomment-12423102) > > > > I don't know if you are using proxy to access, just a suggestion for check. (any console log? ) > > > > > > > > > Nope, I am not using any proxy to access it. > > > I described my situation here: [#15758](https://github.com/open-webui/open-webui/issues/15758) but it has been closed in favour of this current issue. > > > I am just getting a Gateway Timeout after exactly 30 seconds each time I try to upload a large file. > > > Concerning the Open WebUI logs, it just keeps embedding the document, after removing it from the chat due to the Gateway Timeout. > > > > > > Marked as duplicate but my understanding is there is actually a couple of separate issues here. To yours specifically, I don't not think the timeout is coming from the OWUI server or config. I have the exact same issues, 504 gateway timeout in the file uploads, when the embedding takes more than 1minute, the POST to files from the frontend times out. For me this timeout comes from my ALB idle timeout. If it is 30 seconds for you it is coming from some other gateway/api/proxy that you have. > > The proper issue I think is about why the POST request hangs, while the embedding is happening. The issue does not persist when the embedding is bypassed. > > I'm on mobile now but will take a proper look when I'm home this weekend. > > [@kns-12](https://github.com/kns-12) - Quick Look shows GCP and Heroku have some default timeouts of 30 seconds - here is my understanding of what's going on for you: > > 1. Frontend Posts to files endpoint (begin timer) > 2. Server file endpoint calls process_file > 3. File processing take more then 30seconds > 4. Your request from the frontend timeout (unrelated to the owui server), due to some config from the above mentioned Hi, it seems like the timeout happens internally in open-webui during the file upload/embedding. The embedding still continues and finishes after the file gets removed from the chat in my case. Also the upload to s3 as well as my own vector storage works. I am not using GCP or Heroku and the remote server isnt timeouting either. Having the async upload like described in this issue would resolve that most likely. There is no possibility to extend the timeout in open-webui afaik
GiteaMirror commented 2026-05-05 18:43:22 -05:00
Author
Owner
Copy Link

@rgaricano commented on GitHub (Aug 5, 2025):

openwebui env vars:
AIOHTTP_CLIENT_TIMEOUT (default 300)
AIOHTTP_CLIENT_TIMEOUT_TOOL_SERVER_DATA (default 10)
AIOHTTP_CLIENT_TIMEOUT_OPENAI_MODEL_LIST (default 10)

also I saw that is hardcoded in
b8da4a8cd8/backend/open_webui/main.py (L1695)

(maybe increase it or set as total=None or 0 for unlimited &| adding also sock_connect & sock_read times params? )

<!-- gh-comment-id:3154416050 --> @rgaricano commented on GitHub (Aug 5, 2025): openwebui env vars: AIOHTTP_CLIENT_TIMEOUT (default 300) AIOHTTP_CLIENT_TIMEOUT_TOOL_SERVER_DATA (default 10) AIOHTTP_CLIENT_TIMEOUT_OPENAI_MODEL_LIST (default 10) also I saw that is hardcoded in https://github.com/open-webui/open-webui/blob/b8da4a8cd8257d4846f3608e299618a0b4f185ed/backend/open_webui/main.py#L1695 (maybe increase it or set as total=None or 0 for unlimited &| adding also sock_connect & sock_read times params? )
GiteaMirror commented 2026-05-05 18:43:22 -05:00
Author
Owner
Copy Link

@kns-12 commented on GitHub (Aug 5, 2025):

openwebui env vars: AIOHTTP_CLIENT_TIMEOUT (default 300) AIOHTTP_CLIENT_TIMEOUT_TOOL_SERVER_DATA (default 10) AIOHTTP_CLIENT_TIMEOUT_OPENAI_MODEL_LIST (default 10)

also I saw that is hardcoded in

open-webui/backend/open_webui/main.py

Line 1695 in b8da4a8

timeout = aiohttp.ClientTimeout(total=1)
(maybe increase it or set as total=None or 0 for unlimited &| adding also sock_connect & sock_read times params? )

Setting the mentioned ENVs doesn't have any effect.
Think I will just wait for the refactoring. As a workaround splitting large files does work.

<!-- gh-comment-id:3154649949 --> @kns-12 commented on GitHub (Aug 5, 2025): > openwebui env vars: AIOHTTP_CLIENT_TIMEOUT (default 300) AIOHTTP_CLIENT_TIMEOUT_TOOL_SERVER_DATA (default 10) AIOHTTP_CLIENT_TIMEOUT_OPENAI_MODEL_LIST (default 10) > > also I saw that is hardcoded in > > [open-webui/backend/open_webui/main.py](https://github.com/open-webui/open-webui/blob/b8da4a8cd8257d4846f3608e299618a0b4f185ed/backend/open_webui/main.py#L1695) > > Line 1695 in [b8da4a8](/open-webui/open-webui/commit/b8da4a8cd8257d4846f3608e299618a0b4f185ed) > > timeout = aiohttp.ClientTimeout(total=1) > (maybe increase it or set as total=None or 0 for unlimited &| adding also sock_connect & sock_read times params? ) Setting the mentioned ENVs doesn't have any effect. Think I will just wait for the refactoring. As a workaround splitting large files does work.
GiteaMirror commented 2026-05-05 18:43:23 -05:00
Author
Owner
Copy Link

@decent-engineer-decent-datascientist commented on GitHub (Aug 11, 2025):

Hey friends, signing up to this thread.

<!-- gh-comment-id:3175700185 --> @decent-engineer-decent-datascientist commented on GitHub (Aug 11, 2025): Hey friends, signing up to this thread.
GiteaMirror commented 2026-05-05 18:43:24 -05:00
Author
Owner
Copy Link

@robbiekouwenberg commented on GitHub (Aug 13, 2025):

+1 for refactor. Also less hardcoded vars in general would be nice

<!-- gh-comment-id:3182482000 --> @robbiekouwenberg commented on GitHub (Aug 13, 2025): +1 for refactor. Also less hardcoded vars in general would be nice
GiteaMirror commented 2026-05-05 18:43:25 -05:00
Author
Owner
Copy Link

@tjbck commented on GitHub (Aug 19, 2025):

Addressed with 5e1f4fa0ff in dev.

<!-- gh-comment-id:3202146989 --> @tjbck commented on GitHub (Aug 19, 2025): Addressed with 5e1f4fa0ff75cec8a4569797ff3bdd118eb0e601 in dev.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
confirmed
confirmed issue
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#56108
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?