Build an LLM and RAG-based Chat Application with AlloyDB and Vertex AI Reviews

psql "host=$INSTANCE_IP user=$PGUSER dbname=postgres" -c "CREATE DATABASE $PGDATABASE" Your active configuration is: [cloudshell-1367] psql: error: connection to server at "10.104.48.2", port 5432 failed: Connection timed out Is the server running on that host and accepting TCP/IP connections?

Xing L. · Reviewed 1 hour ago

doohyun c. · Reviewed 2 hours ago

Aswini V. · Reviewed 6 hours ago

Anurag-B M. · Reviewed 7 hours ago

the first milestone on the lab was not validated even if there was completed in the lab.

LIVIU GABRIEL G. · Reviewed 9 hours ago

En la última parte tras el deploy me faltaban permisos

Diego S. · Reviewed 10 hours ago

Subin J. · Reviewed 11 hours ago

psql "host=$INSTANCE_IP user=$PGUSER dbname=postgres" -c "CREATE DATABASE $PGDATABASE" Your active configuration is: [cloudshell-1367] psql: error: connection to server at "10.104.48.2", port 5432 failed: Connection timed out Is the server running on that host and accepting TCP/IP connections?

Xing L. · Reviewed 12 hours ago

gaurav m. · Reviewed 21 hours ago

psql "host=$INSTANCE_IP user=$PGUSER dbname=postgres" -c "CREATE DATABASE $PGDATABASE" Your active configuration is: [cloudshell-1367] psql: error: connection to server at "10.104.48.2", port 5432 failed: Connection timed out Is the server running on that host and accepting TCP/IP connections?

Xing L. · Reviewed 1 day ago

The first step could not go through. Always says there is no TCP/IP connection.

Xing L. · Reviewed 1 day ago

Imran B. · Reviewed 1 day ago

Ayush P. · Reviewed 1 day ago

Atul W. · Reviewed 1 day ago

Martin (Xu) Y. · Reviewed 1 day ago

Muniba A. · Reviewed 1 day ago

Fabiana R. · Reviewed 1 day ago

The deployment failed Deploying... Setting IAM Policy...warning Creating Revision...failed Deployment failed Setting IAM policy failed, try "gcloud beta run services remove-iam-policy-binding --region=us-east1 --member=allUsers --role=roles/run.invoker toolbox" ERROR: (gcloud.run.deploy) The user-provided container failed to start and listen on the port defined provided by the PORT=8080 environment variable within the allocated timeout. This can happen when the container port is misconfigured or if the timeout is too short. The health check timeout can be extended. Logs for this revision might contain more information.

Ana N. · Reviewed 1 day ago

Payam E. · Reviewed 1 day ago

Andrii O. · Reviewed 1 day ago

The first step could not go through. Always says there is no TCP/IP connection.

Xing L. · Reviewed 1 day ago

Chris F. · Reviewed 1 day ago

Valerio P. · Reviewed 1 day ago

only time outs.... start another try

Dirk D. · Reviewed 1 day ago

Andrea F. · Reviewed 1 day ago