mirror of
https://github.com/open-webui/open-webui.git
synced 2026-05-07 11:28:35 -05:00
no files upload issues? #4082
Reference in New Issue
Block a user
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?
Originally created by @Fahad-alkamli on GitHub (Feb 23, 2025).
Bug Report
Important Notes
Before submitting a bug report: Please check the Issues or Discussions section to see if a similar issue or feature request has already been posted. It's likely we're already tracking it! If you’re unsure, start a discussion post first. This will help us efficiently focus on improving the project.
Collaborate respectfully: We value a constructive attitude, so please be mindful of your communication. If negativity is part of your approach, our capacity to engage may be limited. We’re here to help if you’re open to learning and communicating positively. Remember, Open WebUI is a volunteer-driven project managed by a single maintainer and supported by contributors who also have full-time jobs. We appreciate your time and ask that you respect ours.
Contributing: If you encounter an issue, we highly encourage you to submit a pull request or fork the project. We actively work to prevent contributor burnout to maintain the quality and continuity of Open WebUI.
Bug reproducibility: If a bug cannot be reproduced with a
:mainor:devDocker setup, or a pip install with Python 3.11, it may require additional help from the community. In such cases, we will move it to the "issues" Discussions section due to our limited resources. We encourage the community to assist with these issues. Remember, it’s not that the issue doesn’t exist; we need your help!Note: Please remove the notes above when submitting your post. Thank you for your understanding and support!
Installation Method
[Describe the method you used to install the project, e.g., git clone, Docker, pip, etc.]
docker, both ollama and open-webui in the same docker
Environment
0.5.7
-Windows 10
Confirmation:
Expected Behavior:
I have uploaded the files and the model seems to think and read each file but all of sudden it seems like it can't see the files and stop processing and show an error? even though in the thinking process I can see clearly that it actually started working on the documents.
[Describe what you expected to happen.]
Summarizes the files
Actual Behavior:
Unfortunately, I don't have access to your uploaded research papers or any files you've mentioned. My system doesn't track or store user-uploaded content beyond what is explicitly provided in the conversation. If you haven't uploaded any papers yet, feel free to share them, and I'll be happy to help summarize them for you!
[Describe what actually happened.]
Description
Bug Summary:
[Provide a brief but clear summary of the bug]
model can't see the uploaded files after processing for a while.
Reproduction Details
upload 3 files and ask it to summarize it using this prompt:
Please provide a comprehensive summary of only the research papers I have uploaded, with each paper summarized in its own paragraph. For each paper, highlight the main findings, methodology, dataset details, and key results. Write in a natural, human-like tone that is engaging and easy to understand. Additionally, include a table summarizing only the uploaded papers with the following columns: Reference (citation/title), Dataset (description/size/source), Learning Model (algorithm/architecture), Advantages (strengths of the approach), Methodology (key techniques), Disadvantages (limitations). Important: Exclude any papers not explicitly uploaded by me. If no papers are detected, state this clearly and avoid generating placeholder examples.
Steps to Reproduce:
[Outline the steps to reproduce the bug. Be as detailed as possible.]
Logs and Screenshots
Browser Console Logs:
[Include relevant browser console logs, if applicable]
Docker Container Logs:
[Include relevant Docker container logs, if applicable]
Screenshots/Screen Recordings (if applicable):
[Attach any relevant screenshots to help illustrate the issue]
Additional Information
[Include any additional details that may help in understanding and reproducing the issue. This could include specific configurations, error messages, or anything else relevant to the bug.]
Note
If the bug report is incomplete or does not follow the provided instructions, it may not be addressed. Please ensure that you have followed the steps outlined in the README.md and troubleshooting.md documents, and provide all necessary information for us to reproduce and address the issue. Thank you!