Adobe Commerce site down troubleshooter

a. YES – If you checked Adobe Commerce Status, and it showed an issue, open a Support Ticket for further investigation.
b. NO – If you checked Adobe Commerce Status, and it did not show an issue, proceed to Step 2.

a. YES – If you checked Fastly Status and it showed an issue, open a Support Ticket for further investigation.
b. NO – If you checked Fastly Status and it did not show an issue, proceed to Step 3.

To check error codes in Firefox: Click the Open Menu icon > Web Developer > Toggle Tools > Network tab > All filter > Status column. To check error codes in Chrome: Click the Open Menu icon > More Tools > Developer Tools > Network tab > All filter > Status column.

a. YES – Open a Support Ticket for further investigation.
b. NO – Proceed to Step 4.

a. Error Code 500 – Check log of /var/log/platform/. If this data does not present the issue to you, you can open a Support Ticket and include the troubleshooting information you have so far for further investigation.

b. Error Code 503 – Check log of var/reports. If this data does not present the issue to you, you can open a Support Ticket and include the troubleshooting information you have so far for further investigation.

c. Error Code 404 - Run the following query: SELECT f.flag_data->>'$.current_version' as flag_version, (su.id IS NOT NULL) as update_exists FROM flag f LEFT JOIN staging_update su ON su.id = f.flag_data->>'$.current_version' WHERE flag_code = 'staging'; If the query returns a table, where update_exists value is “0”, refer to the Error 404 on all pages, storefront and Admin, due to Content Staging issue article. In all other cases proceed to Step 5.

d. Other Error Codes – Proceed to Step 5.

a. YES – Proceed with steps for Checking for DDOS attacks from CLI.
b. NO – Check logs of /var/log/exception.log and /var/log/deploy.log, and if this data does not present the issue to you, proceed to Step 6.

a. YES – Proceed to Step 13.
b. NO – Proceed to Step 7.

a. YES – Proceed with steps for checking Elasticsearch.
b. NO – Proceed to Step 8.

a. YES – Proceed with Checking slow queries and Processes taking too long in MySQL and checking your query structure in this MySQL query tutorial.
b. NO – Proceed to Step 9.

a. YES – Proceed with consulting the Checking static content article.
b. NO – Proceed to Step 10.

a. YES – Proceed with consulting Common PHP Fatal Errors and solutions.
b. NO – Proceed to Step 11.

a. YES – Proceed with steps to verify Redis is running and for Redis troubleshooting.
b. NO – Proceed to Step 12.

a. YES – If your Index is locked by another process, consult Index is locked by another process. If you have other Indexer errors, please open a Support Ticket for further investigation.
b. NO – Open a Support Ticket for further investigation.

a. YES – Proceed to consult General custom module troubleshooting help.
b. NO – Proceed to Step 14.

a. YES – Proceed with checking your MySQL error in this MySQL server error message reference.
b. NO – Proceed to Step 15.

a. YES – Proceed to consulting Applying a patch takes your site down.
b. NO – Proceed to Step 16.

a. YES – Proceed with checking your MySQL error in this MySQL server error message reference.
b. NO – Proceed to Step 17.

a. YES – Proceed with checking for MySQL deadlocks in this Deadlocks in MySQL article.
b. NO – Open a Support Ticket for further investigation.