Closed scebll closed 7 months ago
I had the same issue with my instance (running container on unraid with postgresql15) and I switched my network type from bridge to host to stop the infinite ECONNREFUSED errors. It sounds like a network configuration issue with your database and not due to the update. Just a guess, hope that is helpful!
So this error is still occurring for me, I see this is possibly being address in #11911, but still no fix otherwise.
Greetings!
We have recently upgraded from version 3.1.9 to version 3.3.9 and since the upgrade we are seeing many bugs in the console that are flooding the service.
The errors look like this:
Apparently it appears to be connecting to a database on localhost
(::1)
when we are using an external postgresql outside of even the docker service where it is running.Our environment variables look something like this.
Could it be that some change has been made that I missed in the changelog and is producing this error?
There's not much detail either and even increasing the debug level doesn't show any errors other than these lines.