Migrate a MySQL Database to Google Cloud SQL: Challenge Lab Reviews

this shii is not working freaking give more steps and command to runnnn

abdirahman I. · Reviewed over 3 years ago

Mykhailo Z. · Reviewed over 3 years ago

Katia Kaori K. · Reviewed over 3 years ago

Nakayama M. · Reviewed over 3 years ago

ASHISH R. · Reviewed over 3 years ago

Roland Adrian I. · Reviewed over 3 years ago

it works...

Carlos V. · Reviewed over 3 years ago

Carlos V. · Reviewed over 3 years ago

JUTTUKA H. · Reviewed over 3 years ago

William M. · Reviewed over 3 years ago

The lab is broken because the system reports "Your PHP Installation Appears to be Missing the MySQL Extension Which is Required by WordPress". So the blog was not running in the first place.

Kalyan K. · Reviewed over 3 years ago

The lab is broken because the system reports "Your PHP Installation Appears to be Missing the MySQL Extension Which is Required by WordPress". So the blog was not running in the first place.

Kalyan K. · Reviewed over 3 years ago

Gopal B. · Reviewed over 3 years ago

Maksym K. · Reviewed over 3 years ago

Ewelina K. · Reviewed over 3 years ago

Piotr M. · Reviewed over 3 years ago

Przemysław D. · Reviewed over 3 years ago

Aleksander C. · Reviewed over 3 years ago

Michael G. · Reviewed over 3 years ago

Christian B. · Reviewed over 3 years ago

Paweł M. · Reviewed over 3 years ago

"Check that the blog instance is authorized to access Cloud SQL" test fails even though both "lab-monitor" and "blog" VMs are able to connect to cloud SQL instance. The message returned by the check is this: Check complete. Points earned: 0. Message: No matching authorization found. Instance IPs: ["34.168.80.26", "35.233.193.251"] Cloud SQL authorization ranges: ["34.168.80.26", "35.233.193.251"] Why? update: if you grant in CloudSQL instance connection whitelist "0.0.0.0/0" then it works, which is not good at all. Another idea would be to set the VM IP in CIDR notation which I have not tried and may fix the problem and be more secure than wildcard

Giorgi J. · Reviewed over 3 years ago

documentation was linked was vague and unhelpful for the use case

Herleen K. · Reviewed over 3 years ago

Gaby C. · Reviewed over 3 years ago

documentation was linked was vague and unhelpful for the use case

Herleen K. · Reviewed over 3 years ago