Error in UI when deploying edgedb with self hosted postgres and pg_bouncer #6657
shauryagoel
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have deployed Postgres db and edgedb in separate pods (in K8s). To connect to Postgres, I am using pg_bouncer to improve the handling of the connections. Hence, I specify the IP of pg_bouncer in the EDGEDB_SERVER_BACKEND_DSN environment variable when deploying the edgedb pod. I have also enabled the variable EDGEDB_SERVER_ADMIN_UI. However, I am unable to access the edgedb UI as I am getting an SSLV3_ALERT_CERTIFICATE_UNKNOWN error in the logs. If instead of using pg_bouncer's IP, I use the Postgres instance's IP, then, everything is working as expected and I am not getting any errors. Also, both approaches (using pg_bouncer's IP and Postgres's IP) work fine when using the edgedb client and CLI. Has anybody faced a similar issue?
Beta Was this translation helpful? Give feedback.
All reactions