<p>We've a Craft 3 site hosted with Digital Ocean (Serverpilot set-up) with the DNS routed through Cloudflare.</p>

<p>The client has experienced issues uploading large ZIP files to (c140MB), returning a 413 error. After updating the PHP conf to enable larger files and tweaked the Nginx conf realised that the issue was with Cloudflare file upload limit.</p>

<p>Having set up a subdomain for the site to bypass Cloudflare we are now getting 500 errors in the browser console when trying to upload large files through the Craft control panel:</p>

<pre><code>POST https://admin.site.com/index.php?p=admin/actions/assets/save-asset 500
</code></pre>

<p>There are no errors in the server logs and nothing showing up in the Craft debug toolbar.</p>

<p>Any suggestions on debugging and resolving this issue or on what might be causing the 500 error?</p>

CC BY-SA 4.0
2018-11-14T21:58:09.057Z
You're positive that Cloudflare isn't getting involved on the admin.site.com requests?  I ask because why would you need to increase the Cloudflare file upload limit if it weren't? The 500 ISE has to be originating from _somewhere_.  If it were Craft, it would be in Craft's logs, but I suspect it's coming from something external (nginx, Cloudflare, etc.) and they'll have their own logging mechanisms.
Brad Bell
CC BY-SA 4.0
2018-11-14T22:11:32.857Z
Thanks Brad - set up subdomain to bypass Cloudflare which is why getting 500 error now rather than the 413 error. Flummoxed why nothing turning up in Craft logs or on server. Is there any way can debug the error from the above POST request that is turning up in the browser console?
Cole Henley
CC BY-SA 4.0
2018-11-14T23:34:48.257Z
Ahh, misunderstood that part - sorry.  If you check the that request in the network tab, then click the response tab, does it come back with anything?
Brad Bell
CC BY-SA 4.0
2018-11-15T08:07:23.383Z
Hmmm, seems to be an Nginx error. Will investigate further but strange nothing turning up in logs … 

`<html>
<head><title>500 Internal Server Error</title></head>
<body>
<center><h1>500 Internal Server Error</h1></center>
<hr><center>nginx</center>
</body>
</html>`
Cole Henley
<craft3><assets><error><upload><server>
Large file upload, 500 server error
# Large file upload, 500 server error

(Asked by: username_0 on 2018-11-13)

We've a Craft 3 site hosted with Digital Ocean (Serverpilot set-up) with the DNS routed through Cloudflare.
The client has experienced issues uploading large ZIP files to (c140MB), returning a 413 error. After updating the PHP conf to enable larger files and tweaked the Nginx conf realised that the issue was with Cloudflare file upload limit.
Having set up a subdomain for the site to bypass Cloudflare we are now getting 500 errors in the browser console when trying to upload large files through the Craft control panel:
POST https://admin.site.com/index.php?p=admin/actions/assets/save-asset 500

There are no errors in the server logs and nothing showing up in the Craft debug toolbar.
Any suggestions on debugging and resolving this issue or on what might be causing the 500 error?

**Tags:** craft3, assets, error, upload, server

> **Comments:**
> **username_1**: You're positive that Cloudflare isn't getting involved on the admin.site.com requests?  I ask because why would you need to increase the Cloudflare file upload limit if it weren't? The 500 ISE has to be originating from _somewhere_.  If it were Craft, it would be in Craft's logs, but I suspect it's coming from something external (nginx, Cloudflare, etc.) and they'll have their own logging mechanisms.  
> **username_0**: Thanks Brad - set up subdomain to bypass Cloudflare which is why getting 500 error now rather than the 413 error. Flummoxed why nothing turning up in Craft logs or on server. Is there any way can debug the error from the above POST request that is turning up in the browser console?  
> **username_1**: Ahh, misunderstood that part - sorry.  If you check the that request in the network tab, then click the response tab, does it come back with anything?  
> **username_0**: Hmmm, seems to be an Nginx error. Will investigate further but strange nothing turning up in logs …   `<html> <head><title>500 Internal Server Error</title></head> <body> <center><h1>500 Internal Server Error</h1></center> <hr><center>nginx</center> </body> </html>`  

---

## 0 answers

