Oh man, http error 413 is the worst! Had this exact issue last week with Nginx. Turns out the `client_max_body_size` was set way too low by default.
You gotta edit your Nginx config (usually in `/etc/nginx/nginx.conf` or the site-specific config) and add or update:
```
client_max_body_size 100M;
```
(or whatever size you need).
Don’t forget to restart Nginx after! `sudo systemctl restart nginx`
If you’re on Apache, look for `LimitRequestBody` in your config.
Also, pro tip: Check your PHP settings too if you’re using it—`upload_max_filesize` and `post_max_size` can sneakily block big uploads.
You gotta edit your Nginx config (usually in `/etc/nginx/nginx.conf` or the site-specific config) and add or update:
```
client_max_body_size 100M;
```
(or whatever size you need).
Don’t forget to restart Nginx after! `sudo systemctl restart nginx`
If you’re on Apache, look for `LimitRequestBody` in your config.
Also, pro tip: Check your PHP settings too if you’re using it—`upload_max_filesize` and `post_max_size` can sneakily block big uploads.
