12 days ago
Hi,
I've tried numerous times over the past day to deploy one of the WordPress templates into my account.
I usually pick the template with the 2000+ installs and "100% success" but tbh none of them work for me. I've tried working with the agent to fix the issue and we always go around in circles repeating the same things, getting nowhere.
It starts off with Forbidden when I attempt to access the WordPress "Primary" frontend (despite Primary and the MariaDB deploying successfully), and then after the agent tries a few things we end up with "Application failed to respond"
Thanks,
Steve
Environment: production
Issue: WordPress template deployments consistently fail with "Apache/2.4.67 Configuration error: More than one MPM loaded" and "Application failed to respond" errors, even after multiple fresh deployments and template attempts over the past 24 hours.
Services affected: Primary (WordPress), MariaDB
1 Replies
12 days ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • 12 days ago
12 days ago
Hi! It seems that you are facing common issue with WordPress on Railway, here is the solution from previous bounties - https://station.railway.com/questions/more-than-one-mpm-loaded-error-on-php-8-9c836859#g4q1
You have few options to deal with it:
- In your WordPress service settings on Railway set the start command to "/bin/bash -c "a2dismod mpm_event mpm_worker || true && a2enmod mpm_prefork && apache2-foreground""
- Use a Dockerfile fix:
CMD ["bash", "-lc", "\
set -eux; \
a2dismod mpm_event mpm_worker || true; \
rm -f /etc/apache2/mods-enabled/mpm_event.* /etc/apache2/mods-enabled/mpm_worker.* || true; \
a2enmod mpm_prefork; \
exec apache2-foreground \
"]