Fix 504 Gateway Timeout on GARMTECH Hosting

A 504 Gateway Timeout means the web server did not get a response from the backend in time. On GARMTECH hosting this is usually caused by a slow PHP script, a long database query, a heavy import, or a request waiting for an external API.

Step 1: Identify where the timeout happens

• Only one page (for example /wp-admin/, checkout, an import page) → likely a specific plugin/theme/script.
• All pages → possible PHP crash, high load, misconfiguration, or a global outage (less common).
• Only sometimes → usually performance/overload, external API slowness, or traffic spikes.

Step 2: Check your website error logs in Plesk

1. Log in to Plesk from My.GARMTECH.
2. Open the affected domain.
3. Go to Logs.
4. Look for entries around the time of the 504 error (PHP fatal errors, memory limit errors, database connection issues).

Step 3: Typical causes and fixes

WordPress plugin/theme causes long execution

• Temporarily disable the last updated plugin (or theme) and re-test.
• If you cannot access wp-admin, disable a plugin via files:
  1. Plesk → Files → httpdocs/wp-content/plugins/
  2. Rename the plugin folder (example: plugin-name → plugin-name.disabled).

PHP execution time is too low for the task

Long imports and backups may need higher limits.

• Plesk → domain → PHP Settings
• Increase max_execution_time (example: 120–300 seconds) and memory_limit if needed.
• Save and test again.

Heavy admin tasks (imports, page builders, WooCommerce)

• Run big imports in smaller batches.
• Disable non‑essential plugins during the import.
• Avoid running multiple heavy tasks at the same time (import + backup + updates).

External API / slow third-party service

If your site calls external APIs (payment gateways, shipping providers, CRM), a slow external response can cause timeouts.

• Temporarily disable the integration plugin and re-test.
• Check if the 504 happens only on pages that trigger the integration (checkout, webhooks, sync pages).

Step 4: Quick “is it my browser?” check

• Open the page in an incognito/private window.
• Try from a different network (mobile internet).

When to escalate

If the problem is repeatable and you cannot find the cause, prepare:

• The exact URL that triggers 504.
• Time of the error (with time zone).
• Relevant log lines from Plesk (Logs).
• What changed shortly before the issue started (plugin updates, migration, DNS/SSL changes).