Title: Incompatible with Google Cloud SQL proxy socket connections
Last modified: January 6, 2018

---

# Incompatible with Google Cloud SQL proxy socket connections

 *  [ahmedsl](https://wordpress.org/support/users/ahmedsl/)
 * (@ahmedsl)
 * [8 years, 5 months ago](https://wordpress.org/support/topic/incompatible-with-google-cloud-sql-proxy-socket-connections/)
 * Google recommends using Google Cloud SQL proxy, which creates a local UNIX socket,
   to connect to its managed SQL service. These sockets are generated in the format:
 * `project:region:instance`
 * So you end up with a local file like:
 * `/run/cloud_sql_proxy/my-project:us-central1:my-instance`
 * Using this local file in db-config.php like:
 * `'host' => 'localhost:/run/cloud_sql_proxy/my-project:us-central1:my-instance`
 * Generates thousands of global__r errors in the debug.log and basically breaks
   everything. I think the colons in the local file aren’t being escaped / interpreted
   correctly and that makes the database unreachable.

The topic ‘Incompatible with Google Cloud SQL proxy socket connections’ is closed
to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/hyperdb_33353d.svg)
 * [HyperDB](https://wordpress.org/plugins/hyperdb/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/hyperdb/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/hyperdb/)
 * [Active Topics](https://wordpress.org/support/plugin/hyperdb/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/hyperdb/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/hyperdb/reviews/)

 * 0 replies
 * 1 participant
 * Last reply from: [ahmedsl](https://wordpress.org/support/users/ahmedsl/)
 * Last activity: [8 years, 5 months ago](https://wordpress.org/support/topic/incompatible-with-google-cloud-sql-proxy-socket-connections/)
 * Status: not resolved