NoSuchBucket / 404 The specified bucket does not exist Google Cloud / Firebase Origin: Platform & cloud OSI layer 7 · Application Last updated 4 Nov 2026

Cloud Storage: 404 Not Found — The specified bucket does not exist / No such object: bucket/object

The bucket or object name in your request doesn't exist (typo, deleted, wrong project, or a leading slash issue).

Exact message you may see The specified bucket does not exist404 Not Found No such objectNoSuchBucket The specified bucket does not existBucketNotFoundException: 404 gs:// bucket does not existNo such object: bucket/object
Explore the map of this error Full error map →
Seen on: Google Cloud

Meaning

Check the exact name (bucket names are global and case-sensitive; objects can contain slashes but no real folders). Confirm with gcloud storage ls. For website hosting, NoSuchKey pages appear when index.html or 404.html is not configured.

Common causes

  • Bucket name typo or deleted bucket
  • Object name wrong/with leading slash
  • Using the wrong project's credentials
  • Eventually consistent listing right after delete
  • Website config missing main page

⚡ Quick fix

  1. List: gcloud storage ls gs://BUCKET/
  2. Verify object path exactly
  3. Set website config: gsutil web set -m index.html -e 404.html gs://BUCKET

Detailed fix by platform

gcloud

  1. gcloud storage ls gs://BUCKET/path/

How to diagnose

  1. Bucket — Exists?
  2. Object — Exact name?
  3. Project — Correct credentials?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: Platform & cloud. Errors that are often confused with or caused by this one (click to open):

403: does not have storage.objects.get access — Cloud Storage: 403 Forbidden — user@example.com does not have storage.objects.get access to the Google Cloud Storage object (Google Cloud / Firebase)403: does not have st…API has not been used in project before or it is disabled — Google Cloud: 403 SERVICE_DISABLED — Cloud Resource Manager API has not been used in project 123456 before or it is disabled. Enable it by visiting (Google Cloud / Firebase)API has not been used…Artifact Registry: Permission artifactregistry.repositories.uploadArtifacts denied — Docker push: denied: Permission "artifactregistry.repositories.uploadArtifacts" denied on resource "projects/p/locations/l/repositories/r" (Google Cloud / Firebase)Artifact Registry: Pe…CORS: No Access-Control-Allow-Origin (Cloud Storage) — Browser: Access to fetch at 'https://storage.googleapis.com/bucket/file' from origin 'https://app.example.com' has been blocked by CORS policy (Google Cloud / Firebase)CORS: No Access-Contr…Error 403: API has not been used in project (Terraform) — Terraform: Error: Error creating Network: googleapi: Error 403: Compute Engine API has not been used in project 123 before or it is disabled (Terraform)Error 403: API has no…Google provider: could not find default credentials — Terraform: Error: Attempted to load application default credentials since neither `credentials` nor `access_token` was set in the provider block. No credentials loaded (Terraform)Google provider: coul…SignatureDoesNotMatch (Cloud Storage signed URL) — Cloud Storage: SignatureDoesNotMatch — The request signature we calculated does not match the signature you provided (Google Cloud / Firebase)SignatureDoesNotMatch…storage/unauthorized: User does not have permission to access — Firebase Storage: Firebase Storage: User does not have permission to access 'images/photo.jpg'. (storage/unauthorized) (Google Cloud / Firebase)storage/unauthorized:…NoSuchBuc…

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.