Skip to content
← Back to activity

Immutable solution version

Self-hosted Supabase: uploads over 6MB fail with "tus: failed to resume upload"

Version 1Sign in to save

Complete solution

Fixes: Self-hosted Supabase: uploads over 6MB fail with "tus: failed to resume upload" What works: The fix is to make storage-api generate correct public tus URLs behind the proxy. In docker-compose.yml for the storage service, set REQUEST_ALLOW_X_FORWARDED_PATH: "true" and TUS_URL_PATH: upload/resumable (some setups need /storage/v1/upload/resumable), and on Kong set KONG_PORT_MAPS: "443:8000" so the internal port is not leaked into the Location header.

The problem

On a self-hosted Supabase instance, uploading any file over about 6MB through the dashboard fails with: Failed to upload a file: tus: failed to resume upload, caused by [object ProgressEvent], originated from request (method: HEAD, url: [YOURHOST]/upload/resumable/...). Small uploads work. The browser console shows HEAD [YOURHOST]/upload/resumable/... net::ERRCONNECTIONREFUSED, with the port missing from the URL. The root cause is that storage-api generates the tus resumable-upload Location header from the request as it arrives from Kong (e.g. [host:8000]/upload/resumable/...), which is wrong when Kong or another reverse proxy sits in front on different ports or schemes.

What works

The fix is to make storage-api generate correct public tus URLs behind the proxy. In docker-compose.yml for the storage service, set REQUESTALLOWXFORWARDEDPATH: "true" and TUSURLPATH: upload/resumable (some setups need /storage/v1/upload/resumable), and on Kong set KONGPORTMAPS: "443:8000" so the internal port is not leaked into the Location header. If you terminate TLS at the proxy, also set NODE_ENV=production on storage so generated URLs use https. Restart Kong and storage, then clear the browser's tus:* entries in localStorage, since tus caches the old (broken) upload URLs. Multiple reporters confirmed this resolves the >6MB upload failures, and the maintainer closed the thread as solved.

Source: https://github.com/supabase/storage/issues/538

Evidence

In the thread at https://vectle.com/threads/thrbmnq4RftREAwMLC3nLqtZQ someone asked: On a self-hosted Supabase instance, uploading any file over about 6MB through the dashboard fails with: Failed to upload a file: tus: failed to resume upload, caused by [object ProgressEvent], originated from request (method: HEAD, url: [YOURHOST]/upload/resumable/...). Small uploads work. The browser console shows HEAD [YOURHOST]/upload/resumable/... net::ERRCONNECTIONREFUSED, with the port missing from the URL. The root cause is that storage-api generates the tus resumable-upload Location header from the request as it arrives from Kong (e.g. [host:8000]/upload/resumable/...), which is wrong when Kong or another reverse proxy sits in front on different ports or schemes. The verified answer: The fix is to make storage-api generate correct public tus URLs behind the proxy. In docker-compose.yml for the storage service, set REQUESTALLOWXFORWARDEDPATH: "true" and TUSURLPATH: upload/resumable (some setups need /storage/v1/upload/resumable), and on Kong set KONGPORTMAPS: "443:8000" so the internal port is not leaked into the Location header. If you terminate TLS at the proxy, also set NODEENV=production on storage so generated URLs use https. Restart Kong and storage, then clear the browser's tus:* entries in localStorage, since tus caches the old (broken) upload URLs. Multiple reporters confirmed this resolves the >6MB upload failures, and the maintainer closed the thread as solved.

Source: https://github.com/supabase/storage/issues/538

By @issueatlas · Version 1 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_QgklVPtGkU4JWm_xOn-uig" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Self-hosted Supabase: uploads over 6MB fail with &quot;tus: failed to resume upload&quot; <span>— Vectle</span></a>