[Bug]: While creating a new brain in localhost instance of Quivr, I am getting error #2547
Comments
GSrinivasKishanLal
changed the title
|
The error you're encountering, "Internal Server Error" with a "CORS missing allow origin" message, suggests a CORS configuration issue in your Quivr backend. To resolve this, ensure your CORS settings allow requests from your frontend's origin. Here's how you can address the problem:
By following these steps and ensuring your CORS configuration includes the origin of your frontend application, you should be able to resolve the "Internal Server Error" related to CORS issues.
|
|
@dosu Thank you for your kind reply, but the issue is still existing with CORS issue occurring for also: |
|
Any solution for this also is required, kindly suggest |
|
To further address the CORS issue for For the persistent 500 Internal Server Error, diving deeper into the server logs is crucial. This error is a broad indication of server-side issues, which could range from problems in your application logic, issues with database connections or queries, to misconfigurations in your server environment. The exact nature of the error should be logged in more detail on your server, providing vital clues for troubleshooting. Ensure that your server and application configurations in If these steps do not resolve the issue, it would be helpful to share more detailed error messages or logs. This additional information can offer more specific insights into what might be causing the problem, enabling more targeted troubleshooting steps.
|
|
@dosu Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://localhost:5050/chat/b55ab619-9838-4d33-be80-1d80d7226f58/question/stream?brain_id=40ba47d7-51b2-4b2a-9247-89e29619efb0. (Reason: CORS request did not succeed). Status code: (null). Where the HTTP method used is : POST and I am facing this issue in the application. Receive "Type Error: Network Error when attempting to fetch resource." in the web page and "NS_ERROR_NET_PARTIAL_TRANSFER" Kindly request you to give a suggestion on how this issue could be fixed. |
|
To tackle the CORS issue you're facing with the
By following these steps, you should be closer to identifying and resolving the issue with the specific endpoint. If the problem persists, sharing more detailed information about the request and how the server handles it could offer further insights for diagnosis and resolution.
|
|
If the issue persists after trying the previously suggested steps, it might be beneficial to take a deeper look into a few more technical aspects and potential solutions:
Given the complexity of CORS and network-related issues, these steps aim to cover a broad spectrum of potential causes. If the problem remains unresolved, it might be helpful to isolate the issue further by creating a minimal reproducible example or consulting with a network specialist to delve deeper into the network error aspects.
|
|
@dosu and others, kindly suggest on a solution, this is the error I am getting before the "add_cors_middleware(app)" function is called in main.py file: backend-core | raise errors_.ConfigError(f'unable to infer type for attribute "{self.name}"') |
|
The error you're encountering, from pydantic import BaseModel
class MyModel(BaseModel):
api_key: str # Explicitly type-annotatedThis definition tells Pydantic that
|
|
@dosu, backend-core | ValueError: Error raised by inference endpoint: HTTPConnectionPool(host='localhost', port=11434): Max retries exceeded with url: /api/embeddings (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f14651a3990>: Failed to establish a new connection: [Errno 111] Connection refused')) backend-core | INFO: 172.19.0.1:36272 - "GET /knowledge?brain_id=40ba47d7-51b2-4b2a-9247-89e29619efb0 HTTP/1.1" 200 OK backend-core | INFO: 127.0.0.1:36282 - "GET /healthz HTTP/1.1" 200 OKAnd, how to skip open AI API Key and use local Ollama. Kindly suggest |
|
getting urlib3-connection- failure error @dosu, kindly suggest |
|
To address the
By following these steps, you should be able to switch to using a local Ollama model, bypassing the need for an OpenAI API Key and resolving the connection issues you've encountered.
|
|
@dosu, kindly suggest on where I shall find this "get_embeddings" function? |
|
The "get_embeddings" function you're looking for is typically found within the Quivr application's codebase, specifically in the
|
|
To address the "Network Error" you're encountering when changing the model for an existing brain in your application, consider the following targeted steps:
Ensure that "ollama-phi3:latest" is a valid model identifier and that the JWT token used in the Authorization header is valid and correctly formatted. Additionally, verify your local environment setup, particularly if using Docker, to ensure network bridging or port forwarding is correctly configured. These steps should help you diagnose and potentially resolve the network error you're facing. If the problem persists, providing more details about your setup and the steps leading to the error could offer further insights.
|
What happened?
Error occurred while creating a brain
Getting response:
Internal Server Error
kindly suggest on any solution to resolve
Relevant log output
Twitter / LinkedIn details
No response
The text was updated successfully, but these errors were encountered: