Blob troubleshooting
Diagnose driver selection, upload, and file-serving problems.
Use this page when Blob is wired up but uploads, reads, or served files do not behave the way you expect.
The wrong driver is selected
| Likely cause | Fix |
|---|---|
| The environment does not expose the hosted storage settings you expected. | Set blob.driver explicitly while you validate the setup. |
| The runtime cannot read your provider credentials or bucket config. | Recheck the top-level blob config and runtime environment variables. |
Upload validation fails
| Likely cause | Fix |
|---|---|
| The file exceeds the configured limit. | Increase the ensure.maxSize rule or reduce the upload size. |
| The content type is not allowed. | Recheck ensure.types or the route-level validation. |
The file does not serve correctly
| Likely cause | Fix |
|---|---|
| The route points at the wrong blob pathname. | Recheck the pathname you pass into blob.serve(). |
| The blob was stored without the expected content type. | Re-store the object with an explicit contentType. |
Still stuck
- Re-run the flow from Quickstart.
- Use Blob SDK to confirm the object exists and the pathname is correct.
- Recheck File uploads if the failure starts at form submission time.