infiniflow / infiniflow/ragflow

[Question]: RAG server not working stable

Open
#9,237 8 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

🐞 bug 🙋‍♀️ question
Dominant language
Go
Stars
91k
Forks
10.8k
Avg merge
1d 14h
Merged PRs (30d)
705

Description

### Self Checks

- [x] I have searched for existing issues [search for existing issues](https://github.com/infiniflow/ragflow/issues), including closed ones.
- [x] I confirm that I am using English to submit this report ([Language Policy](https://github.com/infiniflow/ragflow/issues/5910)).
- [x] Non-english title submitions will be closed directly ( 非英文标题的提交将会被直接关闭 ) ([Language Policy](https://github.com/infiniflow/ragflow/issues/5910)).
- [x] Please do not modify this template :) and fill in all the required fields.

### Describe your problem

i run ragserver , and hold basic config of **launch_backend_service.sh** but after 2 -3 days, BE not received any request from any client (FE ragflow, postman, curl, ..) help me fix that

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing launch_backend_service.sh and the existing issue comments, then reproduce the backend becoming unresponsive after 2–3 days using the reported client types: the RAGFlow frontend, Postman, and curl. Done means identifying the cause and demonstrating that the backend continues receiving requests after the reported interval.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, shell
Domain
api, backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.