413 Payload Too Large on 156.3mb sized file upload with Business Plan
I just upgraded to Business today to increase my file upload size but am still experiencing 413s on files that are between 100 to 200 mb large.
17 Replies
I did a few hours ago and am still getting the 413.
Is there anything else I should try here? It's been about 24 hours since I've upgraded to business and am still not getting the raise on the file upload limit.
I would check who the 413 is from. For example, if you're using nginx, it has its own upload limit (https://www.tecmint.com/limit-file-upload-size-in-nginx/), sometimes the specific app/etc you are using may as well. You could check the headers on the response to see, if it has Cf-Cache-Status it's not from CF
This is coming from a NodeJS cloudlfare pages function
The response headers have
cf-cache-status: DYNAMICThen the 413 is coming from your origin, not Cloudflare
aagh that's awkward, pages functions run on your pages.dev which won't have a higher upload limit, I imagine that's the issue
What do you mean "nodejs" though? Functions don't run nodejs, it's all v8 isolates
Oops yeah, I mean the JS runtime
So the fix here is probably moving my upload handler into a non-pages worker function and updating the routes, right?
That's my thinking but keep in mind as well there are other constraints you may very well hit, Workers/Functions only have 128MB of memory, if you're not streaming the body though, it will explode
I'm a bit confused by the Business plan. I was under the impression that the upload limit would increase as that's why I paid for it.
It will, for any normal origin
If you make a support ticket, they should be able to bump the pages.dev limit and make it work, as long as you properly handle the body in your worker that is
that would be fantastic, will make one right now. thank you!
I do have a support request open from yesterday:
https://support.cloudflare.com/hc/en-us/requests/2955725
Here it is:
https://support.cloudflare.com/hc/en-us/requests/2957984
Thanks, I can't access support tickets, green names/community champs are just helpful community members who can escalate things and are generally in the know, but not CF Employees, which are orange. Let me know the result of it. If it helps to explain, basically it's just that all pages function requests go through your pages.dev, which is itself an invisible cloudflare website in your account with its own upload limit. It needs to be raised, or else it'll reject the request
Do you know the rate of resolution I should expect from this kind of support?
For Biz, no idea on actual time to resolution. Biz has an SLO (service level objective) of 8-72 hrs (P1-P4 issues), depending on severity for first responses. If it takes too long, we can escalate from here and make sure it gets looked at. Definitely not desired experience for you to upgrade to Business for a feature you can't use due to technical reasons
Thank you for the consideration. It was definitely a surprise to see the 413 persist after upgrading. I'm quite eager to have this resolved.
Hi @Chaika would you be able to help me escalate this issue I created on CF support to raise the upload limit? It's been 5 days since the last update.
https://support.cloudflare.com/hc/en-us/requests/2957984
sure, done, hopefully they can just raise it and unblock you
Thank you @Chaika . I got a response earlier today that they are checking with the Pages team to see if it's doable. Fingers crossed.
Hi @Chaika , I haven't received any update on this request in week. My card has been charged again as well. Could this be escalated to resolution soon? If not, I'd like to see if I can cancel the business plan and get a refund.
https://support.cloudflare.com/hc/en-us/requests/2957984
It's already been escalated once, my understanding is they're waiting on the Pages Team and trying to see if they can make an exception, which I believe was relayed to you. Support is aware of the ticket, If you wanted a refund, you could try in a billing ticket. If it is critcal, using a direct worker on a custom domain or route handling the entire upload should do the trick, although of course it is a bit suboptimal in setup
Should be all set now, if you have any more questions respond in ticket
Thank you!