Google CloudMid

Cloud Run HTTP 403: not authenticated or forbidden

A Cloud Run 403 means the caller lacks run.routes.invoke or sent no valid ID token. Grant Cloud Run Invoker, send a token, or allow public access on purpose.

What you see

  • HTTP 403: The request was not authenticated. Either allow public access or set the proper Authorization header
  • HTTP 403: Forbidden: Your client does not have permission to get URL from this server.

What it means

By default a Cloud Run service requires authentication. The caller needs permission to invoke it and must present a valid identity token.

How to confirm the cause

  1. 1
    Check the service's IAM policy
    gcloud run services get-iam-policy SERVICE_NAME --region REGION

    Look for the caller (or allUsers if the service is meant to be public) bound to a role that includes run.routes.invoke.

  2. 2
    Test from a browser through a temporary proxy
    gcloud run services proxy SERVICE --project PROJECT-ID

    The docs describe this as a temporary workaround for browser access.

Causes and fixes

  • Caller lacks permission

    HOW TO TELL
    The identity that makes the call has no invoker role.
    FIX
    Grant run.routes.invoke. The Cloud Run Admin and Cloud Run Invoker roles include it. For a service account caller, add it to the service and give it Cloud Run Invoker.
  • No valid ID token in the request

    HOW TO TELL
    The request has no Authorization header, or the token is not valid.
    FIX
    Send a valid ID token.
  • The service should be public but is not

    HOW TO TELL
    Anonymous users get 403.
    FIX
    Update the service's IAM settings to allow public access, only if that is intended.
  • VPC Service Controls

    HOW TO TELL
    No resource.type = "cloud_run_revision" log entry exists for the request.
    FIX
    VPC Service Controls may be blocking a service with All ingress. Check the perimeter.

How to stop it coming back

  • Keep services private by default and grant invoker to specific identities.
  • Document which service accounts call which services.

Keep going

Sources

Google Cloud documentation (docs.cloud.google.com), read 18 Nov 2026.

Search

Search cheat sheets and projects