Memigrasikan Database MySQL ke Google Cloud SQL: Challenge Lab Ulasan

Peter V. · Diulas 25 hari lalu

Payal L. · Diulas 25 hari lalu

Gauri L. · Diulas 25 hari lalu

Gokul K. · Diulas 25 hari lalu

Labs are great. But the UI of is awfull. Fix it please

Egor S. · Diulas 25 hari lalu

instruction for --authorized-networks not clear (use range and not ip)

Yura T. · Diulas 25 hari lalu

Vikranth R. · Diulas 25 hari lalu

Luiz F. · Diulas 26 hari lalu

Antonio Whinnes G. · Diulas 26 hari lalu

Varsha P. · Diulas 26 hari lalu

Hendy Chandra H. · Diulas 26 hari lalu

Error

Sohail S. · Diulas 26 hari lalu

localhost being used instead of the actual ip address is kind of annoying.

Deeksha C. · Diulas 26 hari lalu

shyamkumar m. · Diulas 26 hari lalu

darren c. · Diulas 26 hari lalu

doesn't work (task 5) and cannot understand why (have tried everything)

Deeksha C. · Diulas 26 hari lalu

Loic N. · Diulas 26 hari lalu

David D. · Diulas 26 hari lalu

Vitalii L. · Diulas 26 hari lalu

RAUSHAN Y. · Diulas 26 hari lalu

Mukesh Kumar Y. · Diulas 26 hari lalu

John L. · Diulas 26 hari lalu

Shawn M. · Diulas 26 hari lalu

Jason E. · Diulas 26 hari lalu

This lab has a validation bug in Task 3. The Cloud SQL instance automatically authorizes RFC 1918 IP ranges (including 10.142.0.3 from the blog VM), but the lab's scoring system fails to detect this implicit authorization and requires manual addition of the IP, which the Google Cloud API explicitly blocks. All manual steps were completed successfully and the WordPress blog is fully functional with the Cloud SQL database. Please fix the validation logic to recognize automatically authorized IP ranges.

Alexandre C. · Diulas 27 hari lalu