Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ERROR: Error opening connection Hostname/IP does not match certificate's #746

Open
1 task
niraj8241 opened this issue Dec 16, 2020 · 1 comment
Open
1 task
Labels
pg PostgreSQL driver

Comments

@niraj8241
Copy link

Describe the bug
Trying to setup a Redshift Connection using a AWS Privatelink connection. The Privatelink URL is a completely separate URL than Redshift hostname. But I can connect to Redshift using standard SQL Client using JDBC/ODBC. When I try to use this privatelink URL in SQLTools. I get the certificate mismatch error. I tried adding "rejectUnauthorized": false but that doesn't help.

To Reproduce
Steps to reproduce the behavior:

  1. Go to 'Connect to AWS Redshift using a PrivateLink URL'

Expected behavior
Should work by ignoring the hostname certificate warning.

Desktop (please complete the following information):

  • SQLTools Version [0.23.0]
  • VSCode Version: [1.5.1]
  • OS: [Windows]
  • Driver:
    • PostgreSQL/Redshift -- v0.2.0
@leomatter
Copy link

leomatter commented Nov 16, 2021

i have the same connecting with ssl to a GCP postgres server
Error opening connection Hostname/IP does not match certificate's altnames: Host: localhost. is not cert's CN: hayry-332210:hayrydb
connecting with psql or knex works..

i know it seems unrelated, but I think there could be a more general issue with ssl

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pg PostgreSQL driver
Projects
None yet
Development

No branches or pull requests

3 participants