CloudRun Suddenly got `Improper path /cloudsql/{SQL_CONNECTION_NAME} to connect to Postgres Cloud SQL instance

TL;DR

This log was recently added in the Cloud Run data path to provide more context for debugging CloudSQL connectivity issues. The fix is ready and should roll out soon.

Steps

1. This log was recently added in the Cloud Run data path to provide more context for debugging CloudSQL connectivity issues. However, the original logic was overly aggressive, emitting this message even for properly working CloudSQL connections. Your application is working correctly and should not receive this warning. Thank you for reporting this issue. The fix is ready and should roll out soon. You should not see this message anymore after the fix is out.

When to use

You are seeing this: However, the original logic was overly aggressive, emitting this message even for properly working CloudSQL connections. Use this skill when you run into "CloudRun Suddenly got `Improper path /cloudsql/{SQLCONNECTIONNAME} to connect to Postgres Cloud SQL instance".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Source: Stack Overflow #67595318 (accepted answer, 12 votes): We have been running a service using NestJS and TypeORM on fully managed CloudRun without issues for several months. Yesterday PM we started getting Improper path /cloudsql/{SQL_CONNECTION_NAME} to connect to Postgres Cloud SQL instance "{SQL_CONNECTION_NAME}" errors in our logs. We didn't make any server/SQL changes around this timestamp. Currently there is no impact to the service so we are not sure if this is a serious issue. This error is not from our code, and our third party modules shouldn't know if we use Cloud SQL, so I have no idea where this errors come from. My assumption is...

Verified resolution: This log was recently added in the Cloud Run data path to provide more context for debugging CloudSQL connectivity issues. However, the original logic was overly aggressive, emitting this message even for properly working CloudSQL connections. Your application is working correctly and should not receive this warning. Thank you for reporting this issue. The fix is ready and should roll out soon. You should not see this message anymore after the fix is out.

Source URL: https://stackoverflow.com/questions/67595318/cloudrun-suddenly-got-improper-path-cloudsql-sql-connection-name-to-connect