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

[GH-ISSUE #1283] Does not load in browser after installation #803

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

Originally created by @vinaypri on GitHub (May 4, 2024).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/1283

How are you running AnythingLLM?

Not listed

What happened?

I have used the non docker installation of Anything LLM on my server. Completed the setup steps as per your documentation and started the server and collector. However when I browse to the address - http://128.199.28.108:3001/ it just keeps loading infinitely.

I have enabled Together AI model in the below steps in the .env file
LLM_PROVIDER='togetherai'
TOGETHER_AI_API_KEY=''
TOGETHER_AI_MODEL_PREF='01.AI/01-ai YI Chat(34B)'

The same key and model work fine in the desktop app. Please help.

Are there known steps to reproduce?

Server address given, you may try to load.

Originally created by @vinaypri on GitHub (May 4, 2024). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/1283 ### How are you running AnythingLLM? Not listed ### What happened? I have used the non docker installation of Anything LLM on my server. Completed the setup steps as per your documentation and started the server and collector. However when I browse to the address - http://128.199.28.108:3001/ it just keeps loading infinitely. I have enabled Together AI model in the below steps in the .env file LLM_PROVIDER='togetherai' TOGETHER_AI_API_KEY='<key-given-here>' TOGETHER_AI_MODEL_PREF='01.AI/01-ai YI Chat(34B)' The same key and model work fine in the desktop app. Please help. ### Are there known steps to reproduce? Server address given, you may try to load.
yindo added the possible bug label 2026-02-22 18:21:27 -05:00
yindo closed this issue 2026-02-22 18:21:27 -05:00
yindo commented 2026-02-22 18:21:27 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (May 4, 2024):

https://github.com/Mintplex-Labs/anything-llm/blob/master/BARE_METAL.md

Warning

This method of deployment is not supported by the core-team and is to be used as a reference for your deployment.
You are fully responsible for securing your deployment and data in this mode.
Any issues experienced from bare-metal or non-containerized deployments will be not answered or supported.

Im sorry, we really cannot aide in non-containarized deployments, there are simply far too many places someone could go wrong or configure something improperly.

Common areas people look over going this route:

  • Not compiling frontend and copying it to server/public
  • Setting for VITE_BASE_API not being /api in frontend/.env
  • No STORAGE_DIR in server/.env
@timothycarambat commented on GitHub (May 4, 2024): https://github.com/Mintplex-Labs/anything-llm/blob/master/BARE_METAL.md > [!WARNING] > This method of deployment is **not supported** by the core-team and is to be used as a reference for your deployment. > You are fully responsible for securing your deployment and data in this mode. > **Any issues** experienced from bare-metal or non-containerized deployments will be **not** answered or supported. Im sorry, we really cannot aide in non-containarized deployments, there are simply far too many places someone could go wrong or configure something improperly. Common areas people look over going this route: - Not compiling frontend and copying it to `server/public` - Setting for `VITE_BASE_API` not being `/api` in `frontend/.env` - No `STORAGE_DIR` in `server/.env`
yindo commented 2026-02-22 18:21:27 -05:00
Author
Owner
Copy Link
Copy Source

@vinaypri commented on GitHub (May 8, 2024):

Hi Timothy,

Thanks for the suggestions. The problem was indeed about not having /api in
frontend/.env. Incidentally this step is not mentioned in your
documentation at
https://github.com/Mintplex-Labs/anything-llm/blob/master/BARE_METAL.md

It would help in future, if you can add it.

Regards

On Sat, May 4, 2024 at 11:58 PM Timothy Carambat @.***>
wrote:

https://github.com/Mintplex-Labs/anything-llm/blob/master/BARE_METAL.md

Warning

This method of deployment is not supported by the core-team and is to
be used as a reference for your deployment.
You are fully responsible for securing your deployment and data in this
mode.
Any issues experienced from bare-metal or non-containerized deployments
will be not answered or supported.

Im sorry, we really cannot aide in non-containarized deployments, there
are simply far too many places someone could go wrong or configure
something improperly.

Common areas people look over going this route:

  • Not compiling frontend and copying it to server/public
  • Setting for VITE_BASE_API not being /api in frontend/.env
  • No STORAGE_DIR in server/.env

—
Reply to this email directly, view it on GitHub
https://github.com/Mintplex-Labs/anything-llm/issues/1283#issuecomment-2094339821,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APGQJCMUXAKMK5BDJL2AJMLZAUSD3AVCNFSM6AAAAABHG6H3WKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJUGMZTSOBSGE
.
You are receiving this because you authored the thread.Message ID:
@.***>

@vinaypri commented on GitHub (May 8, 2024): Hi Timothy, Thanks for the suggestions. The problem was indeed about not having /api in frontend/.env. Incidentally this step is not mentioned in your documentation at https://github.com/Mintplex-Labs/anything-llm/blob/master/BARE_METAL.md It would help in future, if you can add it. Regards On Sat, May 4, 2024 at 11:58 PM Timothy Carambat ***@***.***> wrote: > https://github.com/Mintplex-Labs/anything-llm/blob/master/BARE_METAL.md > > Warning > > This method of deployment is *not supported* by the core-team and is to > be used as a reference for your deployment. > You are fully responsible for securing your deployment and data in this > mode. > *Any issues* experienced from bare-metal or non-containerized deployments > will be *not* answered or supported. > > Im sorry, we really cannot aide in non-containarized deployments, there > are simply far too many places someone could go wrong or configure > something improperly. > > Common areas people look over going this route: > > - Not compiling frontend and copying it to server/public > - Setting for VITE_BASE_API not being /api in frontend/.env > - No STORAGE_DIR in server/.env > > — > Reply to this email directly, view it on GitHub > <https://github.com/Mintplex-Labs/anything-llm/issues/1283#issuecomment-2094339821>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/APGQJCMUXAKMK5BDJL2AJMLZAUSD3AVCNFSM6AAAAABHG6H3WKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJUGMZTSOBSGE> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >
yindo commented 2026-02-22 18:21:28 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (May 8, 2024):

👍
c0625c5cd6

@timothycarambat commented on GitHub (May 8, 2024): 👍 c0625c5cd625fbcb144d2f596edccc245f5d2a7c
yindo changed title from Does not load in browser after installation to [GH-ISSUE #1283] Does not load in browser after installation 2026-06-05 14:37:16 -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#803
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?