dosubot[bot]
commented
6 months ago It looks like the issue you're encountering with the 403 Forbidden responses is related to server-side authentication or configuration problems. Here's a more focused approach to troubleshoot and potentially resolve the issue:
-
Server-Side Authentication Logic: Verify that your backend correctly handles authentication for local requests. This includes checking CORS settings and other security configurations that might block local requests.
-
API Endpoint Accessibility: Ensure that any external APIs or backend services your login functionality depends on are accessible from your local setup. This might involve checking API keys or domain restrictions.
-
Local Environment Configuration: Double-check your local environment configuration, including environment variables and any necessary settings to ensure they match what's required for successful communication with backend services.
-
Debug Network Requests: Use browser developer tools to inspect the failed network requests. Pay close attention to request headers and payloads to identify potential misconfigurations.
-
Frontend Configuration: Review your frontend code for any environment-specific settings that might affect the login process. Ensure that API endpoints and authentication configurations are correctly set for local development.
-
Backend or API Documentation: If using third-party APIs or backend services, consult their documentation for guidance on setting up for local development, including any development-specific keys or settings.
-
Middleware or Proxy Configuration: If your setup involves middleware or proxies, ensure they are correctly configured to allow requests to pass through to your application without being blocked.
For a more targeted investigation, review the server-side logic for endpoints returning 403 responses, ensure your .env file matches the required configurations as outlined in .env.example, and check for any potential misconfigurations in middleware or proxies that could lead to these responses.
If these steps do not resolve the issue, providing more details about your setup and any additional error messages could help in offering further assistance.
#### Details
**Sources** - [Localhost:3000 doesn't load the app](https://github.com/QuivrHQ/quivr/issues/281) - [frontend/app/(auth)/login/page.tsx](https://github.com/QuivrHQ/quivr/blob/main/frontend/app/(auth)/login/page.tsx) - [backend/modules/user/controller/user_controller.py](https://github.com/QuivrHQ/quivr/blob/main/backend/modules/user/controller/user_controller.py) - [docs/configuring/environment-variables.mdx](https://github.com/QuivrHQ/quivr/blob/main/docs/configuring/environment-variables.mdx) - [.env.example](https://github.com/QuivrHQ/quivr/blob/main/.env.example) - [cms/quivr/config/middlewares.js](https://github.com/QuivrHQ/quivr/blob/main/cms/quivr/config/middlewares.js) - [frontend/next.config.js](https://github.com/QuivrHQ/quivr/blob/main/frontend/next.config.js) - [backend/middlewares/auth/auth_bearer.py](https://github.com/QuivrHQ/quivr/blob/main/backend/middlewares/auth/auth_bearer.py) - [frontend/lib/api/user/user.ts](https://github.com/QuivrHQ/quivr/blob/main/frontend/lib/api/user/user.ts) - [frontend/lib/api/user/useUserApi.ts](https://github.com/QuivrHQ/quivr/blob/main/frontend/lib/api/user/useUserApi.ts) - [docs/install.mdx](https://github.com/QuivrHQ/quivr/blob/main/docs/install.mdx) - [README.md](https://github.com/QuivrHQ/quivr/blob/main/README.md)**About Dosu** 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.
To continue the conversation, mention @dosu.
powderblock
sgwaterwoods
dazeb
opendeluxe
4ku
BestLemoon
StanGirard
sweatybridge
What happened?
I setup the full stack locally on my macbook as described in the README. All docker containers are running well without any issues. However, when opening
http://localhost:3000/loginin a webbrowser, it only shows the logo and the text "Talk to Quivr Unpaid users have access to a free and limited demo of Quivr"According to the log, it seems to call some /user endpoints which respond with 403. I would expect that the login-form would be rendered instead first.
Relevant log output
Twitter / LinkedIn details
No response