Opinie (Connect to Remote Agents with ADK and the Agent2Agent (A2A) SDK)

Getting errors only treid everything 00 OK INFO: 127.0.0.1:53800 - "POST /apps/illustration_agent/users/user/sessions HTTP/1.1" 403 Forbidden 2026-03-24 19:14:35,427 - INFO - local_storage.py:60 - Creating local session service at /home/student_02_769af13ec822/adk_and_a2a/illustration_agent/.adk/session.db INFO: 127.0.0.1:53800 - "GET /apps/illustration_agent/users/user/sessions HTTP/1.1" 200 OK INFO: 127.0.0.1:53800 - "POST /run_sse HTTP/1.1" 403 Forbidden INFO: 127.0.0.1:53800 - "GET /debug/trace/session/ HTTP/1.1" 307 Temporary Redirect INFO: 127.0.0.1:53800 - "GET /debug/trace/session HTTP/1.1" 404 Not Found

Bhanu P. · Sprawdzono 24 dni temu

i got an error forbidden 403 on this lab

Megha S. · Sprawdzono 24 dni temu

facing issue to compete task2, as per guided still throws same error for 403 and changed to authuser-2 respectively. the .env file doesnot get filled with respectve environment and facing issue of 403, 404,307

Ruchita H. · Sprawdzono 24 dni temu

Kavish N. · Sprawdzono 24 dni temu

Getting forbidden error and unable to resolve it

Venkatesh B. · Sprawdzono 24 dni temu

Shreetama B. · Sprawdzono 24 dni temu

I kept getting a 403 error which did not get fixed with the given instructions in the codelabs

Amartya G. · Sprawdzono 24 dni temu

things are not working

Prashanth reddy G. · Sprawdzono 24 dni temu

The lab content is good in theory, but the execution experience is very frustrating. I followed all the steps carefully and was able to successfully start the server and open the ADK UI. However, the agent did not respond to any prompts. The terminal consistently showed "403 Forbidden" errors for session-related endpoints (such as /users/user/sessions and /run_sse), which completely blocked progress. This appears to be an authentication/session issue in the lab environment rather than a mistake in following instructions. The lab seems highly sensitive to account/session configuration, but this is not clearly explained. Additionally, the troubleshooting guidance provided (e.g., modifying the URL using "authuser") was not applicable in my case because the URL did not include any "authuser" parameter. This made it even more confusing, as the suggested fix could not be applied. As a result, I spent most of the lab time debugging environment and authentication issues instead of learning the intended concepts. Suggestions: * Clearly instruct users to use a single Google account or incognito mode from the beginning * Provide accurate and applicable troubleshooting steps (especially for 403 errors) * Ensure instructions match the actual URLs and environment behavior * Improve session handling to make the lab more stable and beginner-friendly Overall, the concept is valuable, but the technical issues significantly reduce the learning experience.

Mehhuu Y. · Sprawdzono 24 dni temu

403 error coming up, authuser doesnot resolves the issue

Harsh M. · Sprawdzono 24 dni temu

shreyash w. · Sprawdzono 24 dni temu

Aditya Raj S. · Sprawdzono 24 dni temu

Sai Nireeksha M. · Sprawdzono 24 dni temu

getting Forbidden Error 403 and it is not solving so cannot complete the tasks. lost 21 credits because of that

Rupal K. · Sprawdzono 24 dni temu

Shahid G. · Sprawdzono 24 dni temu

Unable to complete task 2 and 4 due to repeated 403 error, even after trying the suggested workaround.

Lalit K. · Sprawdzono 24 dni temu

sakshi g. · Sprawdzono 24 dni temu

Vinamra J. · Sprawdzono 24 dni temu

lab not working in cloud console. Unable to get the output

DEEPAK K. · Sprawdzono 24 dni temu

Kundan K. · Sprawdzono 24 dni temu

Harshit Sai T. · Sprawdzono 24 dni temu

Anmol H. · Sprawdzono 24 dni temu

Hi Support, I would like to request a credit refund for this lab. I encountered a persistent technical issue with the ADK Web UI on Cloud Shell. Even after following the instructions, the interface failed to generate a Session ID and User ID, returning a '403 Forbidden' error on every POST /sessions request. This prevented me from completing the lab tasks despite multiple attempts (including Incognito mode and port changes). It seems to be a backend/proxy issue with the Cloud Shell Web Preview. Please check and restore my credits. Thank you.

Mutiara N. · Sprawdzono 24 dni temu

Daksh B. · Sprawdzono 24 dni temu

SOMSUBHRA N. · Sprawdzono 24 dni temu