Docker: The upstream server is timing out

[Almaju]

Bug report

Describe the bug

I am trying to implement supabase in a self-hosted environment. I could not make the storage work in a remote VPS. I get "The upstream server is timing out" when trying to upload a file. The entries are correctly created in the database storage.objects though.

To Reproduce

I used the default docker-compose.yml from the doc with STORAGE_BACKEND: file. My intuition is that it has something to do with FILE_STORAGE_BACKEND_PATH?

Expected behavior

The file is uploaded.

Screenshots

/

System information

• OS: Ubuntu
• Version of supabase-js: supabase/storage-api:v0.10.0
• Version of Node.js: v18.3.0

Additional context

Logs from storage when I try to upload:

supabase-storage | [1655166215767] INFO (7 on dd6a4334ff1e): incoming request
supabase-storage |     req: {
supabase-storage |       "method": "POST",
supabase-storage |       "url": "/object/74c7f520-42cf-4ae6-8c08-0479d58f9f8a/Screenshot%202022-04-27%20at%2016.55.23.png",
supabase-storage |       "hostname": "storage:5000",
supabase-storage |       "remoteAddress": "172.21.0.4",
supabase-storage |       "remotePort": 55780
supabase-storage |     }
supabase-storage |     reqId: "req-9"
supabase-storage | [1655166215773] INFO (7 on dd6a4334ff1e): content-type is multipart/form-data; boundary=----WebKitFormBoundarymG0C2C2F66QwFd1q
supabase-storage |     reqId: "req-9"
supabase-storage |     tenantId: "stub"
supabase-storage | [1655166215815] INFO (7 on dd6a4334ff1e): results
supabase-storage |     results: null
supabase-storage |     reqId: "req-9"
supabase-storage |     tenantId: "stub"
supabase-storage | [1655166276139] INFO (7 on dd6a4334ff1e): incoming request
supabase-storage |     req: {
supabase-storage |       "method": "POST",
supabase-storage |       "url": "/object/sign/74c7f520-42cf-4ae6-8c08-0479d58f9f8a/Screenshot%202022-04-27%20at%2016.55.23.png",
supabase-storage |       "hostname": "storage:5000",
supabase-storage |       "remoteAddress": "172.21.0.4",
supabase-storage |       "remotePort": 55784
supabase-storage |     }
supabase-storage |     reqId: "req-a"
supabase-storage | [1655166276178] INFO (7 on dd6a4334ff1e): results
supabase-storage |     results: {
supabase-storage |       "id": "26ae454f-b2a4-42d4-bee5-bf31d1881bb5"
supabase-storage |     }
supabase-storage |     reqId: "req-a"
supabase-storage |     tenantId: "stub"
supabase-storage | [1655166276181] INFO (7 on dd6a4334ff1e): going to sign /object/sign/74c7f520-42cf-4ae6-8c08-0479d58f9f8a/Screenshot%202022-04-27%20at%2016.55.23.png
supabase-storage |     reqId: "req-a"
supabase-storage |     tenantId: "stub"
supabase-storage | [1655166276186] INFO (7 on dd6a4334ff1e): request completed
supabase-storage |     res: {
supabase-storage |       "statusCode": 200
supabase-storage |     }
supabase-storage |     responseTime: 43.80145001411438
supabase-storage |     reqId: "req-a"
supabase-storage |     tenantId: "stub"

[fenos]

what path are you trying to write the file to? did you mount a persistent volume?

[fenos]

Feel free to re-open when providing more info