Mintplex-Labs/anything-llm
1
0
Fork 0
mirror of https://github.com/Mintplex-Labs/anything-llm.git synced 2026-07-19 22:23:50 -04:00
Code Issues 328 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #4656] [BUG]: Blank homePage #2954

New Issue
Closed
opened 2026-02-22 18:32:00 -05:00 by yindo · 6 comments
yindo commented 2026-02-22 18:32:00 -05:00
Owner
Copy Link
Copy Source

Originally created by @ylxiang2018 on GitHub (Nov 17, 2025).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/4656

How are you running AnythingLLM?

Local development

What happened?

when I start the application using command "npm run dev"，the homepage is blank. On the other hand, I can access the onboarding page normally, but after creating the workspace, it redirects to a blank homepage.

Are there known steps to reproduce?

No response

Originally created by @ylxiang2018 on GitHub (Nov 17, 2025). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/4656 ### How are you running AnythingLLM? Local development ### What happened? when I start the application using command "npm run dev"，the homepage is blank. On the other hand, I can access the onboarding page normally, but after creating the workspace, it redirects to a blank homepage. ### Are there known steps to reproduce? _No response_
yindo added the possible bug label 2026-02-22 18:32:00 -05:00
yindo closed this issue 2026-02-22 18:32:00 -05:00
yindo commented 2026-02-22 18:32:01 -05:00
Author
Owner
Copy Link
Copy Source

@ylxiang2018 commented on GitHub (Nov 17, 2025):

The code is the latest version. Why is this issue occurring, and what's the solution?

@ylxiang2018 commented on GitHub (Nov 17, 2025): The code is the latest version. Why is this issue occurring, and what's the solution?
yindo commented 2026-02-22 18:32:01 -05:00
Author
Owner
Copy Link
Copy Source

@angelplusultra commented on GitHub (Nov 18, 2025):

Please share a screen recording of this behavior so we can further assist you.

@angelplusultra commented on GitHub (Nov 18, 2025): Please share a screen recording of this behavior so we can further assist you.
yindo commented 2026-02-22 18:32:01 -05:00
Author
Owner
Copy Link
Copy Source

@ylxiang2018 commented on GitHub (Nov 19, 2025):

Please share a screen recording of this behavior so we can further assist you.

@angelplusultra here is the screen recording:
https://github.com/user-attachments/assets/fbdbfebb-3c1f-48a5-9bfa-987ed2dac803

@ylxiang2018 commented on GitHub (Nov 19, 2025): > Please share a screen recording of this behavior so we can further assist you. @angelplusultra here is the screen recording: https://github.com/user-attachments/assets/fbdbfebb-3c1f-48a5-9bfa-987ed2dac803
yindo commented 2026-02-22 18:32:01 -05:00
Author
Owner
Copy Link
Copy Source

@angelplusultra commented on GitHub (Nov 19, 2025):

Did you run yarn setupat the root level and fill out required environment variables in server/.env.development?

@angelplusultra commented on GitHub (Nov 19, 2025): Did you run `yarn setup`at the root level and fill out required environment variables in `server/.env.development`?
yindo commented 2026-02-22 18:32:01 -05:00
Author
Owner
Copy Link
Copy Source

@ylxiang2018 commented on GitHub (Nov 19, 2025):

Did you run yarn setupat the root level and fill out required environment variables in server/.env.development?

Yes I did

@ylxiang2018 commented on GitHub (Nov 19, 2025): > Did you run `yarn setup`at the root level and fill out required environment variables in `server/.env.development`? Yes I did
yindo commented 2026-02-22 18:32:01 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Nov 20, 2025):

This is not a bug since it is not replicable and is instead an issue with your specific setup.
I notice you are on Windows, and as such - a lot of our commands (like yarn setup wont run fully!)

So just to go over each step:

  • yarn setup -> installs all deps + creates an .env in server and frontend
# frontend/.env
VITE_API_BASE='http://localhost:3001/api' # Use this URL when developing locally
# VITE_API_BASE='/api' # Use this URL deploying on non-localhost address OR in docker.

# server/.env

## MUST HAVE
SERVER_PORT=3001
JWT_SECRET="my-random-string-for-seeding"
SIG_KEY='password'
SIG_SALT='salt'
DATABASE_URL="file:../storage/anythingllm.db"

## Then at least once provider. In dev mode we only read from this file on start and hot-reloading of server will not reload the env if you change it post-startup

LLM_PROVIDER='ollama'
OLLAMA_BASE_PATH='http://127.0.0.1:11434'
OLLAMA_MODEL_PREF='qwen3:1.7b'

EMBEDDING_ENGINE='native'
VECTOR_DB="lancedb"

Now you can run yarn dev:server and yarn dev:frontend and yarn dev:collector from console and be able to load each service independently.

My guess is your frontend .env is incorrect. Otherwise just open up Chrome devtools and the error will be in there and it should be obvious what the root cause is here.

@timothycarambat commented on GitHub (Nov 20, 2025): This is not a bug since it is not replicable and is instead an issue with your specific setup. I notice you are on Windows, and as such - a lot of our commands (like yarn setup **wont run fully**!) So just to go over each step: - `yarn setup` -> installs all deps + creates an `.env` in `server` and `frontend` ``` # frontend/.env VITE_API_BASE='http://localhost:3001/api' # Use this URL when developing locally # VITE_API_BASE='/api' # Use this URL deploying on non-localhost address OR in docker. ``` ``` # server/.env ## MUST HAVE SERVER_PORT=3001 JWT_SECRET="my-random-string-for-seeding" SIG_KEY='password' SIG_SALT='salt' DATABASE_URL="file:../storage/anythingllm.db" ## Then at least once provider. In dev mode we only read from this file on start and hot-reloading of server will not reload the env if you change it post-startup LLM_PROVIDER='ollama' OLLAMA_BASE_PATH='http://127.0.0.1:11434' OLLAMA_MODEL_PREF='qwen3:1.7b' EMBEDDING_ENGINE='native' VECTOR_DB="lancedb" ``` Now you can run `yarn dev:server` and `yarn dev:frontend` and `yarn dev:collector` from console and be able to load each service independently. My guess is your frontend .env is incorrect. Otherwise just open up Chrome devtools and the error will be in there and it should be obvious what the root cause is here.
yindo changed title from [BUG]: Blank homePage to [GH-ISSUE #4656] [BUG]: Blank homePage 2026-06-05 14:49:28 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Desktop
Docker
Integration Request
Integration Request
OS: Linux
OS: Mobile
OS: Windows
UI/UX
blocked
bug
bug
core-team-only
documentation
duplicate
embed-widget
enhancement
feature request
github_actions
good first issue
investigating
needs info / can't replicate
possible bug
pull-request
Mirrored from GitHub Pull Request
 question
stage: specifications
wontfix
No Label possible bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anything-llm#2954
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?