New One-click installs: WordPress, WooCommerce, Mage-OS and PrestaShop on any server

See the plans
Troubleshooting1 min readUpdated

500 errors and white pages: read the logs

A 500 is the store's own code failing. Where to find the error message for Magento, WordPress and Laravel.

A 500 or a white page means the store's PHP code stopped with an error. The error message is in a log; once you have it, the fix is usually clear.

Logs tab: choose the application, the log and how many lines.
Logs tab: choose the application, the log and how many lines.
PlatformWhere to look
Every applicationLogs tab, PHP errors and Web errors.
MagentoLogs tab, Magento exception.log and system.log. A page saying Error log record number points to a report file in var/report.
WordPressTurn on WP_DEBUG_LOG and read wp-content/debug.log.
Laravelstorage/logs/laravel.log.

Usual causes

  • Code uploaded without running compile and static deploy (Magento production mode).
  • An extension that does not support the PHP version.
  • memory_limit reached on a heavy page.
  • Wrong file uploaded or a missing file after a partial upload.

Did this solve it? If not, tell us what you see and we look at your server.

Open a ticket

Keep reading

All 9 guides
The site is down: first checksFive minutes of checks that tell you whether it is DNS, the server, one service or the store itself.1 min readOut of memory and swappingWhen the Memory graph is full and swap grows: what uses the memory and how to bring it back to normal.1 min readVisitors get 429, 444 or a 'Checking your browser' pageWhat the protection answers mean, how to tell a real customer from a bot, and how to let someone through.1 min read

Still stuck? Ask a person.

Tickets go straight to the engineers who run ShopWhizzy servers. Tell us the store, what you see and when it started, and we take it from there.

Open a ticket Help center