Request entity too large

Hi,

While trying to update the product with the uploaded video, I encountered the following error:

Request Entity Too Large

This means the video file size exceeds the current upload limits set by the server.

To resolve this and allow the video upload to work properly, you (or your hosting provider) will need to increase a few server settings.

If you’re using cPanel:

1. Log into your cPanel
2. Go to Select PHP Version > Options
3. Set the following values:

upload_max_filesize = 128M
 post_max_size = 128M
 memory_limit = 256M

If you’re unsure how or don’t have access

Hello,

Please increase the following PHP limits for my hosting account:

upload_max_filesize = 128M
post_max_size = 128M
memory_limit = 256M

Thank you!

Once these limits are updated, the video upload should work without any issues.

Let me know once it’s done or if you need help with anything.

Best regards,

Thanks for sharing that you’re still experiencing the issue.

Even if your upload_max_filesize, post_max_size, and memory_limit values are set correctly in PHP, some hosting environments (especially NGINX-based ones) also enforce their own upload limits separately from PHP.

If you’re using NGINX, you’ll also need to check or ask your hosting provider to update this directive in the NGINX config:

client_max_body_size 128M;

You can include this in your NGINX config (usually in nginx.conf) or ask your hosting support to apply it for you.

Let me know which server stack you’re using (Apache, NGINX, LiteSpeed, etc.) 

Hi Marc,

Thanks for the detailed info – that helps a lot.

From what you’re describing, the issue is likely not with the video upload itself (since 30MB files attach just fine), but rather with the product update/save request, which may still be exceeding a configured limit somewhere else in the stack.

A few things to consider:

1. Nginx directive override: If client_max_body_size is being re-written on NGINX restart, it’s likely managed by a config management tool or panel (like Plesk, cPanel, or a custom template system). You may want to check:
   • If you’re using a control panel, it may have its own upload limit settings that override manual config edits.
   • The directive should ideally be set only once – if it’s defined in two places, NGINX might throw a warning or ignore one of them.
2. Try moving client_max_body_size to the http block in your global nginx.conf (not per vhost), and remove duplicates from server blocks if possible. That way it will apply to all virtual hosts uniformly and avoid conflicts.
3. Payload size during save: Some WooCommerce/product pages can generate large POST data during save (especially with large video preview URLs, metadata, or multiple attachments). Even with high upload_max_filesize, the full POST payload might still hit a limit.
   In this case, check:
   • fastcgi_buffers and fastcgi_buffer_size (if using FastCGI)
   • Whether any security module (e.g., ModSecurity) is interfering
   • Whether a reverse proxy (Cloudflare, etc.) is truncating large requests
4. Just to isolate the problem, could you try:
   • Saving a product with the same video but minimal other content (no long description, no other media) – does the error still occur?
   • Temporarily removing the video and updating the product – just to confirm whether it’s related to the video presence in metadata, not the file upload itself

Let me know and I’ll be happy to help dig deeper.

I’m really glad to hear your issue is resolved -that’s great news! I hope my suggestions helped you along the way.

If you have a moment, it would mean a lot to me if you could leave a review for the plugin. Positive feedback really helps me keep improving and supporting it.

Here’s the link to leave a review: https://wordpress.org/support/plugin/video-wc-gallery/reviews/?filter=5

Thanks again and don’t hesitate to reach out if you need anything else!