{"id":2556,"date":"2026-03-02T11:40:29","date_gmt":"2026-03-02T11:40:29","guid":{"rendered":"https:\/\/ssblog.eu.enginyr.ing\/?p=2556"},"modified":"2026-03-02T11:47:00","modified_gmt":"2026-03-02T11:47:00","slug":"wordpress-502-bad-gateway-in-2026-ghidul-complet-de-depanare-si-rezolvare-directadmin-vps","status":"publish","type":"post","link":"https:\/\/www.serverspan.ro\/blog\/wordpress-502-bad-gateway-in-2026-ghidul-complet-de-depanare-si-rezolvare-directadmin-vps\/","title":{"rendered":"WordPress 502 Bad Gateway \u00een 2026: Ghidul complet de depanare \u0219i rezolvare (DirectAdmin + VPS)"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">O eroare WordPress 502 Bad Gateway \u00eenseamn\u0103 c\u0103 NGINX a primit cererea, a transmis-o c\u0103tre PHP-FPM pentru procesare \u0219i nu a primit niciun r\u0103spuns valid \u00eenapoi. Rezolvarea \u021bine aproape \u00eentotdeauna de una dintre cele \u0219apte situa\u021bii: PHP-FPM este oprit, calea socketului este gre\u0219it\u0103, poolul de workere FPM este epuizat, timeoutul FastCGI al NGINX este prea scurt, procesul a fost terminat de OOM killerul Linux, MySQL blocheaz\u0103 workere PHP, sau un firewall (inclusiv fail2ban) blocheaz\u0103 traficul de loopback. Acest ghid parcurge sistematic diagnosticarea fiec\u0103rei cauze, cu comenzi reale \u0219i c\u0103i specifice DirectAdmin, astfel \u00eenc\u00e2t s\u0103 nu ghice\u0219ti.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">\u00cenainte de orice: cite\u0219te logurile<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Nu atinge fi\u0219ierele de configurare \u00eenainte de a \u0219ti care este eroarea exact\u0103. Logurile \u00ee\u021bi vor spune precis cu ce categorie de 502 ai de-a face, iar s\u0103ritul peste acest pas pierde timp. Ruleaz\u0103 aceste trei comenzi \u00een ordine \u0219i cite\u0219te outputul cu aten\u021bie \u00eenainte de a trece la orice sec\u021biune de rezolvare.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># Logul de erori NGINX \u2014 \u00ee\u021bi arat\u0103 ce a v\u0103zut NGINX c\u00e2nd cererea a e\u0219uat\ntail -50 \/var\/log\/nginx\/error.log\n\n# Logul PHP-FPM \u2014 \u00ee\u021bi arat\u0103 dac\u0103 FPM cade, r\u0103m\u00e2ne f\u0103r\u0103 workere sau refuz\u0103 conexiuni\ntail -50 \/var\/log\/php8.5-fpm.log\n\n# Ring bufferul kernelului \u2014 \u00ee\u021bi arat\u0103 dac\u0103 OOM killerul a pornit \u0219i a terminat un proces\ndmesg | grep -iE \"oom|killed process\" | tail -20<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Logul de erori NGINX este cel mai important. O linie care con\u021bine <code>connect() to unix:\/var\/run\/php\/php8.5-fpm.sock failed (2: No such file or directory)<\/code> indic\u0103 Fix 1 sau Fix 2. O linie cu <code>connect() failed (111: Connection refused)<\/code> indic\u0103 Fix 1. O linie cu <code>upstream timed out (110: Connection timed out)<\/code> indic\u0103 Fix 4. O linie f\u0103r\u0103 nicio eroare upstream, combinat\u0103 cu o intrare OOM \u00een kernel, indic\u0103 Fix 5. Potrive\u0219te tiparul erorii cu remediul corespunz\u0103tor.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Fix 1: PHP-FPM este oprit<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Aceasta este cea mai frecvent\u0103 cauz\u0103. PHP-FPM se opre\u0219te silen\u021bios dup\u0103 un eveniment de epuizare a memoriei, un update e\u0219uat sau o eroare \u00een configura\u021bia poolului, \u00een timp ce NGINX r\u0103m\u00e2ne activ. Monitorizarea automat\u0103 a serviciilor din DirectAdmin supravegheaz\u0103 NGINX, dar nu reporne\u0219te \u00eentotdeauna PHP-FPM al\u0103turi de acesta.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>systemctl status php8.5-fpm\n\n# Dac\u0103 este inactiv sau \u00een stare de eroare:\nsystemctl start php8.5-fpm\n\n# Verific\u0103 de ce nu a pornit (cite\u0219te outputul complet):\njournalctl -xeu php8.5-fpm --no-pager | tail -30<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 porne\u0219te f\u0103r\u0103 probleme \u0219i eroarea 502 dispare, investiga\u021bia nu s-a \u00eencheiat. Ceva l-a oprit. Verific\u0103 logul PHP-FPM \u0219i logul OOM al kernelului (Fix 5) pentru a g\u0103si cauza principal\u0103, altfel va c\u0103dea din nou \u00een c\u00e2teva ore. Dac\u0103 systemctl raporteaz\u0103 o eroare de sintax\u0103 \u00een configura\u021bia poolului, g\u0103se\u0219te \u0219i corecteaz\u0103 directiva problematic\u0103 \u00eenainte de repornire.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Fix 2: Nepotrivire \u00eentre calea socketului din NGINX \u0219i PHP-FPM<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Aceasta este a doua cauz\u0103 ca frecven\u021b\u0103 \u0219i este aproape \u00eentotdeauna declan\u0219at\u0103 de un upgrade de versiune PHP prin CustomBuildul DirectAdmin. C\u00e2nd CustomBuild upgradeaz\u0103 PHP (de exemplu de la 8.4 la 8.5), creeaz\u0103 un nou fi\u0219ier socket la o cale nou\u0103, dar nu actualizeaz\u0103 automat fiecare configura\u021bie de virtual host NGINX care referen\u021biaz\u0103 calea veche. Fi\u0219ierul socket referit \u00een configura\u021bia NGINX nu mai exist\u0103, produc\u00e2nd eroarea \u201eNo such file or directory&#8221; \u00een logul NGINX.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Mai \u00eent\u00e2i, listeaz\u0103 ce fi\u0219iere socket exist\u0103 efectiv pe server \u00een acest moment.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>ls -la \/var\/run\/php\/<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Apoi g\u0103se\u0219te ce solicit\u0103 efectiv configura\u021bia de virtual host NGINX pentru domeniul afectat.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># DirectAdmin stocheaz\u0103 configura\u021biile de virtual host aici:\ngrep -r \"fastcgi_pass\" \/etc\/nginx\/conf.d\/virtual\/domeniultau.conf\n\n# Sau caut\u0103 \u00een toate virtual hosturile simultan:\ngrep -r \"fastcgi_pass\" \/etc\/nginx\/conf.d\/virtual\/<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Valoarea de dup\u0103 <code>fastcgi_pass unix:<\/code> trebuie s\u0103 corespund\u0103 exact unui fi\u0219ier socket care exist\u0103 \u00een <code>\/var\/run\/php\/<\/code>. Dac\u0103 difer\u0103, editeaz\u0103 configura\u021bia virtual hostului pentru a referen\u021bia calea corect\u0103 a socketului, apoi testeaz\u0103 \u0219i re\u00eencarc\u0103 NGINX.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>nginx -t &amp;&amp; systemctl reload nginx<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">\u00cen DirectAdmin, configura\u021bia NGINX per utilizator se afl\u0103 de obicei la <code>\/etc\/nginx\/conf.d\/virtual\/username.domeniultau.conf<\/code>. Modific\u0103rile f\u0103cute aici supravie\u021buiesc rebuildurilor CustomBuild dac\u0103 se afl\u0103 \u00een fi\u0219ierul de configurare corect, controlat de utilizator. Modific\u0103rile f\u0103cute \u00een configura\u021bia global\u0103 NGINX vor fi suprascrise la urm\u0103toarea rulare CustomBuild.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Fix 3: Poolul de workere PHP-FPM este epuizat (pm.max_children)<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">PHP-FPM poate rula cu socketul corect \u0219i tot poate produce erori 502 sub trafic, dac\u0103 toate sloturile de workere disponibile sunt ocupate. C\u00e2nd toate sloturile <code>pm.max_children<\/code> sunt pline \u0219i sose\u0219te o nou\u0103 cerere, PHP-FPM nu poate accepta conexiunea. NGINX a\u0219teapt\u0103 p\u00e2n\u0103 expir\u0103 timeoutul <code>fastcgi_read_timeout<\/code> \u0219i returneaz\u0103 un 502. Aceasta produce erori intermitente care se agraveaz\u0103 pe m\u0103sur\u0103 ce traficul cre\u0219te.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Logul FPM va afi\u0219a avertismentul explicit c\u00e2nd aceasta este cauza.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>grep \"max_children\" \/var\/log\/php8.5-fpm.log<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 g\u0103se\u0219ti intr\u0103ri de tipul <code>server reached pm.max_children setting (X), consider raising it<\/code>, poolul este subdimensionat. Deschide configura\u021bia poolului \u0219i recalculeaz\u0103 limita pe baza memoriei RAM disponibile efectiv. G\u0103se\u0219te mai \u00eent\u00e2i dimensiunea medie de memorie a workerelor PHP active.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>ps --no-headers -o \"rss,cmd\" -C php-fpm8.5 | awk '{ sum+=$1 } END { printf (\"%d%s\\n\", sum\/NR\/1024,\"M\") }'<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 outputul arat\u0103 45MB per proces \u0219i ai 1.8GB de RAM disponibili pentru PHP (dup\u0103 sc\u0103derea NGINX, MySQL \u0219i overheadului OS), maximul t\u0103u sigur este de 40 de procese child (1800 \/ 45 = 40). Deschide <code>\/etc\/php\/8.5\/fpm\/pool.d\/www.conf<\/code> (sau fi\u0219ierul pool per utilizator \u00een setupul DirectAdmin) \u0219i ajusteaz\u0103 corespunz\u0103tor. Schimb\u0103 \u0219i managerul de procese din <code>ondemand<\/code> \u00een <code>dynamic<\/code> pentru a men\u021bine workere de baz\u0103 pre-ini\u021bializate \u0219i a elimina laten\u021ba de cold-start.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>pm = dynamic\npm.max_children = 40\npm.start_servers = 8\npm.min_spare_servers = 4\npm.max_spare_servers = 12\npm.max_requests = 500<\/code><\/pre>\n\n\n\n<pre class=\"wp-block-code\"><code>systemctl reload php8.5-fpm<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">Fix 4: Timeoutul FastCGI din NGINX este prea scurt<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Opera\u021biunile WordPress grele \u2014 importuri mari de produse WooCommerce, rand\u0103ri de pagini Elementor cu zeci de widgeturi sau ecrane de administrare care ruleaz\u0103 interog\u0103ri complexe de baze de date \u2014 pot dep\u0103\u0219i timeoutul implicit FastCGI de 60 de secunde al NGINX. NGINX abandoneaz\u0103 conexiunea \u0219i returneaz\u0103 un 502 chiar dac\u0103 PHP-FPM proceseaz\u0103 cererea normal \u00een background.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Logul de erori NGINX va afi\u0219a <code>upstream timed out (110: Connection timed out) while reading response header from upstream<\/code> dac\u0103 aceasta este cauza. \u00cen DirectAdmin, adaug\u0103 override-urile de timeout \u00een blocul de configurare NGINX personalizat al domeniului, nu \u00een configura\u021bia global\u0103 NGINX. Locul corect pentru personaliz\u0103rile la nivel de utilizator care supravie\u021buiesc unui rebuild CustomBuild este \u00een fi\u0219ierul de virtual host per utilizator.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>fastcgi_connect_timeout 300;\nfastcgi_send_timeout 300;\nfastcgi_read_timeout 300;<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Aceasta este o m\u0103sur\u0103 de atenuare, nu o rezolvare. Un proces PHP care necesit\u0103 120 de secunde pentru a genera o pagin\u0103 are o problem\u0103 \u2014 o interogare lent\u0103 la baza de date, un apel API extern blocant sau un plugin prost codat. Dup\u0103 cre\u0219terea timeoutului pentru a opri erorile 502, instaleaz\u0103 pluginul Query Monitor \u0219i profileaz\u0103 cererea lent\u0103 pentru a g\u0103si bottleneckul real.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Fix 5: OOM Killerul Linux a terminat PHP-FPM<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 PHP-FPM este g\u0103sit oprit f\u0103r\u0103 erori \u00een propriul log, iar repornirea lui rezolv\u0103 temporar eroarea 502 \u00eenainte ca aceasta s\u0103 reapar\u0103, OOM killerul Linux este probabil vinovatul. OOM killerul kernelului este un mecanism de ultim\u0103 instan\u021b\u0103 care termin\u0103 procesul cel mai consumator de memorie pentru a preveni blocarea total\u0103 a sistemului. \u00ce\u0219i scrie ac\u021biunile \u00een logul kernelului, nu \u00een logul PHP-FPM \u2014 de aceea este at\u00e2t de frecvent trecut cu vederea.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>dmesg | grep -iE \"oom|killed process\" | tail -20\n# Sau prin journalctl:\njournalctl -k | grep -iE \"oom|killed\"<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 g\u0103se\u0219ti intr\u0103ri de tipul <code>Out of memory: Kill process [PID] (php-fpm8.5) score X or sacrifice child<\/code>, RAM-ul de pe VPS-ul t\u0103u este insuficient pentru setarea curent\u0103 <code>pm.max_children<\/code>. Repornirea PHP-FPM f\u0103r\u0103 reducerea consumului de memorie va duce la acela\u0219i crash la urm\u0103torul spike de trafic. Op\u021biunile tale sunt: redu <code>pm.max_children<\/code> la o valoare pe care serverul t\u0103u o poate sus\u021bine efectiv (calculeaz\u0103-o corect conform Fix 3), identific\u0103 \u0219i elimin\u0103 pluginurile cu memory leakuri care umfl\u0103 dimensiunea workerelor individuale, sau upgradeaz\u0103 la un <a href=\"https:\/\/www.serverspan.ro\/virtual-servers\">plan VPS<\/a> cu mai mult RAM.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Fix 6: MySQL blocheaz\u0103 workere PHP-FPM<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Aceasta este cauza cel mai des nediagnosticat\u0103 a erorilor 502 \u0219i este rareori acoperit\u0103 \u00een ghidurile generale despre WordPress. C\u00e2nd MySQL este supra\u00eenc\u0103rcat, blocat sau ruleaz\u0103 o interogare extrem de lent\u0103, fiecare worker PHP-FPM care face un apel la baza de date se blocheaz\u0103 a\u0219tept\u00e2nd un r\u0103spuns. Deoarece workerele PHP sunt blocate \u2014 nu crashate \u2014 ele apar ca procese active, iar <code>pm.max_children<\/code> se umple instant. Cererile noi intr\u0103 la coad\u0103 \u0219i expir\u0103, produc\u00e2nd un 502. MySQL \u00eensu\u0219i nu arunc\u0103 o eroare vizibil\u0103 pentru WordPress p\u00e2n\u0103 la expirarea timeoutului de conexiune.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>systemctl status mysql\n\n# Conecteaz\u0103-te \u0219i verific\u0103 lista de procese active:\nmysql -u root -p -e \"SHOW FULL PROCESSLIST;\"\n\n# Caut\u0103 interog\u0103ri cu o valoare Time mare sau State care arat\u0103 \"Waiting for table lock\"\n# Termin\u0103 o interogare blocant\u0103 prin ID-ul procesului ei (\u00eenlocuie\u0219te ID cu num\u0103rul real):\nmysql -u root -p -e \"KILL QUERY ID;\"<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 MySQL ruleaz\u0103 dar processlistul arat\u0103 zeci de interog\u0103ri acumul\u00e2ndu-se, problema este probabil un index lips\u0103 din baza de date, un job WP-Cron sc\u0103pat de sub control care declan\u0219eaz\u0103 interog\u0103ri masive simultane sau un plugin WordPress care efectueaz\u0103 un full table scan la fiecare \u00eenc\u0103rcare de pagin\u0103. <a href=\"https:\/\/www.serverspan.ro\/blog\/cum-sa-repari-eroarea-critica-wordpress-ghid-complet-de-recuperare-pentru-orice-site-web\">Ghidul de recuperare a erorii critice WordPress<\/a> acoper\u0103 dezactivarea WP-Cron \u0219i izolarea conflictelor de pluginuri la nivel de baz\u0103 de date.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Fix 7: Fail2Ban blocheaz\u0103 traficul de loopback sau IP-urile Cloudflare<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Aceasta este o cauz\u0103 specific\u0103 \u0219i frustrant\u0103 care se prezint\u0103 ca un 502 complet normal din perspectiva vizitatorului, dar nu las\u0103 nicio eroare PHP-FPM evident\u0103 \u00een loguri. Fail2ban, un instrument de securitate legitim \u0219i important, poate fi configurat gre\u0219it astfel \u00eenc\u00e2t s\u0103 baneze accidental <code>127.0.0.1<\/code> (adresa de loopback) sau range-urile IP folosite de Cloudflare ca proxy. C\u00e2nd NGINX \u00eencearc\u0103 s\u0103 transmit\u0103 o cerere c\u0103tre PHP-FPM prin interfa\u021ba de loopback, este blocat la nivelul firewallului \u0219i returneaz\u0103 o eroare de conexiune refuzat\u0103.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># Verific\u0103 dac\u0103 adresa de loopback sau IP-urile Cloudflare sunt banate \u00een prezent:\nfail2ban-client status\nfail2ban-client status nginx-http-auth\n\n# Verific\u0103 regulile iptables active pentru orice DROP pe loopback:\niptables -L -n | grep \"127.0.0.1\"\n\n# Dac\u0103 127.0.0.1 este banat, debaneaz\u0103-l imediat:\nfail2ban-client set JAILNAME unbanip 127.0.0.1<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Pentru a preveni reapari\u021bia problemei, adaug\u0103 adresa de loopback \u0219i range-urile IP publicate de Cloudflare \u00een lista <code>ignoreip<\/code> a fail2ban din <code>\/etc\/fail2ban\/jail.local<\/code>. Cloudflare public\u0103 range-urile sale actuale de IP-uri la <code>https:\/\/www.cloudflare.com\/ips\/<\/code>. Dac\u0103 site-ul t\u0103u ruleaz\u0103 \u00een spatele Cloudflare \u0219i observi erori 502 doar din anumite regiuni geografice, o problem\u0103 de rutare pe partea Cloudflare sau un IP de origine expirat \u00een configura\u021bia DNS Cloudflare merit\u0103 verificat \u00eenainte de a s\u0103pa mai ad\u00e2nc \u00een stackul serverului.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Bonus: Xdebug activ \u00een produc\u021bie<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Xdebug este o extensie PHP de debugging care nu trebuie niciodat\u0103 \u00eenc\u0103rcat\u0103 pe un server de produc\u021bie. C\u00e2nd este activ\u0103, adaug\u0103 30 p\u00e2n\u0103 la 60MB overhead per worker PHP \u0219i \u00eencetine\u0219te semnificativ execu\u021bia. Pe un VPS unde \u00een mod normal \u00eencap 40 de workere \u00een RAM, Xdebug reduce capacitatea la 15 workere \u00eenainte de a epuiza memoria, cauz\u00e2nd direct eroarea 502 din Fix 3. Aceasta este frecvent\u0103 dup\u0103 ce un dezvoltator testeaz\u0103 local, export\u0103 o configura\u021bie \u0219i aceasta ajunge \u00een produc\u021bie cu ini-ul Xdebug \u00eenc\u0103 activat.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># Verific\u0103 dac\u0103 Xdebug este activ:\nphp -m | grep -i xdebug\n\n# G\u0103se\u0219te fi\u0219ierul de configurare care \u00eel activeaz\u0103:\nfind \/etc\/php\/8.5\/ -name \"*.ini\" | xargs grep -l \"xdebug\"\n\n# Dezactiveaz\u0103-l prin comentarea liniei extension:\n# Schimb\u0103: zend_extension=xdebug.so\n# \u00cen:      ;zend_extension=xdebug.so\n\nsystemctl reload php8.5-fpm<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">Checklist rapid de diagnosticare<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 e\u0219ti \u00een mijlocul unui incident \u0219i ai nevoie de o secven\u021b\u0103 structurat\u0103, folose\u0219te aceast\u0103 ordine. Fiecare pas elimin\u0103 o categorie de cauze \u00eenainte de a trece la urm\u0103toarea.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Cite\u0219te <code>\/var\/log\/nginx\/error.log<\/code> \u2014 identific\u0103 stringul exact de eroare upstream \u00eenainte de a atinge orice fi\u0219ier.<\/li>\n\n\n\n<li>Ruleaz\u0103 <code>systemctl status php8.5-fpm<\/code> \u2014 serviciul ruleaz\u0103? Dac\u0103 nu, porne\u0219te-l \u0219i verific\u0103 <code>journalctl -xeu php8.5-fpm<\/code> pentru motivul opririi.<\/li>\n\n\n\n<li>Ruleaz\u0103 <code>ls \/var\/run\/php\/<\/code> \u0219i compar\u0103 cu <code>grep fastcgi_pass \/etc\/nginx\/conf.d\/virtual\/domeniultau.conf<\/code> \u2014 se potrivesc exact?<\/li>\n\n\n\n<li>Ruleaz\u0103 <code>dmesg | grep -i oom<\/code> \u2014 a fost procesul terminat de kernel?<\/li>\n\n\n\n<li>Ruleaz\u0103 <code>grep \"max_children\" \/var\/log\/php8.5-fpm.log<\/code> \u2014 poolul de workere atinge plafonul?<\/li>\n\n\n\n<li>Ruleaz\u0103 <code>systemctl status mysql<\/code> \u0219i <code>SHOW FULL PROCESSLIST<\/code> \u2014 MySQL este blocat sau supra\u00eenc\u0103rcat?<\/li>\n\n\n\n<li>Ruleaz\u0103 <code>iptables -L -n | grep 127.0.0.1<\/code> \u2014 fail2ban blocheaz\u0103 traficul de loopback?<\/li>\n\n\n\n<li>Ruleaz\u0103 <code>php -m | grep xdebug<\/code> \u2014 o extensie de debugging umfl\u0103 consumul de memorie?<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 parcurgi \u00eentregul checklist \u0219i eroarea 502 persist\u0103, problema este aproape sigur de natur\u0103 ambiental\u0103: un binar PHP corupt dup\u0103 un update e\u0219uat, un disc plin care \u00eempiedic\u0103 crearea fi\u0219ierului socket sau o problem\u0103 hardware pe nodul fizic. Verific\u0103 spa\u021biul pe disc cu <code>df -h<\/code> \u0219i utilizarea inode-urilor cu <code>df -i<\/code> \u00eenainte de a escalada. Dac\u0103 serverul este administrat prin planurile noastre de <a href=\"https:\/\/www.serverspan.ro\/webhosting\">web hosting<\/a>, deschide un tichet de suport cu outputul logului de erori NGINX ata\u0219at \u2014 un 502 pe infrastructur\u0103 managed \u00eenseamn\u0103 c\u0103 ceva la nivel de server necesit\u0103 investiga\u021bie la nivelul hypervisorului.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>O eroare WordPress 502 Bad Gateway \u00eenseamn\u0103 c\u0103 NGINX a primit cererea, a transmis-o c\u0103tre PHP-FPM pentru procesare \u0219i nu a primit niciun r\u0103spuns valid \u00eenapoi. Rezolvarea \u021bine aproape \u00eentotdeauna de una dintre cele \u0219apte situa\u021bii: PHP-FPM este oprit, calea socketului este gre\u0219it\u0103, poolul de workere FPM este epuizat, timeoutul FastCGI al NGINX este prea [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":2553,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[9,12],"tags":[14313,14314,14308,14317,14319,14315,14316,14306,14318,14320],"class_list":["post-2556","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-tutorials","category-virtual-servers","tag-fail2ban-loopback-502","tag-fastcgi_read_timeout-502","tag-fix-502-bad-gateway-directadmin","tag-mysql-blocheaza-php-fpm-502","tag-nginx-php-fpm-eroare-502-directadmin","tag-oom-killer-php-fpm-wordpress","tag-php-fpm-oprit-wordpress-vps","tag-pm-max_children-502-bad-gateway","tag-wordpress-502-bad-gateway-rezolvare-2026","tag-xdebug-productie-502"],"_links":{"self":[{"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/2556","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2556"}],"version-history":[{"count":3,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/2556\/revisions"}],"predecessor-version":[{"id":2559,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/2556\/revisions\/2559"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/media\/2553"}],"wp:attachment":[{"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2556"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2556"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2556"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}