Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Can nor create any brain after installed the latest version #1455

Closed
BabaSarf opened this issue Oct 22, 2023 · 5 comments
Closed

[Bug]: Can nor create any brain after installed the latest version #1455

BabaSarf opened this issue Oct 22, 2023 · 5 comments
Labels
area: backend Related to backend functionality or under the /backend directory bug Something isn't working Stale

Comments

@BabaSarf
Copy link

What happened?

I have installed Quivr on VPS with the domain name. I can create a user and log in but to start I need to create a brain the hourglass turns for a minit or so then stop without creating any brain with no error on the docker terminal

Relevant log output

No response

Twitter / LinkedIn details

No response

@BabaSarf BabaSarf added the bug Something isn't working label Oct 22, 2023
@dosubot dosubot bot added the area: backend Related to backend functionality or under the /backend directory label Oct 22, 2023
@dosubot
Copy link

dosubot bot commented Oct 22, 2023

🤖

Hello,

Thank you for reaching out and I'm sorry to hear that you're having trouble creating a brain in Quivr.

Based on similar issues that have been resolved in the past, there are a few potential solutions that you could try:

  1. Update your frontend .env file to use your local IP. For example, change NEXT_PUBLIC_BACKEND_URL=localhost:5050 to NEXT_PUBLIC_BACKEND_URL=http://192.168.1.15:5050. Also, make sure to open port 5050 in your firewall.

  2. If you're setting up Quivr for the first time, follow these steps:

    • Clone the Quivr repository
    • Copy env.example to .env for both the frontend and backend
    • Populate the Supabase details in both files
    • Run docker compose up in VSCode
    • Once the container is running, copy the two tables mentioned in this issue and run them as queries in Supabase
    • Refresh localhost:3000
    • You should see "Default brain" in the dropdown and be able to create a new brain
  3. If you're using Windows, the issue might be due to the file start.sh being saved to git with Windows characters. You can fix this by running the command dos2unix backend/core/scripts/start.sh and restarting the docker compose.

You can find more details about these solutions in the following issues: [Bug]: , [Issue] Error Creating New Brain, [Issue] Error creating brain.

In the latest version of Quivr, changes were made to the BrainConfig type, which could potentially affect the brain creation process. You can find more details about these changes in the frontend/lib/types/brainConfig.ts and backend/models/databases/supabase/brains.py files.

Unfortunately, I couldn't find specific system requirements for running Quivr in the repository. However, if you could provide more details about your VPS (like the operating system, CPU, RAM, etc.), it might help in diagnosing the issue.

I hope this helps! If you have any other questions or if the issue persists, please let me know.

Best,

Sources


This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.

Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.

If you want to continue the conversation, start your reply with @dosu-bot.

@BabaSarf
Copy link
Author

None of the above suggestions fixed the problem I am facing

@StanGirard
Copy link
Collaborator

Please give more informations. Logs required to help debug :)

@BabaSarf
Copy link
Author

No docker logs at all related to the error. Everything fine on the terminal but I will load the logs anyway just incase I am missing something .

Copy link
Contributor

Thanks for your contributions, we'll be closing this issue as it has gone stale. Feel free to reopen if you'd like to continue the discussion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: backend Related to backend functionality or under the /backend directory bug Something isn't working Stale
Projects
None yet
Development

No branches or pull requests

2 participants