Closed runningcd closed 1 month ago
Make sure to change the env variable specified in https://docs.quivr.app/deployment/digital_ocean part 9 ;)
Hey there, @runningcd! 👋 I'm Dosu, a friendly bot here to assist you while we wait for a human maintainer to join. Whether it's squashing bugs, answering questions, or helping you contribute, I've got your back. Let's take a peek at your issue, shall we? I'll have a full answer for you shortly! 🤖
It should be 192.168.0.18 in your FRONTEND URL env variable
To address the issue with JS and CSS resources not loading, consider the following steps:
Check for Browser Extensions: Disable any extensions that might block resources, or try accessing the site in incognito mode or a different browser.
Server CORS Policy: Ensure your backend service includes CORS headers to allow resources from the frontend service. For FastAPI, use CORSMiddleware
to add CORS headers, specifying your frontend URL in allow_origins
.
Environment Variable: Confirm the NEXT_PUBLIC_FRONTEND_URL
environment variable is correctly set to your frontend's URL in the .env
file or directly in the docker-compose.yml
under the frontend
service.
Redis Memory Overcommit Warning: This warning suggests the host system may not have enough memory for Redis. Consider increasing your system's memory or configuring Redis to use less memory.
Celery Worker Running as Superuser: Running Celery with superuser privileges is not recommended. Create a dedicated user for running the Celery worker to mitigate potential security risks.
LangChainDeprecationWarnings: Update your code to replace deprecated LangChain library features with their latest versions.
Flower Inspection Issues: Check Flower's configuration and dashboard to ensure it's correctly monitoring Celery workers.
Celery Deprecation Warning: Update your code according to the Celery documentation to address features that will be removed in future versions.
By following these steps, you should be able to resolve the loading issues with your JS and CSS resources.
To continue the conversation, mention @dosu.
Make sure to change the env variable specified in https://docs.quivr.app/deployment/digital_ocean part 9 ;)
@StanGirard It works. Thank you for your help.
What happened?
I'm deploying on a remote server, and http://ip:3000 accessing after docker compose starts, neither js nor css resources can be loaded, like http://ip:3000/_next/static/css/59ffadf4069e4968.css![error](https://github.com/QuivrHQ/quivr/assets/45549748/076307fe-76ff-4a09-940c-4d8624556dfa)
docker compose logs
Relevant log output
No response
Twitter / LinkedIn details
No response