Collabora throwing 413 Request Entity Too Large error

rcdncn

I have a Nextcloud instance running on a non-Cloudron server, but use Collabora within Cloudron to open documents and convert. Currently, I will get the following error in my Nextcloud logs:

[richdocuments] Error: Failed to convert preview: Client error: `POST https://[servername]/cool/convert-to/png` resulted in a `413 Request Entity Too Large` response:
<html>
<head><title>413 Request Entity Too Large</title></head>
<body>
<center><h1>413 Request Entity Too Large</h1>< (truncated...)

	GET /core/preview?fileId=11028&x=32&y=32&mimeFallback=true&v=687e6d&a=0
	from 70.54.87.2 by kv_pdacadmin at Sep 12, 2025, 12:46:02 PM

Some research suggests the it might be the nginx at the cloudron side that may be the issue, and that client_max_body_size may need to be increased. What's odd is that I can open large files for editing, so I think that Nextcloud is sending other requests to Collabora (thumbnails, pdf conversion?) that are failing.
I can't see any error logs in nginx on Cloudron, but I can see the access.

Am I on the right path? Is there a documented way to alter the nginx infor for a single app that is persistent between updates?

james

Hello @rcdncn

Is POST https://[servername]/cool/convert-to/png your Nextcloud or the collabora?
This is important because if you Nextcloud responds with 413 Request Entity Too Large then the issue is with your Nextcloud provider.

rcdncn

It's appearing in the Nextcloud log. But isn't this the error received by collabora to Nextcloud when the request is placed?

james

Hello @rcdncn
From the error message you have posted, it looks like Nextcloud is giving this error.
Another question, are you using Cloudflare with proxying by any chance?
Since Cloudflare does limit the max upload size / post size when proxying.

Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.

Cloudron Forum

Collabora throwing 413 Request Entity Too Large error