[MPG] 500 – Internal Server Error

This error is very common if your source file is too large to process. The general solution is to increase the "memory_limit" parameter accordingly or split your dataset into multiple MPG projects.

There is no particular size of the memory_limit that we recommend as it solely depends on your data source file. For instance, if your data source file has only 500 records, even 1MB should be enough. However, if you have 100 columns and 150,000 rows, your memory_limit would need to be 256MB or even 512MB.

You can increase the PHP memory limit in the  php.ini file by setting:

memory_limit = 512M

If you don’t have access to php.ini, you can add the following line to your WordPress site's wp-config.php file:

define('WP_MEMORY_LIMIT', '512M');

If you are not comfortable modifying the limit yourself, please contact your hosting provider to request an increase.

A large import can also stop because it takes longer than PHP allows, rather than because it runs out of memory. If your error log points to a maximum execution time error instead, ask your host to raise max_execution_time as well:

max_execution_time = 300

📝 Note: When an import is interrupted, MPG keeps a rebuild marker on the project for five minutes and will not rebuild the index again until it clears. Wait five minutes before retrying. If you see the message Can't rebuild project index., see A project cannot be saved / URLs disappear from the project.