-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Redis Connection Error: ECONNREFUSED at 127.0.0.1:6379 Causing Service Failure #8269
Comments
Hey @KazeroG - we don't officially maintain the Render.yaml but a pull request would be most welcome! It seems it's missing a redis in Render.yaml https://docs.render.com/redis |
I am having the same issue with the docker compose version from the docs. I have checked that I can connect to the redis service from the host computer. And both containers are in the same docker network |
Yes that's the issue, you're looking at the .env/documentation for main, while the docker version is still the old one :-/. |
Ahhh, alright. So waiting a bit and it should all sync up with the docs |
Yes it should! Sorry |
I've got this issue. Not sure from the discussion what the fix is; wait for an update to the docker compose? |
@JTCorrin use the .env.example variable from the latest published version and not the one from the main branch, (so this one https://github.com/twentyhq/twenty/blob/v0.31.3/packages/twenty-server/.env.example) |
Damn took me 6 hours till found this hahaha |
Bug Description
When running the application, a connection error occurs with Redis, causing the service to exit. This issue happens because the application cannot connect to 127.0.0.1:6379, resulting in an ECONNREFUSED error in the logs.
Expected behavior
The application should successfully connect to Redis at 127.0.0.1:6379, or an alternative Redis instance if configured, without raising connection errors. The application should start and run as expected without interruption.
Technical inputs
other info
The text was updated successfully, but these errors were encountered: