Skip to content

CH keeper-client doesn't connect to secure Keeper port 9281 #1858

@DimensionWieldr

Description

@DimensionWieldr

I checked the Altinity Stable Builds lifecycle table, and the Altinity Stable Build version I'm using is still supported.

Type of problem

Bug report - something's broken

Describe the situation

Trying to connect to Keeper's secure port using clickhouse keeper-client runs into a certificate loading error.

How to reproduce the behavior

  • altinity/clickhouse-server:25.3.8.30001.altinityfips
  • Make sure CH configs only expose secure Keeper port 9281, not 9181 (explicitly remove 9181 with an xml remove clause)
  • Try to connect to Keeper using clickhouse keeper-client

Expected behavior

I connect successfully and am able to run queries.

Logs, error messages, stacktraces, screenshots...

Poco::Exception. Code: 1000, e.code() = 0, SSL Exception: error:1000007d:SSL routines:OPENSSL_internal:CERTIFICATE_VERIFY_FAILED

Additional context

This might be an issue on more versions than just FIPS.

Metadata

Metadata

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions