Menghubungkan ke Agen Jarak Jauh dengan ADK dan SDK Agent2Agent (A2A) Ulasan

Maitrii M. · Diulas 24 hari lalu

auth user error

Gurusharan B. · Diulas 24 hari lalu

Alexandru C. · Diulas 24 hari lalu

worst experience in my entire learning journey

Ak P. · Diulas 24 hari lalu

Stuck to this part. Even though I changed it from 0-8 it doesn't work Note: As before, if you get a Forbidden Error 403, you may have multiple accounts signed into your Incognito session. Try incrementing the value of the authuser value at the end of the URL, for example changing it from authuser=0 to authuser=1. authuser=2, etc. In production you could handle this with a service account creating a Signed URL.

Mark Samuel N. · Diulas 24 hari lalu

Ketan D. · Diulas 24 hari lalu

i dont want to give even one star, so many flaws, i tried my self to rectify the errors but still 1 hour is not enough worst

Nadanesh K. · Diulas 24 hari lalu

Chetan G. · Diulas 24 hari lalu

karthik g. · Diulas 24 hari lalu

a2a step 3 is not able to detect cloud run

Sam W. · Diulas 24 hari lalu

this has a bug

Deeksha C. · Diulas 24 hari lalu

There are too many issue wiht the AUTH always throwing me 403 forbidden error eve though i have tried musltiple things

Akash M. · Diulas 24 hari lalu

Yes

Pramod M. · Diulas 24 hari lalu

lab task 2 and 4 failed because of some glitch

Rohan B. · Diulas 24 hari lalu

Khemraj P. · Diulas 24 hari lalu

Using adk web --allow_origins="*", solved 403 error

Vithurabiman S. · Diulas 24 hari lalu

I encountered a blocking issue in this lab that prevented completion despite following all instructions carefully. The ADK web server started successfully, but every attempt to send a message resulted in a consistent 403 Forbidden error from backend endpoints (e.g., /run_sse and session creation APIs). I verified the following multiple times: Correct lab-provided account was used (no personal account interference) Project ID was correctly set and active gcloud authentication and application-default credentials were configured Vertex AI API was enabled Environment variables (GOOGLE_CLOUD_PROJECT, GOOGLE_CLOUD_LOCATION) were set Clean sessions were used (incognito, multiple browsers, fresh lab restart) Despite all of this, the issue persisted across multiple lab restarts. The provided troubleshooting note about "authuser" is not relevant to this failure point, as the error occurs before any browser-based image preview step. This appears to be an environment or lab configuration issue rather than a user error. Request: I would appreciate either: Credit for lab completion, since the issue is reproducible and blocking, OR Guidance or fix for this specific error This lab consumed significant time (~14 credits), and I made a genuine effort to debug systematically before reporting. Thank you.

jay p. · Diulas 24 hari lalu

Sarath T. · Diulas 24 hari lalu

Kundan K. · Diulas 24 hari lalu

Oken K. · Diulas 24 hari lalu

Akash K. · Diulas 24 hari lalu

Http 403 issue need to explain properly to resolve the issue and move forward

Abhijeet C. · Diulas 24 hari lalu

adk web not working

KC W. · Diulas 24 hari lalu

Anshuman S. · Diulas 24 hari lalu

Venkata M. · Diulas 24 hari lalu