Trello Import is Not Working with Large Files #19

Closed
opened 2025-10-09 18:34:26 +03:00 by OVERLORD · 2 comments
Owner

Originally created by @Suleman-Elahi on GitHub.

Hi,

I tried to import 1 board from Trello and it spin for a while and then vanish. I have tried it multiple times to no avail. No error and nothing. Although I would agree that I am importing a complex board that gives large JSON file ~107 MB.

In browser console I see:

Failed to load resource: net::ERR_BLOCKED_BY_CLIENT
/api/projects/1595730568765506564/boards?requestId=local:1757918596348:1   Failed to load resource: the server responded with a status of 413 ()
index-DWjGvHqQ.js:56  SyntaxError: Unexpected end of JSON input
logError @ index-DWjGvHqQ.js:56
index-DWjGvHqQ.js:56  The above error occurred in task queueRequest
Originally created by @Suleman-Elahi on GitHub. Hi, I tried to import 1 board from Trello and it spin for a while and then vanish. I have tried it multiple times to no avail. No error and nothing. Although I would agree that I am importing a complex board that gives large JSON file ~107 MB. In browser console I see: ``` Failed to load resource: net::ERR_BLOCKED_BY_CLIENT /api/projects/1595730568765506564/boards?requestId=local:1757918596348:1 Failed to load resource: the server responded with a status of 413 () index-DWjGvHqQ.js:56 SyntaxError: Unexpected end of JSON input logError @ index-DWjGvHqQ.js:56 index-DWjGvHqQ.js:56 The above error occurred in task queueRequest ```
Author
Owner

@Suleman-Elahi commented on GitHub:

I did all that. I was happening due to cloudflare's proxy(free plan has 100MB limit). I turned it off. Perhaps planka can switch to chunked uploads in future.

@Suleman-Elahi commented on GitHub: I did all that. I was happening due to cloudflare's proxy(free plan has 100MB limit). I turned it off. Perhaps planka can switch to chunked uploads in future.
Author
Owner

@meltyshev commented on GitHub:

Hey! It looks like the exact error returned from the server is 413 - Content Too Large, and in the console the issue is that the server responds with this error in plain text instead of JSON - that's why the client fails to parse it (since it expects JSON).

My assumption is that you have a proxy server configured with a max body size limit, and once that limit is exceeded - it returns the plain text error. For example, in the PLANKA Docs for Nginx configuration there's a line client_max_body_size 50M. If that's the case, I'd suggest increasing client_max_body_size to something like 128M.

@meltyshev commented on GitHub: Hey! It looks like the exact error returned from the server is `413 - Content Too Large`, and in the console the issue is that the server responds with this error in plain text instead of JSON - that's why the client fails to parse it (since it expects JSON). My assumption is that you have a proxy server configured with a max body size limit, and once that limit is exceeded - it returns the plain text error. For example, in the PLANKA Docs for Nginx configuration there's a line `client_max_body_size 50M`. If that's the case, I'd suggest increasing `client_max_body_size` to something like `128M`.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/planka#19