We already have the max upload size set to 500mb in fact. The max size of each media item that we are uploading is under 20mb. The usync sync package doesn't exceed 70mb.
I don't see the pagesize setting currently in our publisher.config. I assume it defaults to 50 as in the example on the linked page, is that right?
Yes in later versions the default is 50, you can push that right down if you want to test it.
but i would check your upload size configs in the web.config/IIS just to make sure.
a 413 error is returned by the webserver its not the uSync code doing that, and 413 is request to large so it does point to it being the server stopping it.
but I could be a proxy or firewall or load balancer if you have one, as the requests might well be going through that. before hitting the server ?.
Request entity too large error
Hi Kevin
uSync Complete 8.11.4
Uploading a usync package with media folder that contains several fairly large files (max 12mb each). Package size is about 70mb.
Getting this error in the browser:
Any way around this?
Regards
Jules
Hi,
you can see if reducing the
PageSizevalue in the uSync config will help (this will pack less items per request, so reduce the size.https://docs.jumoo.co.uk/usync/8.x/complete/publisher/config
but you probably want to up the max upload size in the web config, to let the larger file uploads (just for uSync).
https://docs.jumoo.co.uk/usync/8.x/complete/publisher/upload
Hi Kevin
We already have the max upload size set to 500mb in fact. The max size of each media item that we are uploading is under 20mb. The usync sync package doesn't exceed 70mb.
I don't see the pagesize setting currently in our publisher.config. I assume it defaults to 50 as in the example on the linked page, is that right?
Jules
Hi,
Yes in later versions the default is 50, you can push that right down if you want to test it.
but i would check your upload size configs in the web.config/IIS just to make sure.
a 413 error is returned by the webserver its not the uSync code doing that, and 413 is request to large so it does point to it being the server stopping it.
but I could be a proxy or firewall or load balancer if you have one, as the requests might well be going through that. before hitting the server ?.
Found it!
Our general
maxcontentlengthmaxrequestlengthsettings were in fact too low for the package size.There was a location element added in web.config for path
umbraco/uSyncReceiveHowever, the error we saw was on the path
umbraco/backoffice/uSync/uSyncNuExporterApi/UploadFileHad to add another location element wth higher
maxcontentlengthmaxrequestlengthfor pathumbraco/backoffice/uSync/uSyncNuExporterApi/UploadFileis working on a reply...