[Question]: /admin shows 404

[DmSilkin]

Self Checks

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

Describe your problem

Hey, i've upgraded ragflow to 0.22.1 and would like to login to admin panel. But ragflow still shows 404 response. I am running this in kubernetes with image infiniflow/ragflow:v0.22.1:

Admin server is also running on the port 9381. Nginx config is equal to the example.

How should I access to the admin panel?

[dosubot[bot]]

Hi @DmSilkin! I'm Dosu and I’m helping the ragflow team.

The admin panel API is served at /api/v1/admin on port 9381, not at /admin directly. To access the admin panel, use the main RagFlow web interface (usually via the host port mapped to Nginx, typically port 80), then navigate to /admin in your browser—do not try to access port 9381 directly, as it only serves API endpoints and will return a 404 if you visit /admin there reference.

Make sure the admin server is enabled with the --enable-adminserver flag or by setting ENABLE_ADMIN_SERVER=1 in your environment, and confirm that port 9381 is exposed and healthy in your Kubernetes setup reference. Your Nginx config should proxy /api/v1/admin requests to http://localhost:9381 reference.

If you still see a 404, check that your frontend build includes the Admin UI routes and that all containers/pods are running and healthy. The default admin credentials are [email protected] and password admin reference.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

   

[DmSilkin]

how do i check build if i use ragflow:0.22.0 from dockerhub? Does it include admin webui?

[dosubot[bot]]

Yes, the ragflow:0.22.0 Docker image does include the admin web UI. The frontend (including the admin UI) is built and copied into the image at /ragflow/web/dist, which is served by Nginx. The admin backend runs as a separate service on port 9381, but it’s disabled by default—you need to start the container with the --enable-adminserver flag or set ENABLE_ADMIN_SERVER=1 in your environment for the admin UI to work Dockerfile reference entrypoint script.

To check if the admin UI is present and running:

• Make sure you enabled the admin server as described above.
• Access /admin via the main RagFlow web interface (usually port 80).
• If you see a login page, the admin UI is included and working. If you get a 404 or 502, check that the admin backend process is running and listening on port 9381, and review container logs for errors troubleshooting guide.
• You can verify the version inside the container by running cat /ragflow/VERSION version check.

Let me know if you need help with specific troubleshooting steps!

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

   

[Lynn-Inf]

The image ragflow:v0.22.0 and v0.22.1 have admin web UI. Make sure you start the container with the --enable-adminserver flag or set ENABLE_ADMIN_SERVER=1 like dosubot said, and docker exec -it <ragflow server container name> /bin/bash, then see logs folder to find admin_server.log. No admin_server.log means no admin server has been started.

[aaronchen2k]

@dosu after enable admin server, http://localhost:9381/ return a 404, why?

[dosubot[bot]]

This is expected: the admin server on port 9381 only serves API endpoints under /api/v1/admin, not a web UI or any content at the root path. So if you visit http://localhost:9381/ directly, you'll always get a 404 error by design (source, code).

To use the admin web UI, go to the main RagFlow web interface (usually via Nginx on port 80 or 8080) and navigate to /admin. The web UI will proxy API calls to port 9381 internally. If the admin server is enabled and healthy, this is the correct and only supported way to access the admin panel.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

   

[aaronchen2k]

@dosu Got an error when using admin cli as below:

admin> LIST USERS Error: Parse error: Unexpected token Token('$END', '') at line 1, column 6. Expected one of: * SEMICOLON