You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
we are evaluating the admin-console for productive use and need to connect from external (with a valid CN in the certificate) but also need to go cluster internal via service where the hostname does not match the certificate.
configured:
config:
server_config:
ssl:
hostname_validation: falseverify_certs: false # also tried optionally
Still getting the error when connecting internal:
[HPM] Error occurred while proxying request pulsar-admin-console-prod01-***/admin/v2/tenants to https://prod01-broker.prod01-***.svc.cluster.local:8443/ [ERR_TLS_CERT_ALTNAME_INVALID] (https://nodejs.org/api/errors.html#errors_common_system_errors)
Should not the hostname_validation: false setting avoid exactly that issue?
PS: Also set verify_certs: false but also did not help.
The text was updated successfully, but these errors were encountered:
MarkusNeuron
changed the title
Option server_config.ssl.hostname_validation = false seems not to work
Option server_config.ssl.hostname_validation: false seems not to work
Sep 20, 2023
Hi,
we are evaluating the admin-console for productive use and need to connect from external (with a valid CN in the certificate) but also need to go cluster internal via service where the hostname does not match the certificate.
configured:
Still getting the error when connecting internal:
Should not the
hostname_validation: false
setting avoid exactly that issue?PS: Also set
verify_certs: false
but also did not help.The text was updated successfully, but these errors were encountered: