Criar bancos de dados do Cloud SQL avaliações

Selmir K. · Revisado há about 1 month

Wow, I tried a lot of time to complete this lab because the ssh to the VM was not working... After all I just run gcloud auth login before trying ssh and generate the ssh keys locally. But in general good material to work and practice about CloudSQL and Client conn.

Juan C. · Revisado há about 1 month

Igor P. · Revisado há about 1 month

Oleg N. · Revisado há about 1 month

Muhammad S. · Revisado há about 1 month

Leonardo M. · Revisado há about 1 month

Aziz A. · Revisado há about 1 month

Francisco P. · Revisado há about 1 month

Dave S. · Revisado há about 1 month

Ramya Aline A. · Revisado há about 1 month

Vijaya Mary Hana M. · Revisado há about 1 month

Priya G. · Revisado há about 1 month

John Lhoyd J. · Revisado há about 1 month

Pallavi P. · Revisado há about 2 months

Takuya H. · Revisado há about 2 months

Rohit K. · Revisado há about 2 months

Nikica G. · Revisado há about 2 months

Not able to SSH the VM in the last step.

Nikita G. · Revisado há about 2 months

Gowtham R. · Revisado há about 2 months

Keerthana S. · Revisado há about 2 months

Alex P. · Revisado há about 2 months

connection to vm instance always failed with ssh key errors

Husong L. · Revisado há about 2 months

Dedi A. · Revisado há about 2 months

JOSE JAVIER O. · Revisado há about 2 months

could not connect to VM in lab via SSH. ---- Checking VPC settings ---- VPC settings: 1 issue(s) found. There is an issue with your IAP configuration Check the following items: - The IAP firewall rule is valid. - IAP tunneling is enabled. - You are connecting using an IAP token. - You have the IAM role of Project Owner, IAP-Secured Tunnel User, or iap.tunnelInstances.accessViaIAP (preferred) - Your organization hasn't blocked access to external IP addresses. IAP changes the source traffic to 35.235.240.0/20 and the tunnel to https://tunnel.cloudproxy.app. - If your organization blocks access to public IP addresses, try connecting through a bastion server. Connection via cloud identity-aware proxy failed Code: 4003 Reason: failed to connect to backend connection to VM is refused

Chris S. · Revisado há about 2 months