Skip to content
This repository was archived by the owner on Aug 22, 2024. It is now read-only.
This repository was archived by the owner on Aug 22, 2024. It is now read-only.

Unable to connect to PG using SSL #54

@dkadetov

Description

@dkadetov

Describe the bug
I seem to have a similar problem when trying to use verify-full SSL mode

Steps to reproduce
Set up a connection to Postgres using verify-full sslmode and a root certificate

?sslmode=verify-full&sslrootcert=/psql-root.crt

Expected behavior
Connection successfully established

pgSCV startup options

PGSCV_LISTEN_ADDRESS: 0.0.0.0:9890
PGSCV_AUTOUPDATE: off
PGSCV_NO_TRACK_MODE: true
PGSCV_DISABLE_COLLECTORS: system,postgres/logs,postgres/storage
POSTGRES_DSN: postgresql://XXX:XXX@XXX.postgres.database.azure.com:5432/postgres?sslmode=verify-full&sslrootcert=/psql-root.crt

Errors and Logs
{"level":"warn","service":"pgscv","time":"2023-05-10T06:29:33Z","message":"failed to close database connection: tls: failed to send closeNotify alert (but connection was closed anyway): write tcp xx.x.x.xx:51086->xx.xx.xxx.xxx:5432: write: broken pipe; ignore"}

Environment:

  • Used Container: Alpine Linux v3.13.11 lesovsky/pgscv:v0.8.0-beta.6
  • pgSCV Version: pgscv v0.8.0-beta.6 3650072-HEAD
  • PostgreSQL Version: 11.17
  • PostgreSQL Azure DaaS

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions