Cloud SQL PostgreSQL: Hostname/IP does not match certificate's altnames #1735

Activity

1. joshxyzhimself commented on Apr 22, 2020

   

   joshxyzhimself

   on Apr 22, 2020

   Author

   More actions

   Also tried creating a client cert then using the ca, cert, and key as parameters for NodeJS TLS createSecureContext function, this shit sucks
2. joshxyzhimself commented on Apr 22, 2020

   

   joshxyzhimself

   on Apr 22, 2020

   Author

   More actions

   Confirmed at db-migrate/node-db-migrate#592
3. fhinkel

   added

   api: cloudsqlIssues related to the Cloud SQL for MySQL API.Issues related to the Cloud SQL for MySQL API.

   type: questionRequest for information or clarification. Not an issue.Request for information or clarification. Not an issue.

   on Apr 22, 2020
4. fhinkel commented on Apr 28, 2020

   

   fhinkel

   on Apr 28, 2020

   Contributor

   More actions

   @kurtisvg Can you have a look or re-assign please. Thanks
5. fhinkel

   assigned

   kurtisvg

   on Apr 28, 2020
6. kurtisvg commented on Apr 28, 2020

   

   kurtisvg

   on Apr 28, 2020

   Contributor

   More actions

   Hi @joshxyzhimself,

   From a quick look at the other issue it looks like you were able to resolve the problem yourself using these pages:

   • https://cloud.google.com/sql/docs/postgres/authorize-ssl
   • https://cloud.google.com/sql/docs/postgres/connect-admin-proxy

   In the future, please note that this repo (and the issues on it) are are only used for tracking problems with the samples in it. You will likely be able to get faster or more specific help using the following resources:

   • Asking a question with the cloudsql tag on StackOverflow
   • Filing an issue in the Cloud SQL issue tracker
   • For proxy related issues, opening an issue on the Cloud SQL proxy github repo.
7. kurtisvg

   closed this as completedon Apr 28, 2020