IpInkpacket

Blog

Why File storage is unavailable is not a rejected upload

Inkpacket File storage is unavailable is an unreachable bucket after a PDF was accepted. It is not a picker reject and not a spend. That is storage-down honesty — not HTTP 402, not checkout.

Upload a PDF from Documents → new, or from Templates → new. A real file at or under 15 MB is accepted. After that, an unreachable bucket returns File storage is unavailable. Re-upload a valid PDF. Inkpacket does not pretend the file landed. That is storage-down honesty: the picker already said yes, the object never reached a readable store, a missing bucket is not Upload a PDF file, and opening Billing will not “repair storage.”

The four picker refusals are why a rejected PDF upload is not an envelope. Where a good file is supposed to land is where uploaded PDFs are stored. The Settings card is Settings storage: S3 versus local. Desk help is Docs. This guide is why File storage is unavailable sits after accept, and why that string is not a bounced picker.

The FAQ and Features start from a PDF. Ask Inkpacket for why File storage is unavailable is not a rejected upload to open this article. Ask how file storage works to open help. Those phrases stay on the product screens. This article is the public version of File storage is unavailable — the string the desk already uses when the bucket cannot be reached after a file was accepted.

What unavailable covers

  • An unreachable bucket after accept. File storage is unavailable. Re-upload a valid PDF.
  • A missing object later. The PDF could not be loaded from storage. That envelope already exists.
  • A zero-byte stored object. The stored PDF is empty. That is not the picker saying no first.
  • A signer who sees Could not load the PDF. Refresh; if it persists, the sender opens the envelope and confirms the file.

Settings shows S3-compatible when S3_BUCKET, S3_ACCESS_KEY_ID, and S3_SECRET_ACCESS_KEY are set; optional S3_ENDPOINT points at R2 or another S3-compatible host. Otherwise Local fallback — uploads still work. GET /api/v1/health reports storage.configured and storage.backend. Health staying 200 does not turn an unreachable bucket into a filed copy. File storage is unavailable is not a send. It does not increment the monthly cap. It does not return HTTP 402 ENVELOPE_LIMIT. A rejected picker never reached this string — empty, non-PDF, unreadable, or over 15 MB files are refused first.

What this is not

  • Not Upload a PDF file. That is an empty picker. Nothing was accepted.
  • Not Only PDF files are accepted. A renamed office file never left the picker.
  • Not PDF must be 15 MB or smaller. Oversized bytes are rejected before storage is asked.
  • Not checkout. Billing is not open. Paying a listed price does not bring the bucket back.

Local fallback still accepts a valid PDF when S3_* keys are missing. That is not “storage down.” File storage is unavailable is the other fork: keys or a local path exist, the file was accepted, then the store could not be reached. Reminders go out by email today. Text-message (SMS) is coming soon. Email still soft-fails on the send, not on this string. Text-message (SMS) is coming soon. Drive archive waits for completed. Stripe off: Payments not live. None of those flags repair the bucket or count the failed write as an envelope.

The click-path

  1. Upload a real PDF at or under 15 MB. If the picker refuses, that is a reject — not this article.
  2. If the desk says File storage is unavailable, fix the store. Re-upload. Do not open Billing for a bucket.
  3. If a later preview says The stored PDF is empty or The PDF could not be loaded from storage, re-upload on that same envelope.
  4. If send returns HTTP 402 ENVELOPE_LIMIT, that is the monthly cap, not a storage string.
  5. On a phone, Documents is a drawer row. File storage is unavailable is the same copy. Help is not a drawer row — it stays in the header.

Saving a good file as a template still does not count — why saving a template is not an envelope. The inbox statuses are document list aging and status honesty. Ask Inkpacket for why File storage is unavailable is not a rejected upload to open this article. Ask how file storage works to open help. Ask upload a pdf to open Documents → new.

Ask and the store

Ask Inkpacket for why File storage is unavailable is not a rejected upload to open this article. Ask how file storage works or what does file storage unavailable mean to open help. Marketing Ask stays site Q&A and deep links. It will not repair a bucket, re-upload a PDF, or increment the monthly cap from this article. Unavailable is a store miss after accept. The four picker strings are a different no.

Caps and what is not open yet

Seeing File storage is unavailable is not a send. Send of a draft that actually stored is. Free allows 5 packets a month. Free at 5 packets a month is the live cap desk send, bulk rows, Web Form fills, and API send share. Hitting it returns HTTP 402 ENVELOPE_LIMIT. Starter is 20 envelopes — more than Free — plus 3 published Web Forms. Seat counts are planning numbers; invite does not refuse when a workspace is full.

Billing is published, not charging. Checkout is not open. Text-message (SMS) is coming soon. Drive missing: Drive not configured. Stripe off: Payments not live. Those flags do not repair the bucket or count a failed write. The FAQ and FAQ use File storage is unavailable in the same words.

Fix the store. Re-upload. Send when the file is actually there. Open a workspace on Free — see published pricing — and read File storage is unavailable next to the four picker strings so storage-down honesty is a post-accept miss you already named, not a 402 you opened Settings to undo.

Open a workspace on Free

Billing is published, not charging. Send an envelope from the desk without a card.

Open a workspace