​

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 (producción)

• Las directivas php_value de public/.htaccess no se aplican (no hay Apache mod_php).
• public/.user.ini puede o no aplicarse según el pool PHP-FPM; no depender solo de él.
• El 413 en PUT /events/config/basic_info/{id}/update-general-aspect suele lanzarlo el middleware global ValidatePostSize cuando Content-Length supera post_max_size de PHP, antes de ejecutar EventosController::updateGeneralAspect. La página genérica de Symfony (“Oops! An Error Occurred”) indica ese rechazo temprano.
• Estos rechazos no quedan registrados en MySQL (failed_jobs, communication_logs, etc.).

​

Cómo confirmarlo en los logs de Laravel Cloud

1. Abre el dashboard de Laravel Cloud del entorno de producción.
2. Ve a Logs.
3. Filtra en la hora del incidente por:
   • Access logs: update-general-aspect con estado 413
   • Application logs: PostTooLargeException o The POST data is too large
4. Opcional: API de logs de Laravel Cloud con un token de organización (LARAVEL_CLOUD_API_TOKEN en local).

​

Mitigaciones en la aplicación (implementadas)

• Redirección amigable ante PostTooLargeException (bootstrap/app.php).
• Validación en el formulario de diseño del evento (5 MB por imagen, tope combinado).
• Si tras el deploy siguen fallando cargas cerca de 5–8 MB, abrir ticket con Laravel Cloud para subir post_max_size / límites del proxy del entorno.