Blog Sections Open
Handling 502 Errors When MultiPhotos Uploads Large Batches of Images
Large gallery uploads can fail long before the CMS finishes processing them if the host times out or the image pipeline is too heavy.
A 502 Bad Gateway during a large MultiPhotos upload is usually not a gallery configuration issue. It is a server timeout or upstream processing failure caused by too many images being handled in one request.
What usually triggers it
- low FastCGI or proxy timeout values
- image processing that takes too long per request
- memory spikes during thumbnail creation
- uploading too many large files in one batch
What helps in practice
- reduce the batch size and test with smaller groups first
- increase execution time, memory, and proxy timeout limits where possible
- generate thumbnails asynchronously or in smaller chunks
- pre-optimize source images before upload
If the tool deletes the previous batch while the next one fails, the workflow itself needs to be rethought. Large media imports are much safer when the upload and processing steps are separated.
Fixing Blank Pages After Scheduled Unpublish Events with Cache Enabled
Why scheduled resource state changes can leave stale empty pages in cache and how to handle the cache layer correctly.
Fixing Old URLs That Persist After Changing Resource Aliases
Why Evolution CMS can keep redirecting to stale aliases after a slug change and how to clear the right layers.