.How do I fix “504 Gateway Timeout” during Shopware 6 installation?
Most Common Cause
A 504 Gateway Timeout during Shopware 6 installation usually means PHP, Nginx, Apache, or your hosting proxy timed out while Composer dependencies, database migrations, or asset builds were still running. In most cases, increasing PHP execution limits and web server timeout values fixes it immediately—especially on shared hosting or low-memory VPS setups.
Quick Diagnostic — check these first
Rules out: Composer or migration crashes caused by low RAM
Rules out: Reverse proxy or FastCGI timeout failures
Rules out: Browser session and web request timeout limits
Rules out: Partial Composer installs and cache write failures
Rules out: Fatal PHP errors hidden behind the timeout page
Cause 1 PHP execution limits too low
Shopware installation runs heavy Composer operations, plugin checks, migrations, and cache generation. Small PHP limits often kill the request before installation completes.
Fix: Increase memory_limit to at least 512M,
set max_execution_time to 300 or higher, and restart PHP-FPM. On VPS setups, 1GB memory works much
better for first-time installs.
Cause 2 Nginx or proxy timeout reached
Even if PHP is still working, Nginx, Apache, Cloudflare, or another reverse proxy can terminate the request after 60 seconds and return a 504 page.
Fix: Increase values like
fastcgi_read_timeout, proxy_read_timeout, or Apache Timeout settings to
300 seconds or higher. Then reload the web server configuration before retrying the installer.
Cause 3 Browser installer timing out
The web installer is convenient, but slower servers often struggle during dependency installation and initial cache warm-up.
Fix: Install Shopware from the command line instead. Run Composer install commands and database setup through SSH. CLI execution avoids browser request limits and is far more stable on staging or production servers.
Cause 4 Slow database or low server resources
Entry-level hosting plans often don’t have enough CPU or I/O performance for Shopware installation tasks. Database migrations can stall long enough to trigger gateway timeouts.
Fix: Upgrade temporary server resources, disable
unnecessary background services, and retry the installation after clearing incomplete cache and
var/cache files. We see this constantly on shared hosting plans marketed as “Shopware ready.”
Related Answers
Was this answer helpful?
Your feedback helps us improve our answers.
Still need help?
Talk to our Shopware experts
We've handled GDPR/CCPA compliance for dozens of EU & US Shopware stores.