​

Configuration for File Upload Limits

​

Problem

​

Root Cause

​

Solution

​

1. Configuration Files Updated

​

/public/.htaccess

php_value upload_max_filesize 10M
php_value post_max_size 10M
php_value max_execution_time 300
php_value max_input_time 300

​

/public/.user.ini

upload_max_filesize = 10M
post_max_size = 10M
max_execution_time = 300
max_input_time = 300
memory_limit = 256M

​

2. If the Above Doesn’t Work

​

For Apache with mod_php:

upload_max_filesize = 10M
post_max_size = 10M
max_execution_time = 300
max_input_time = 300
memory_limit = 256M

sudo service apache2 restart

​

For Nginx with PHP-FPM:

php_admin_value[upload_max_filesize] = 10M
php_admin_value[post_max_size] = 10M
php_admin_value[max_execution_time] = 300
php_admin_value[max_input_time] = 300
php_admin_value[memory_limit] = 256M

sudo service php8.x-fpm restart
sudo service nginx restart

​

For Shared Hosting:

1. Contact your hosting provider to increase the limits
2. Use the .user.ini file we’ve created (some hosts support this)
3. Or use a php.ini file in your public directory (check with your host if this is supported)

​

3. Verification

<?php
phpinfo();
?>

• upload_max_filesize: should be at least 10M
• post_max_size: should be at least 10M
• max_execution_time: should be at least 300
• memory_limit: should be at least 256M

​

4. Laravel Configuration

• /app/Http/Controllers/Eventos/EventosController.php

'urlHeaderImage' => 'nullable|file|mimes:jpeg,png,jpg,gif,svg|max:5120',
'urlFooterImage' => 'nullable|file|mimes:jpeg,png,jpg,gif,svg|max:5120',
'urlThumbnailImage' => 'nullable|file|mimes:jpeg,png,jpg,gif,svg|max:5120',

​

5. Image Dimensions Updated

• Header: 1200×600 (previously 1200×300)
• Footer: 1200×600 (previously 1200×100)

​

6. Error Messages Translated

• /resources/lang/es/validation.php
• /lang/es/validation.php

​

Testing

1. Clear Laravel’s cache: php artisan cache:clear
2. Clear config cache: php artisan config:clear
3. Restart your web server
4. Try uploading an image between 4-5MB

​

Troubleshooting

1. Check your server’s error logs
2. Verify PHP configuration with phpinfo()
3. Check disk space on your server
4. Verify folder permissions (storage folder should be writable)
5. Check if there are any Nginx/Apache body size limits:
   • For Nginx: client_max_body_size in nginx.conf
   • For Apache: LimitRequestBody directive

​

Notes

• The PHP limits (10M) are set higher than Laravel’s validation (5M) to ensure uploads succeed
• Always test in a staging environment before deploying to production
• Monitor your server’s performance after increasing these limits

​

Laravel Cloud (production)

• public/.htaccess php_value directives are not applied (no Apache mod_php).
• public/.user.ini may or may not be honored depending on the PHP-FPM pool; do not rely on it alone.
• HTTP 413 on PUT /events/config/basic_info/{id}/update-general-aspect is usually thrown by Laravel’s global ValidatePostSize middleware when Content-Length exceeds PHP post_max_size, before EventosController::updateGeneralAspect runs. The generic Symfony error page (“Oops! An Error Occurred”) is a symptom of that early rejection.
• These upload rejections are not stored in MySQL (failed_jobs, communication_logs, etc. will not show them).

​

How to confirm in Laravel Cloud logs

1. Open the Laravel Cloud dashboard for the production environment.
2. Go to Logs.
3. Filter around the incident time for:
   • Access logs: update-general-aspect with status 413
   • Application logs: PostTooLargeException or The POST data is too large
4. Optional: use the Laravel Cloud logs API with an organization API token (LARAVEL_CLOUD_API_TOKEN locally).

​

Application-side mitigations (implemented)

• Friendly redirect when PostTooLargeException is thrown (bootstrap/app.php).
• Client-side checks in the event design form (5 MB per image, combined cap).
• If uploads still fail near 5–8 MB after deploy, open a Laravel Cloud support ticket to raise post_max_size / proxy body limits for the environment.