GithubHelp home page GithubHelp logo

Comments (8)

4dex avatar 4dex commented on July 21, 2024 1

In case anyone else encounters this issue again, I came across it when using an older version of the cloud_sql_proxy image. Had to update the image before the proxy would connect to my cloud sql instances.

Updated from image: gcr.io/cloudsql-docker/gce-proxy:1.11 to image: gcr.io/cloudsql-docker/gce-proxy:1.33.2 and the x509: certificate is valid for project-name:name-db, not project-name:name-db-whatever issue went away.

from cloud-sql-proxy.

Carrotman42 avatar Carrotman42 commented on July 21, 2024

Interesting, I'm wondering whether something is messed up on the backend. Can you email your project name and instances to [email protected] and I can help debug the issue from there?

Some debugging we can do in public, though: how are your staging/production databases set up? Is one created from a backup of another or something?

from cloud-sql-proxy.

Jakedavies avatar Jakedavies commented on July 21, 2024

The staging/production databases are essentially the exact same, and there is a nightly cron that takes the backup from the production and restores it to the staging database.

from cloud-sql-proxy.

Carrotman42 avatar Carrotman42 commented on July 21, 2024

To follow up, the workaround here was to reset the SSL configuration of the instance. I'm currently investigating the root cause of the issue.

from cloud-sql-proxy.

roberthbailey avatar roberthbailey commented on July 21, 2024

@Carrotman42 — Let me know if you need any help debugging from the GKE-side of things.

from cloud-sql-proxy.

Carrotman42 avatar Carrotman42 commented on July 21, 2024

Thanks for the offer, but it turned out to be a strictly Cloud SQL-related problem. I submitted a fix this morning and it should be in production within a week or so. There may still be bugs related to this one which are yet undiscovered, but until then the workaround of resetting SSL configuration should work for this class of bug.

I will close this bug when the fix finishes rolling out.

from cloud-sql-proxy.

Carrotman42 avatar Carrotman42 commented on July 21, 2024

The fix should be rolled out. Please reopen if you're still encountering the problem.

from cloud-sql-proxy.

retnuh avatar retnuh commented on July 21, 2024

Hi there, after creating a new instance and restoring from a backup of a different instance, we encountered the same issue. Doing a reset of the SSL configuration cleared the problem.

from cloud-sql-proxy.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.