How to fix server error on Adobe Commerce (Magento)

Steps for Adobe Commerce (Magento)

1. SSH into your server and tail the application log: tail -f var/log/exception.log and var/log/system.log — these show the exact PHP exception causing the 500.
2. Also check your web server error log (Apache: /var/log/apache2/error.log; Nginx: /var/log/nginx/error.log) for upstream PHP-FPM or out-of-memory errors.
3. Disable recently installed extensions via the Admin panel at Stores > Configuration > Advanced > Advanced > Disable Modules Output, or via bin/magento module:disable Vendor_Module.
4. Run bin/magento setup:upgrade and bin/magento cache:flush from the CLI to clear stale configuration after any module change.
5. If the error is theme-related, switch to the Luma (default) theme via Content > Design > Configuration > [store view] > Applied Theme to isolate it.
6. Increase PHP memory if needed in php.ini (memory_limit = 756M) or in .htaccess for Apache environments.
7. After the fix, submit the URL in Google Search Console > URL Inspection > Request Indexing.

What is server error?

An HTTP 500 (or any 5xx) response means your web server encountered an error and could not deliver the page — instead of your store content, visitors and search-engine crawlers receive an error message. Common culprits include broken app/plugin code, a crashed database connection, exhausted server memory, a misconfigured hosting environment, or a recent theme/code change that introduced a bug. Unlike a 404 ("page not found"), a 5xx error tells crawlers the page should exist but the server failed to produce it.

Google explicitly drops URLs from its index when they persistently return 5xx errors — your products, categories, and blog posts simply disappear from search results, costing you organic traffic and revenue. Even intermittent 5xx errors waste your crawl budget: Googlebot retries and eventually de-prioritises your site, slowing the indexing of new and updated pages. Shoppers who land on a broken page immediately leave, driving up bounce rates and signalling poor quality to both users and search engines. If high-revenue pages stay broken long enough, recovering their rankings can take weeks or months even after the fix.

See the complete Server error guide for every platform and the full background.