A 502 Bad Gateway on a WordPress site running behind Nginx means Nginx could not obtain a usable response from its upstream, normally PHP-FPM. Start with the Nginx error log, then compare the configured fastcgi_pass target with PHP-FPM’s listen target. A missing socket or stopped service needs a listener fix; a timeout usually needs PHP-FPM, database, cache, or WordPress workload investigation rather than a larger Nginx timeout.
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
The safest workflow is: reproduce the error once, record its scope and time, read Nginx and PHP-FPM logs for that timestamp, verify the upstream listener, make the smallest configuration or application change, run nginx -t, and reload only after the test succeeds.
As an Amazon Associate I earn from qualifying purchases.
Recommended Free Tools
What a 502 means in a WordPress-Nginx stack
Nginx is the gateway in this setup. It accepts the browser request and, for a PHP URL, passes the request to an upstream process. WordPress code is usually executed by PHP-FPM through either a Unix-domain socket such as /run/php/php8.2-fpm.sock or a TCP listener such as 127.0.0.1:9000. Nginx then waits for PHP-FPM to return a valid response header and body.
The 502 page only says that this exchange failed. It does not identify whether PHP-FPM is stopped, the socket path is wrong, permissions prevent access, a worker crashed, or a dependency made the request fail. BOA’s troubleshooting documentation describes the same pattern for gateway errors: the browser-facing status is reported by Nginx but is usually caused downstream by PHP-FPM, the database, a cache service, or the application itself.
#1 Best Overall
- BLUE LIGHT BLOCKING GLASSES: Our blue light glasses for women boast UV400 protection, blocking harmful blue rays from computer screens. With these bluelight glasses women, you can enjoy gaming, reading, or watching TV with no worries of eye strain.
- EYE RELIEF: Our blue light glasses are engineered to reduce blurry vision or strain caused by prolonged screen time. These womens blue light glasses aid in better sleep by preventing blue light from disrupting your natural sleep cycle, helping you fall asleep faster and enjoy a more restful night's sleep, making them the perfect christmas present.
- COMFORTABLE: Crafted from durable material, our trendy blue light glasses for woman or blue light glasses men ensure long-lasting comfort. The high-transmittance lenses accessories, gamer gifts for men, help keep your eyes relaxed. Perfect stocking stuffers, gifts for gamers men, christmas gifts for men, halloween costumes.
- LIGHTWEIGHT: These clear blue light glasses feature a lightweight frame, meaning they’ll stay comfy for long-term wear. Perfect as blue blockers glasses for women or mens blue light glasses, these non-prescription fake glasses for men can be worn throughout the day. The blue light blocking glasses women feature polycarbonate HD lenses, which are anti-reflective and restore true color.
- WORRY-FREE PURCHASE: If you experience any issues, our support team is ready to assist you quickly. These are the perfect costume glasses for cosplay dressing up.
A 504 is related but not identical: it generally means Nginx waited past its timeout. In practice, the log wording and timing values are more useful than the status code alone.
Capture the failure before changing configuration
Reproduce the problem once, not dozens of times. Write down the complete URL, HTTP method, UTC or server-local time, response status, and whether the failure affects the whole site or one route. Note whether the browser, WordPress dashboard, REST API, cron request, or an external health check is reporting it.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
- Every URL fails: suspect Nginx-to-PHP-FPM connectivity, a stopped service, a broken listener, permissions, or host-wide resource pressure.
- Only PHP URLs fail: inspect the FastCGI location and PHP-FPM first.
- Only
/wp-admin, REST, oradmin-ajax.phpfails: investigate the specific plugin, theme, scheduled task, or request workload after confirming the backend is reachable. - Failures are intermittent: correlate timestamps with worker exhaustion, memory pressure, process restarts, database latency, or cache-service failures.
Keep a copy of the current Nginx configuration before editing it. A simple timestamped copy of the relevant server block gives you a known rollback point if a change introduces a second problem.
Read Nginx logs first
Find the error log
NGINX documentation notes that the error-log path depends on the installation. On many Linux packages it is /var/log/nginx/error.log; a virtual host may define a different file. Check the active configuration if that path is not present:
nginx -T 2>/dev/null | grep -E 'error_log|access_log'Then inspect entries around the recorded failure time:
sudo tail -n 100 /var/log/nginx/error.logFor a live reproduction, follow the file in one terminal while making one request in another:
sudo tail -f /var/log/nginx/error.logDo not treat the generic HTML 502 page as a diagnosis. The error-log line immediately before or after it normally contains the actionable signature.
Rank #2
- WINDEX GAMING WIPES: effortlessly clean all your gaming gear and gaming electronics in one easy step with our new Windex Gaming Wipes
- AMMONIA FREE: our ammonia-free formula is safe to use on all of your favorite gaming equipment like consoles, headsets, controllers, screens, keyboards, and more
- PRE-MOISTENED WIPES: each wipe instantly removes dust, dirt, and stubborn smudges and fingerprints leaving a streak-free shine
- ANTI-STATIC: great for cleaning and wiping down your gaming gear and electronics leaving behind no visible residue
- COMPACT RESEALABLE PACKAGE: store your pack of Windex Gaming Wipes anywhere in your home for whenever a quick and easy wipedown is needed
Use upstream timing fields when access logging provides them
NGINX exposes several variables that can be included in an access-log format: $upstream_connect_time, $upstream_header_time, $upstream_response_time, and $request_time. Their relationship helps separate connection failures from slow application work.
- Very small or zero connect time with a 502: Nginx may not have reached a usable listener, or the upstream failed before returning headers.
- Connect succeeds but header time is long: PHP-FPM accepted the request but PHP or a dependency is taking too long to produce headers.
- Response time ends abruptly: a worker may have crashed, been killed, or closed the connection before completing the response.
- High request time across many URLs: look for saturation, memory pressure, database latency, or cache failures instead of changing one WordPress route.
If your access log does not include these variables, the error log and PHP-FPM log can still establish the cause. Add timing fields only through a planned configuration change, validate it, and avoid replacing a production log format without preserving the existing fields.
Match the log signature to the next check
| Nginx message pattern | Most likely area | First check |
|---|---|---|
connect() failed or No such file |
Stopped PHP-FPM service, wrong socket path, missing socket, or permissions | Service state, pool listen, socket existence, and worker access |
upstream timed out |
Slow or saturated PHP-FPM/application work | Worker limits, memory, database and cache latency, and the affected request |
upstream sent too big header |
Response headers exceed the configured FastCGI buffers | Identify the endpoint and inspect unusually large cookies or headers before tuning buffers |
prematurely closed connection |
PHP fatal error, backend crash, forced termination, or process restart | PHP-FPM and PHP application logs at the same timestamp |
The wording is a triage tool, not proof of a single cause. Confirm it against the service state and correlated logs before making a change.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Verify PHP-FPM and its listener
Check that the service is running
Service names include the PHP version on many distributions. Debian and Ubuntu commonly use a name such as php8.2-fpm; other systems may expose php-fpm. List matching units if you are unsure:
systemctl list-units --type=service | grep -i fpmThen inspect the relevant unit and its recent messages:
sudo systemctl status php8.2-fpm
sudo journalctl -u php8.2-fpm --since '-30 min'Replace the unit name with the one installed on the server. A failed or repeatedly restarting service must be fixed before Nginx can deliver PHP responses. Check the PHP-FPM log configured by the package as well as the system journal; fatal errors, out-of-memory kills, and configuration parse errors often appear there.
Find the pool’s listen directive
PHP-FPM pools define the endpoint in a line beginning with listen =. Locate active pool files without assuming a particular PHP version:
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsRank #3
- Ergonomic & Adjustable Design: Fight "text neck" and improve your posture. Designed for comfort, it offers an adjustable height (7.1in-8.5in) (1.4in adjustable range) and angle (5°-85°) Please note: cell phone stand is only 9 inches tall—the length of a standard pencil
- Without blocking subtitles Perfect for office desk Tiktok Face Time Zoom video—this is the ultimate kitchen desk essential for phones! Perfect viewing experience while reducing neck back strain, A must-have for gamers streamers desk, and anyone who values both style and support!
- Sleek & Stable Design fits Otterbox Case: Say goodbye to bent cables, tangles, and tip-overs! LISEN’s stylish adjustable desk phone holder features a built-in charging hole and smart cable management, keeping your phone secure and your workspace clutter-free cool gadgets for men
- ANTI-SLIP DESIGN free hands: The under 10.00 items easy gadgets back and the bottom of this kitchen essentials for women are fully covered by anti-skid silicone, which LISEN stand up desk decor can provide maximum protection device from any scratches and slides
- Your Perfect Viewing Companion:If your product arrives damaged or breaks within 365 days, reach out to LISEN for a quick and hassle-free solution. Struggling with assembly, like tightening the screw? We’ve got your back! Your experience matters to us. (Product including: phone Holder stand*1, screw*1, hexagon screwdriver*1, specification*1)
sudo grep -R "^[[:space:]]*listen[[:space:]]*=" /etc/php /etc/php-fpm.d 2>/dev/nullThe result may be a Unix socket, for example /run/php/php8.2-fpm.sock, or a TCP address such as 127.0.0.1:9000. The Nginx fastcgi_pass value must match that target exactly. A different PHP version, a distribution-specific run directory, or a stale socket path is enough to produce a 502.
Confirm the socket or TCP port exists
For a Unix socket, check the path and ownership:
sudo ls -l /run/php/
sudo stat /run/php/php8.2-fpm.sockThe socket should exist while PHP-FPM is running. Its owner, group, and mode must allow the Nginx worker account to connect. The exact account varies by distribution; common names include www-data and nginx. Check the running worker account rather than guessing:
ps -eo user,group,comm | grep '[n]ginx'For a TCP listener, inspect listening sockets:
sudo ss -ltnp | grep -E ':9000|php-fpm'Do not expose PHP-FPM on a public interface merely to make the check pass. A local address such as 127.0.0.1 keeps the listener on the server; firewall and pool settings should reflect the intended trust boundary.
Make fastcgi_pass agree with PHP-FPM
Find the WordPress server block and its PHP location, often a block matching .php$. Display the loaded configuration to avoid editing an unused file:
Free tools Windows power users keep installed
One-click scans. No signup required.
sudo nginx -T 2>/dev/null | lessInside the active PHP location, compare the line with the pool value:
fastcgi_pass unix:/run/php/php8.2-fpm.sock;For TCP, the form is:
fastcgi_pass 127.0.0.1:9000;Use one form, not both. Correct the Nginx value or the pool configuration according to which endpoint is intended, and avoid changing unrelated rewrite rules while diagnosing a gateway error. If you change a pool’s socket path, make sure the runtime directory is created at boot and that any socket ownership settings still permit Nginx access.
Always test before reloading:
sudo nginx -tProceed only when the command reports a successful syntax and configuration test. If it fails, use the file and line number in the output, restore the rollback copy if necessary, and test again. A successful test does not prove that PHP-FPM is healthy; it only proves Nginx can parse the configuration.
Rank #4
- Easy Installation: Our gaming lights have been designed to enhance your entertainment experience. Simply position the led light bar next to your TV or game console to create a game room environment with ease. They come with USB power and a 60 inch cord for direct mounting and mobility
- Audio Syncing & Extensive Mode: The built-in high-sensitivity music sensor allows you to sync the TV led lights to your favorite music. Lights react and move to the beat of music, film and game audio, creating an incredible immersive sound and light experience – and all without the need for an additional hub. You can choose from 64+ patterns, including strobe, illusion, jump, energy, gradient, running, chasing, fluttering mode etc. Each mode can be applied to different scenes
- 64+ Chasing IC+RGB & W Effect: The independent control design of IC+RGB and white all-in-one multifunctional rgbw led bar lights monitor backlight allows you to easily switch the led lights for desk between IC+RGB and white to enjoy a variety of lighting effects, you can choose white lighting mode with high brightness for better illumination when working, etc. Choose IC+RGB lighting mode when you need to create an entertaining atmosphere for the light show, 16 million colours of Color changing rgb light bar let you dance to the beat and create a dynamic party atmosphere
- Dynamic and Dimmable Lights: 1%-full brightness free brightness adjustment gives you the flexibility to adjust dimmable led light bar for room decorations or a variety of occasions
- USB Powered: USB light bars for room can be powered by powernank, usb charger, TV, Monitor, laptop PC mainframe, making behind TV led lighting bar easy to install in any location.TV led lights are powered by the TV usb interface / PC mainframe, can be turned on/off synchronously with TV / PC
Reload without dropping existing connections:
sudo systemctl reload nginxImmediately retest the original URL and watch the error log. If the socket now connects but the request times out, move to workload analysis rather than reverting a correct listener fix.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Resolve an upstream timeout without hiding the cause
Determine whether the backend is slow or saturated
An upstream timed out entry means Nginx waited for a connection, response header, or response data longer than the relevant limit. A slow report, import, REST request, or uncached page can be legitimate but expensive; a full PHP-FPM pool can make even a simple homepage wait.
- Check PHP-FPM active, idle, and maximum worker counts in the pool status or service logs.
- Look for messages that the pool has reached its process limit or is repeatedly spawning and killing workers.
- Check memory and swap pressure at the failure time. The operating system may terminate PHP-FPM workers when memory is exhausted.
- Measure database latency and connection errors. WordPress requests often wait on MySQL-compatible database queries before PHP can send headers.
- Check the configured cache service, including Valkey or Redis where used, for restarts, refused connections, or slow commands.
- Compare the failing URL with a lightweight static file. If static content is fast while PHP is slow, keep the investigation on the upstream path.
BOA’s documentation specifically groups PHP-FPM, MySQL, Valkey/Redis, and application failures as downstream causes of Nginx gateway errors. That is why increasing fastcgi_read_timeout should not be the first response: it can leave more requests waiting, consume more workers, and turn a visible failure into resource exhaustion.
Change timeouts only for a measured workload
If logs show a known operation that consistently needs more time and PHP-FPM has sufficient capacity, adjust the smallest applicable timeout in the server or location block. Record the old value, make the change narrowly, run nginx -t, reload, and observe worker and memory usage. Do not use a large global timeout to compensate for an unknown database lock, plugin loop, or exhausted pool.
For an operation that should be asynchronous, redesign the task or schedule it outside the browser request instead of allowing an HTTP request to occupy a PHP-FPM worker indefinitely. The correct fix is workload-specific; the 502/504 page cannot tell you which timeout value is safe.
Handle “upstream sent too big header”
This signature means Nginx received response headers larger than its configured FastCGI buffering could hold. WordPress plugins that create unusually large cookies, redirect chains, or verbose authentication headers can trigger it, especially on dashboard or login routes.
First identify the endpoint and inspect its cookies and redirects. Remove the source of unnecessary header growth where possible. If the header size is expected and the server has adequate memory, tune the FastCGI buffer directives for the affected location rather than applying an unbounded global setting. Validate with nginx -t, reload, and retest the same request. Buffer increases consume memory per active request, so pair the change with capacity monitoring.
Best Value
- Compatible with Wide Screens - To ensure compatibility with the dual monitor mount, your each monitor must meet three conditions at the same time: First, computer screens size range: 13 to 32 inches. Second, screen weight range: 4.4 to 19.8 lbs. Third, the back of the monitor screen must have VESA mounting holes with a pitch of 75x75mm or 100x100mm.
- Regarding the compatibility with desks - Your desk must meet three conditions at the same time: First, desk material: Only wooden desks are recommended, plastic or glass desks cannot be used. Second, desk thickness range: 0.59" - 3.54". Third, the bottom of the desk should not have any cross beams or panels, as this will interfere with installation. We recommend carefully checking that your desk and monitors meets all above conditions before purchasing.
- Dual C-Clamp Hold - Worried your dual monitors might wobble or slip? Our upgraded base uses a larger platform plus a dual C-clamp structure to lock the dual monitor arm firmly to your desk. Each arm safely keeps your screens steady while you type, click and game—no shaking, no sliding, just a clean and secure setup you can trust every day. It also provides Grommet Mounting installation choice, both options ensure stable and secure fixation for your 0.59" - 3.54" desk.
- Full-Motion Adjustment For Comfortable View - Pull the screen closer when you’re deep in a spreadsheet, push it back to watch videos, or rotate to portrait for coding — moving everything smoothly with just one hand. The monitor stand offers +85°/-50° tilt, ±90° swivel and 360° rotation. Raise your monitor up to 15.75″ to support a healthy sitting posture. Whether you’re working from home, gaming through the night, or switching between video calls and documents, getting the screens to your natural line of sight helps relieve neck, shoulder and back strain so you can stay focused longer with less fatigue.
- Keep Your Desk Organized: By lifting both screens off the desktop, this dual monitor stand opens up valuable space for your keyboard, notebook, docking station or a simple, clutter-free work area. Built-in cable management guides wires along the arms, keeping cords out of sight and out of the way. Enjoy a tidy, modern workstation that looks as good as it feels to use.
Investigate a prematurely closed connection
When Nginx reports that the upstream closed the connection prematurely, PHP-FPM may have encountered a fatal PHP error, a worker crash, an out-of-memory kill, or a forced restart. Read the PHP-FPM and PHP error logs at the exact request time. A WordPress debug log, when already enabled under your site’s normal privacy policy, can identify a plugin or theme call that terminates execution.
Check whether the same process restart appears for unrelated URLs. Repeated restarts indicate service or host instability; a single route points more strongly to application code or input-specific processing. Roll back the most recent plugin, theme, PHP, or configuration change through your normal deployment process, then retest the original URL and one unrelated PHP URL.
When only WordPress admin or one endpoint returns 502
/wp-admin fails but the public site works
Confirm a simple public PHP page and the login page separately. If only dashboard requests fail, inspect the PHP-FPM log and the Nginx location handling /wp-admin. Recent plugin updates, dashboard widgets, background tasks, and expensive queries can exhaust workers or terminate a request. Disable or roll back the most recent change through a controlled maintenance procedure, then test the dashboard again. Keep a record of each change so you can restore unrelated extensions once the culprit is identified.
REST API or admin-ajax.php fails
These endpoints often carry plugin and editor workloads. Reproduce the failing action while watching Nginx, PHP-FPM, and application logs. Compare a small authenticated request with the failing action to determine whether the problem is endpoint-specific or account-wide. A timeout on one action calls for query, external-request, and worker analysis; a connection failure on all actions still points to the listener or service.
A scheduled task triggers the errors
Correlate the first 502 timestamp with scheduled-task execution and PHP-FPM restarts. Temporarily suspend the task through your established WordPress operations process, verify that normal requests recover, and then repair or split the task before re-enabling it. Do not leave a production task disabled without documenting the operational impact.
Check dependencies before changing Nginx
PHP-FPM can be running and accepting connections while WordPress still fails because a dependency is unavailable. Inspect database connection errors, slow queries, lock waits, cache-service health, filesystem permissions, and disk space. A full disk can prevent PHP sessions, cache files, or logs from being written; memory pressure can kill workers without changing the Nginx configuration.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware match- Database: correlate connection refusals, authentication errors, and latency with the failing request time.
- Cache: check whether the configured cache daemon is reachable and whether failures are blocking requests or merely disabling an optimization.
- Filesystem: verify free space and write permissions for WordPress uploads, temporary directories, PHP sessions, and log locations.
- Process limits: review PHP-FPM worker limits, operating-system file descriptors, and web-server connection limits together.
Fix the dependency or capacity bottleneck first. A larger Nginx timeout cannot make a failed database connection succeed.
Use Nginx debug logging only as a short escalation
NGINX documents that debug logging is disabled by default and requires a build compiled with debug support. When ordinary error and application logs do not explain the exchange, enable it temporarily with a directive such as:
error_log /var/log/nginx/error.log debug;Apply it only in a controlled window, after keeping a rollback copy and checking configuration syntax. Debug output can grow very large and affect performance. Reproduce the failure once, collect the relevant lines, restore the normal log level, run nginx -t, and reload. Leave debug logging enabled only as long as needed to answer a specific question about request routing or upstream communication.
Quick Recap
A low-risk decision path
| Observed scope or signature | Priority action | Change risk |
|---|---|---|
| All PHP URLs fail; socket missing or “connect() failed” | Restore PHP-FPM, correct the pool listener, or fix socket ownership; then validate and reload Nginx | Low when limited to the verified listener and service |
| Intermittent 502/504 with long upstream times | Analyze workers, memory, database, cache, and restarts before adjusting timeouts | Medium; capacity changes can affect the whole site |
| “Upstream sent too big header” on one route | Reduce cookie/header size or tune buffers only for the affected location | Medium; larger buffers consume per-request memory |
| “Prematurely closed connection” after a plugin or theme change | Correlate PHP logs, roll back the change, and retest a control URL | Low when the rollback is controlled |
| Only dashboard, REST, or AJAX fails | Isolate the endpoint’s plugin, theme, task, query, or input workload | Medium; disabling an extension can change site behavior |
Prevent the next gateway outage
- Keep the Nginx
fastcgi_passvalue and PHP-FPM poollistenvalue documented together, including the PHP version. - Monitor Nginx error rates, PHP-FPM worker utilization, process restarts, memory pressure, database latency, and cache availability.
- Retain enough Nginx and PHP-FPM log history to correlate an incident by timestamp.
- Test configuration changes with
nginx -tand retain a rollback copy before every reload. - Load-test expensive WordPress operations outside peak traffic and move long jobs out of synchronous browser requests when possible.
- Review plugin, theme, PHP, and server changes as deployments so an endpoint-specific failure has a clear rollback candidate.
- Keep debug logging off during normal operation and enable it only for a bounded investigation.
Final verification checklist
- Reproduce the original URL and record its status, method, scope, and timestamp.
- Read the Nginx error log and classify the exact upstream signature.
- Check PHP-FPM service health, pool listener, socket or TCP endpoint, and Nginx-worker access.
- Inspect PHP-FPM, PHP, WordPress, database, and cache logs for the same timestamp.
- Apply one narrowly scoped fix or rollback, keeping the previous configuration available.
- Run
nginx -t; do not reload after a failed test. - Reload Nginx, retest the failing request, and test an unrelated PHP URL.
- Watch logs and resource metrics long enough to confirm the fix is stable rather than a temporary disappearance.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
