GitHub user lhotari edited a comment on the discussion: Issue with TLS after upgrading from 2.8.x
The Pulsar TLS docs for 3.0.x are at https://pulsar.apache.org/docs/3.0.x/security-tls-transport/. The error message hints that `tlsTrustCertsFilePath` isn't properly configured. For broker clients, it's `brokerClientTrustCertsFilePath`. The config is slightly different if you happen to use `tlsEnabledWithKeyStore`. > I do have a certificate on the proxy that I purchased from a registrar, so > it's not the normal self-signed certificate. This worked just fine in > previous versions of Pulsar. Any suggestions on what might work to fix this? Which Helm chart version are you using? Apache Pulsar Helm chart? There's an open issue to add support for pre-existing certificates: https://github.com/apache/pulsar-helm-chart/issues/527. Regarding information security, please notice the ["Important Security Disclaimer for Helm Chart Usage"](https://github.com/apache/pulsar-helm-chart?tab=readme-ov-file#important-security-disclaimer-for-helm-chart-usage) on the Apache Pulsar Helm chart, as well as the related [Pulsar Proxy security considerations](https://github.com/apache/pulsar-helm-chart?tab=readme-ov-file#pulsar-proxy-security-considerations). GitHub link: https://github.com/apache/pulsar/discussions/23408#discussioncomment-10884412 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
