502 Bad Gateway

April 17, 2025

A 502 Bad Gateway error right after a reboot usually means a service your web server relies on didn’t start properly — such as Nginx (if you use Engintron), Apache, PHP-FPM, or MySQL.

Let’s troubleshoot this step by step:

---

✅ Step 1: Check Apache & PHP-FPM status

Run:

If any of them is inactive or failed, restart it:

If you’re using Engintron, it adds Nginx as a reverse proxy:

---

✅ Step 2: Restart cPanel services

Sometimes restarting all WHM/cPanel-related services helps:

You can also try:

---

✅ Step 3: Check what is listening on port 80 and 443

Make sure httpd (Apache) or nginx (if using Engintron) is bound to those ports.

---

✅ Step 4: Look for actual error logs

Check Apache error logs:

If using Nginx (Engintron):

---

✅ Step 5: Check MySQL is running

If your websites use databases (e.g. WordPress), check MySQL:

If it’s not running:

---

✅ Step 6: Check Engintron Panel (if installed)

In WHM:

From there, use the “Restart Nginx + PHP-FPM + MySQL” button.

---

✅ Step 7: Check Firewall/IP blocks

Run:

To check if your own IP is blocked (if using CSF/LFD).

---

Let me know what you find from the service status or logs, and I’ll help pinpoint the exact cause. If you drop the output here, I can review it immediately.