{"id":2446,"date":"2026-02-09T17:17:48","date_gmt":"2026-02-09T17:17:48","guid":{"rendered":"https:\/\/ssblog.eu.enginyr.ing\/?p=2446"},"modified":"2026-03-02T13:31:45","modified_gmt":"2026-03-02T13:31:45","slug":"nginx-502-bad-gateway-cel-mai-detaliat-ghid-pe-care-il-vei-gasi-vreodata-de-la-basics-la-kernel-tuning","status":"publish","type":"post","link":"https:\/\/www.serverspan.ro\/blog\/nginx-502-bad-gateway-cel-mai-detaliat-ghid-pe-care-il-vei-gasi-vreodata-de-la-basics-la-kernel-tuning\/","title":{"rendered":"NGINX 502 Bad Gateway: Cel mai detaliat ghid pe care \u00eel vei g\u0103si vreodat\u0103 (De la basics la Kernel Tuning)"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">\u00cen via\u021ba fiec\u0103rui administrator de sistem, exist\u0103 un moment de groaz\u0103 pur\u0103: \u00eencep s\u0103 curg\u0103 rapoartele c\u0103 &#8220;<a href=\"https:\/\/www.serverspan.ro\/blog\/realitatea-tichetelor-de-tip-serverul-meu-merge-greu\/\">site-ul este picat<\/a>&#8220;, dar c\u00e2nd verifici serverul, totul pare \u00een regul\u0103. \u00cenc\u0103rcarea CPU este mic\u0103. Discul nu este plin. Serviciile ruleaz\u0103. Totu\u0219i, fiecare browser care \u00ee\u021bi acceseaz\u0103 domeniul este \u00eent\u00e2mpinat de ecranul alb al mor\u021bii: <strong><a href=\"https:\/\/www.serverspan.ro\/blog\/php-fpm-vs-oom-killer-ghidul-definitiv-de-tuning-pentru-vps-uri-cu-trafic-mare\/\">502 Bad Gateway<\/a><\/strong>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Spre deosebire de o eroare 500 Internal Server Error (care \u00eenseamn\u0103 de obicei c\u0103 codul t\u0103u PHP a cr\u0103pat fatal) sau o eroare 504 Gateway Timeout (care \u00eenseamn\u0103 c\u0103 scriptul t\u0103u e prea lent), o eroare 502 este o defec\u021biune de re\u021bea. \u00censeamn\u0103 c\u0103 lan\u021bul de comunicare s-a rupt. Nginx, ac\u021bion\u00e2nd ca &#8220;Gateway&#8221; sau proxy, a \u00eencercat s\u0103 paseze o cerere c\u0103tre aplica\u021bia backend (cum ar fi PHP-FPM), iar backend-ul, \u00een esen\u021b\u0103, i-a \u00eenchis telefonul \u00een nas, a refuzat s\u0103 r\u0103spund\u0103 sau a vorbit aiurea.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">La ServerSpan, gestionarea a mii de instan\u021be <a href=\"https:\/\/www.serverspan.ro\/blog\/ce-este-un-server-virtual-un-ghid-despre-tipurile-de-virtualizare\/\">Linux VPS<\/a> ne-a \u00eenv\u0103\u021bat c\u0103 erorile 502 sunt rareori simple. Pot fi cauzate de orice, de la un simplu conflict de plugin-uri p\u00e2n\u0103 la dep\u0103\u0219iri complexe ale stivei TCP la nivel de kernel. Acest ghid complet este scris pentru a te duce de la un nivel de \u00eencep\u0103tor absolut (&#8220;Ce este un gateway?&#8221;) la un nivel de sysadmin senior (&#8220;Cum urm\u0103resc apelurile de sistem?&#8221;). Indiferent dac\u0103 g\u0103zduie\u0219ti un mic <a href=\"https:\/\/www.serverspan.ro\/blog\/wordpress-502-bad-gateway-in-2026-ghidul-complet-de-depanare-si-rezolvare-directadmin-vps\/\">blog WordPress<\/a> sau un magazin WooCommerce masiv, a\u0219a repari t\u0103cerea.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Partea 1: \u00cen\u021belegerea arhitecturii<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">\u00cenainte de a repara eroarea, trebuie s\u0103 \u00een\u021belegi fluxul datelor. \u00centr-un stack web modern (LEMP: Linux, Nginx, MySQL, PHP), Nginx nu execut\u0103 cod PHP. Este un reverse proxy. Serve\u0219te fi\u0219iere statice (imagini, CSS, JS) eficient, dar c\u00e2nd vede un fi\u0219ier `.php`, paseaz\u0103 cererea c\u0103tre un proces separat numit <strong>PHP-FPM<\/strong> (FastCGI Process Manager).<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">G\u00e2nde\u0219te-te la Nginx ca la chelnerul dintr-un restaurant \u0219i la PHP-FPM ca la buc\u0103tarul din buc\u0103t\u0103rie.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Cererea:<\/strong> Un client (browser) comand\u0103 o friptur\u0103 (index.php).<\/li>\n\n\n\n<li><strong>Pasarea comenzii:<\/strong> Chelnerul (Nginx) scrie comanda pe un bon \u0219i o gliseaz\u0103 prin fereastr\u0103 (Socket\/Port) c\u0103tre buc\u0103t\u0103rie (PHP-FPM).<\/li>\n\n\n\n<li><strong>Eroarea 502:<\/strong> Chelnerul gliseaz\u0103 bonul prin fereastr\u0103, dar:\n<ul class=\"wp-block-list\">\n<li>Buc\u0103t\u0103ria este \u00een fl\u0103c\u0103ri (Serviciul a cr\u0103pat).<\/li>\n\n\n\n<li>Fereastra este b\u0103tut\u0103 \u00een cuie (Permisiuni refuzate\/Permission Denied).<\/li>\n\n\n\n<li>Buc\u0103tarii ignor\u0103 fereastra pentru c\u0103 sunt prea ocupa\u021bi (Backlog Full).<\/li>\n\n\n\n<li>Buc\u0103tarul ia bonul \u0219i moare instant de infarct (Segfault).<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">\u00cen oricare dintre aceste cazuri, chelnerul trebuie s\u0103 se \u00eentoarc\u0103 la client \u0219i s\u0103 spun\u0103: &#8220;Nu pot s\u0103 v\u0103 preiau comanda&#8221;. Aceasta este eroarea 502 Bad Gateway.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Partea 2: Lista de verificare pentru &#8220;Junior Admin&#8221; (\u00cencepe aici)<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">\u00cenainte s\u0103 \u00eencepi s\u0103 umbli la parametrii de kernel, f\u0103 verific\u0103rile de s\u0103n\u0103tate de baz\u0103. 80% dintre erorile 502 sunt cauzate de simple e\u0219ecuri ale serviciilor.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">1. PHP-FPM chiar ruleaz\u0103?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Sun\u0103 evident, dar serviciile crap\u0103. Dac\u0103 PHP-FPM nu ruleaz\u0103, Nginx nu are cu cine s\u0103 vorbeasc\u0103.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo systemctl status php8.2-fpm<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 scrie &#8220;inactive&#8221; sau &#8220;failed&#8221;, reporne\u0219te-l. Dac\u0103 e\u0219ueaz\u0103 la repornire, verific\u0103 sintaxa configura\u021biei:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo php-fpm8.2 -t<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">2. Nginx vorbe\u0219te cu cine trebuie?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Un scenariu comun pe serverele <strong><a href=\"https:\/\/www.serverspan.ro\/blog\/migrare-de-la-shared-hosting-la-vps-ghidul-zero-downtime-pas-cu-pas\/\">Managed VPS<\/a><\/strong> este un upgrade de versiune PHP. Faci upgrade de la PHP 8.1 la 8.2 folosind `apt upgrade`. Vechiul serviciu (`php8.1-fpm`) se opre\u0219te, iar cel nou (`php8.2-fpm`) porne\u0219te.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Totu\u0219i, fi\u0219ierele tale de configurare Nginx (`\/etc\/nginx\/sites-available\/your-site`) s-ar putea s\u0103 indice \u00eenc\u0103 spre vechea cale de socket:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>fastcgi_pass unix:\/run\/php\/php8.1-fpm.sock; # GRE\u0218IT<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Verific\u0103 directorul `\/run\/php\/` s\u0103 vezi ce socket exist\u0103 de fapt \u0219i actualizeaz\u0103 config-ul Nginx pentru a se potrivi.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">3. Verific\u0103 log-urile de eroare (\u00cen mod corect)<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Nu da doar `tail` la log uit\u00e2ndu-te cum curge textul. Folose\u0219te `grep` pentru codul specific de eroare. Log-ul de eroare Nginx se afl\u0103 de obicei la `\/var\/log\/nginx\/error.log`.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>grep \"502\" \/var\/log\/nginx\/access.log\ntail -n 100 \/var\/log\/nginx\/error.log<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Caut\u0103 fraze precum &#8220;Connection refused&#8221; (Serviciu picat), &#8220;No such file or directory&#8221; (Cale socket gre\u0219it\u0103) sau &#8220;Upstream sent too big header&#8221; (Buffer overflow). Aceste indicii \u00ee\u021bi definesc urm\u0103torii pa\u0219i.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Partea 3: Fix-urile Intermediare (<a href=\"https:\/\/www.serverspan.ro\/blog\/performanta-la-nivel-de-aplicatie-optimizarea-php-8-5-si-nginx-pentru-vps-uri-cu-trafic-intens\/\">Tuning de Configura\u021bie<\/a>)<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 serviciul este pornit \u0219i c\u0103ile sunt corecte, dar \u00eenc\u0103 prime\u0219ti erori 502\u2014\u00een special intermitente sub sarcin\u0103 mare\u2014te confrun\u021bi probabil cu un blocaj de configurare. Asta este comun pe planurile <strong>VPS de \u00eenalt\u0103 performan\u021b\u0103<\/strong> unde set\u0103rile implicite limiteaz\u0103 hardware-ul.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">1. Dep\u0103\u0219irea buffer-ului de antet (Header Buffer Overflow)<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Problema:<\/strong><br>Aplica\u021biile web moderne trimit antete HTTP mari. Cookie-urile, token-urile de securitate (JWT) \u0219i datele complexe de sesiune pot umfla antetul de r\u0103spuns trimis de PHP c\u0103tre Nginx. Nginx are un buffer dedicat pentru citirea acestor antete, definit de `fastcgi_buffer_size`. Valoarea implicit\u0103 este adesea minuscul\u0103 (4KB sau 8KB\u2014o pagin\u0103 de memorie).<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 PHP trimite un antet de 10KB, Nginx nu \u0219tie ce s\u0103 fac\u0103 cu surplusul. \u00cen loc s\u0103 \u00eel trunchieze, consider\u0103 r\u0103spunsul invalid \u0219i arunc\u0103 o eroare 502.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Solu\u021bia:<\/strong><br>M\u0103re\u0219te limitele buffer-ului \u00een `nginx.conf` \u00een blocul `http {}` sau \u00een blocul specific al serverului.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>http {\n    ...\n    fastcgi_buffers 16 16k; \n    fastcgi_buffer_size 32k;\n    ...\n}<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">D\u0103 reload la Nginx dup\u0103 aceast\u0103 schimbare (`nginx -s reload`). Asta rezolv\u0103 cam 30% dintre erorile 502 &#8220;misterioase&#8221; legate de plugin-urile de login\/autentificare.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">2. Nepotrivirea de Timeout (Timeout Mismatch)<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Problema:<\/strong><br>Exist\u0103 o negociere a r\u0103bd\u0103rii \u00eentre Nginx \u0219i PHP. Nginx are `fastcgi_read_timeout` (c\u00e2t timp a\u0219teapt\u0103 ca PHP s\u0103 r\u0103spund\u0103). PHP are `max_execution_time` (c\u00e2t timp ruleaz\u0103 \u00eenainte s\u0103 se sinucid\u0103).<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 Nginx a\u0219teapt\u0103 30 de secunde, dar PHP \u00eencearc\u0103 s\u0103 ruleze 60 de secunde, Nginx va \u00eenchide telefonul la secunda 30. Asta cauzeaz\u0103 de obicei un 504 Gateway Timeout, dar uneori poate rezulta \u00eentr-un 502 dac\u0103 socket-ul se \u00eenchide brusc.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Solu\u021bia:<\/strong><br>Asigur\u0103-te c\u0103 Nginx este mai r\u0103bd\u0103tor dec\u00e2t PHP.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># \u00cen php.ini\nmax_execution_time = 300\n\n# \u00cen nginx.conf\nfastcgi_read_timeout 300;<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">Partea 4: Senior Admin Deep Dive (Kernel &amp; <a href=\"https:\/\/www.serverspan.ro\/blog\/analiza-kernel-panic-in-2026-citirea-core-dump-ului-pentru-a-gasi-cauza-reala\/\">Analiz\u0103 Forensic\u0103<\/a>)<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Aici \u00eencepe munca adev\u0103rat\u0103. Dac\u0103 log-urile tale tac, configura\u021bia pare ok, dar serverul t\u0103u \u00eenc\u0103 arunc\u0103 erori 502 sub trafic intens, ai de-a face cu epuizarea resurselor la nivel de sistem de operare. Bun venit \u00een kernel.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">1. Aruncarea silen\u021bioas\u0103 din coad\u0103 (SYN Flood \/ Backlog Drop)<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Conceptul:<\/strong><br>C\u00e2nd Nginx se conecteaz\u0103 la PHP-FPM via TCP (127.0.0.1:9000), execut\u0103 un handshake TCP. Sistemul de operare \u021bine aceste conexiuni \u00eentr-o &#8220;Coad\u0103 de Ascultare&#8221; (Listen Queue) p\u00e2n\u0103 c\u00e2nd aplica\u021bia (PHP-FPM) le accept\u0103.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Aceast\u0103 coad\u0103 are o limit\u0103 de m\u0103rime. Dac\u0103 PHP-FPM este cople\u0219it (proceseaz\u0103 cererile mai lent dec\u00e2t sosesc), aceast\u0103 coad\u0103 se umple. Odat\u0103 plin\u0103, kernel-ul Linux <strong>arunc\u0103 silen\u021bios<\/strong> noile tentative de conexiune. Nginx trimite un pachet SYN, a\u0219teapt\u0103, nu prime\u0219te r\u0103spuns \u0219i presupune c\u0103 backend-ul este mort -&gt; Eroare 502.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Diagnosticare:<\/strong><br>Trebuie s\u0103 verifici statisticile de re\u021bea ale kernel-ului pentru pachete aruncate (dropped packets).<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># Verific\u0103 ListenDrops\nnstat -az | grep ListenDrop<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 acest num\u0103r cre\u0219te \u00een timp ce vezi erori 502, backlog-ul t\u0103u este prea mic.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Solu\u021bia:<\/strong><br>Trebuie s\u0103 ridici limita \u00een dou\u0103 locuri: \u00een Kernel (OS) \u0219i \u00een Aplica\u021bie (PHP).<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># 1. Editeaz\u0103 \/etc\/sysctl.conf\nnet.core.somaxconn = 65535\nnet.ipv4.tcp_max_syn_backlog = 65535\n\n# Aplic\u0103 schimb\u0103rile\nsysctl -p\n\n# 2. Editeaz\u0103 config-ul pool-ului PHP-FPM (www.conf)\nlisten.backlog = 65535\n\n# Reporne\u0219te PHP-FPM\nsystemctl restart php8.2-fpm<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">2. Epuizarea Porturilor Efemere (Ephemeral Port Exhaustion)<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Conceptul:<\/strong><br>Fiecare conexiune dintre Nginx \u0219i PHP-FPM consum\u0103 o pereche de porturi TCP. Chiar \u0219i dup\u0103 ce cererea se termin\u0103, conexiunea r\u0103m\u00e2ne \u00eentr-o stare numit\u0103 `TIME_WAIT` timp de 60 de secunde pentru a asigura integritatea datelor. Linux are o gam\u0103 limitat\u0103 de &#8220;porturi efemere&#8221; (de obicei cam 28.000) pentru aceste conexiuni de ie\u0219ire.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 serve\u0219ti 500 de cereri pe secund\u0103, consumi 30.000 de porturi pe minut. Vei r\u0103m\u00e2ne f\u0103r\u0103 porturi. Nginx nu va reu\u0219i s\u0103 deschid\u0103 o nou\u0103 conexiune -&gt; Eroare 502.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Diagnosticare:<\/strong><br>Num\u0103r\u0103 conexiunile \u00een starea TIME_WAIT.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>netstat -n | grep TIME_WAIT | wc -l<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 acest num\u0103r este aproape de 28.000, ai probleme serioase.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Solu\u021bia:<\/strong><br>Activeaz\u0103 &#8220;TCP Reuse&#8221; \u00een kernel. Asta permite Linux-ului s\u0103 refoloseasc\u0103 socket-urile `TIME_WAIT` \u00een siguran\u021b\u0103 pentru conexiuni noi.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># \/etc\/sysctl.conf\nnet.ipv4.tcp_tw_reuse = 1\nnet.ipv4.ip_local_port_range = 1024 65535<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">3. Urm\u0103rirea erorilor de segmentare (Segfaults) cu <code>strace<\/code><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Conceptul:<\/strong><br>Uneori PHP-FPM nu doar \u00eenghea\u021b\u0103; moare. O eroare de segmentare (Segfault) apare c\u00e2nd un proces \u00eencearc\u0103 s\u0103 acceseze memorie pe care nu o de\u021bine. Kernel-ul \u00eel omoar\u0103 instantaneu. Asta se \u00eent\u00e2mpl\u0103 des din cauza extensiilor PHP cu bug-uri (precum ImageMagick, Redis sau IonCube).<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">C\u00e2nd procesul moare \u00een mijlocul cererii, Nginx vede conexiunea t\u0103iat\u0103 brusc (&#8220;Connection reset by peer&#8221;) -&gt; Eroare 502.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Diagnosticare:<\/strong><br>Log-urile standard adesea nu \u00ee\u021bi vor ar\u0103ta <em>de ce<\/em> a cr\u0103pat. Trebuie s\u0103 ata\u0219ezi un &#8220;tracer&#8221; la proces.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">1. G\u0103se\u0219te ID-ul procesului Master (PID) al PHP-FPM:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>pgrep -P 1 php-fpm<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">2. Ruleaz\u0103 `strace` pe master \u0219i urm\u0103re\u0219te toate procesele copil (`-f`). Salveaz\u0103 output-ul \u00eentr-un fi\u0219ier pentru c\u0103 va fi masiv.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>strace -f -p &#91;PID] -s 1024 -o \/tmp\/debug.log<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">3. Reprodu eroarea 502 vizit\u00e2nd site-ul.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">4. Opre\u0219te `strace` (Ctrl+C) \u0219i inspecteaz\u0103 log-ul.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>grep \"SIGSEGV\" \/tmp\/debug.log<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Uit\u0103-te la liniile imediat <em>dinaintea<\/em> SIGSEGV. Probabil vei vedea un acces la un fi\u0219ier `.so` (ex: `imagick.so`). Dezactiveaz\u0103 acea extensie \u00een `php.ini` \u0219i vezi dac\u0103 revine stabilitatea.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Partea 5: Unix Sockets vs. TCP Sockets (Marea Dezbatere)<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Una dintre cele mai comune \u00eentreb\u0103ri pe care le primim la ServerSpan este: <em>&#8220;Ar trebui s\u0103 folosesc Unix Sockets sau Porturi TCP pentru PHP?&#8221;<\/em> R\u0103spunsul \u00ee\u021bi afecteaz\u0103 rata de erori 502.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Unix Sockets (`\/run\/php\/php-fpm.sock`)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Pro:<\/strong> Mai rapide. F\u0103r\u0103 overhead TCP (f\u0103r\u0103 rutare, checksums). Securitate (controlat\u0103 prin permisiuni pe fi\u0219ier).<\/li>\n\n\n\n<li><strong>Contra:<\/strong> G\u00e2tuire la scalare (Scalability bottleneck). Socket-urile se bazeaz\u0103 pe un fi\u0219ier pe disc. Sub sarcin\u0103 extrem de mare, gestionarea &#8220;lac\u0103tului&#8221; (lock) pe acest fi\u0219ier creeaz\u0103 un consum mare de CPU. De asemenea, dac\u0103 <a href=\"https:\/\/www.serverspan.ro\/blog\/gestionarea-docker-si-a-containerelor-pe-un-vps-cele-mai-bune-practici-pentru-stabilitate-si-performanta\/\">rulezi Nginx \u0219i PHP \u00een containere diferite<\/a> (Docker), socket-urile sunt mai greu de partajat.<\/li>\n\n\n\n<li><strong>Risc 502:<\/strong> Risc mare de erori &#8220;Permission Denied&#8221; dac\u0103 set\u0103rile de user\/group sunt gre\u0219ite.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">TCP Sockets (`127.0.0.1:9000`)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Pro:<\/strong> Scalabile. Pot fi balansate (Load Balanced &#8211; PHP pe alt server). Kernel-ul gestioneaz\u0103 backlog-urile TCP eficient.<\/li>\n\n\n\n<li><strong>Contra:<\/strong> Mai lente (diferen\u021b\u0103 de microsecunde). Consum\u0103 porturi.<\/li>\n\n\n\n<li><strong>Risc 502:<\/strong> Risc mare de &#8220;Port Exhaustion&#8221; \u0219i &#8220;Backlog Overflow&#8221; dac\u0103 nu sunt tunate.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Verdictul nostru:<\/strong><br>Pentru un singur <strong>Managed VPS<\/strong> care g\u0103zduie\u0219te un site WordPress standard, r\u0103m\u00e2i la Unix Sockets. Beneficiul de vitez\u0103 merit\u0103. Pentru un cluster cu trafic mare, load-balanced, sau dac\u0103 vezi erori misterioase de socket, treci pe TCP.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Partea 6: Preven\u021bie \u0219i Monitorizare<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">S\u0103 repari eroarea e bine; s\u0103 o previi e mai bine. Ai nevoie de vizibilitate asupra a ce face PHP-FPM.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Activeaz\u0103 Pagina de Status<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">PHP-FPM are un dashboard integrat, dar este dezactivat implicit. Activeaz\u0103-l \u00een `www.conf`:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>pm.status_path = \/status<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">\u0218i permite Nginx s\u0103-l serveasc\u0103:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>location ~ ^\/(status|ping)$ {\n    allow 127.0.0.1;\n    deny all;\n    fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;\n    include fastcgi_params;\n    fastcgi_pass unix:\/run\/php\/php8.2-fpm.sock;\n}<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Acum \u00eel po\u021bi interoga local:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>curl 127.0.0.1\/status<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Fii atent la <strong>&#8220;listen queue&#8221;<\/strong> \u0219i <strong>&#8220;max active processes&#8221;<\/strong>. Dac\u0103 &#8220;max active processes&#8221; este egal cu limita ta `pm.max_children`, ai nevoie de mai mult RAM \u0219i mai mul\u021bi copii. Dac\u0103 &#8220;listen queue&#8221; este mai mare de zero, utilizatorii t\u0103i experimenteaz\u0103 laten\u021b\u0103 care se va transforma eventual \u00een erori 502.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Concluzie: Nu te teme de Gateway<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Eroarea 502 Bad Gateway nu este un act aleatoriu al sor\u021bii. Este o defec\u021biune determinist\u0103 a re\u021belei sau a resurselor. \u00censeamn\u0103 c\u0103 chelnerul t\u0103u (Nginx) nu poate vorbi cu buc\u0103tarul (PHP). Verific\u00e2nd sistematic statusul serviciilor, revizuind log-urile, verific\u00e2nd m\u0103rimile buffer-elor \u0219i eventual plonj\u00e2nd \u00een metricile TCP ale kernel-ului, po\u021bi rezolva 100% dintre aceste erori.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">La ServerSpan, configur\u0103m imaginile noastre de <a href=\"https:\/\/www.serverspan.ro\/blog\/managed-vs-unmanaged-pentru-gazduire-magazin-online-cum-sa-faci-alegerea-corecta\/\">Managed Cloud VPS<\/a> cu aceste optimiz\u0103ri de kernel pre-aplicate, pentru c\u0103 noi credem c\u0103 ar trebui s\u0103-\u021bi petreci timpul scriind con\u021binut, nu depan\u00e2nd handshake-uri TCP. Dar c\u00e2nd lucrurile se stric\u0103, s\u0103 \u0219tii s\u0103 m\u00e2nuie\u0219ti `strace` \u0219i `sysctl` te face un adev\u0103rat maestru al infrastructurii tale.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>\u00cen via\u021ba fiec\u0103rui administrator de sistem, exist\u0103 un moment de groaz\u0103 pur\u0103: \u00eencep s\u0103 curg\u0103 rapoartele c\u0103 &#8220;site-ul este picat&#8220;, dar c\u00e2nd verifici serverul, totul pare \u00een regul\u0103. \u00cenc\u0103rcarea CPU este mic\u0103. Discul nu este plin. Serviciile ruleaz\u0103. Totu\u0219i, fiecare browser care \u00ee\u021bi acceseaz\u0103 domeniul este \u00eent\u00e2mpinat de ecranul alb al mor\u021bii: 502 Bad Gateway. [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":2443,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[9],"tags":[773,13949,9010,13954,732,5885,1154,13957,13958,13946,5980,6149,10147,13951,591,13953,13959,3703,590,738,13955,6011,13939,13948,13952,13966,13947,4550,3884,13950,13960,13962,13961,13964,13963,5985,13956,10654,13965,2216],"class_list":["post-2446","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-tutorials","tag-backup-vps","tag-cel-mai-bun-vps-hosting","tag-cloud-vps","tag-comenzi-linux-vps","tag-configurare-vps","tag-depanare-vps","tag-gazduire-cloud","tag-latenta-vps","tag-latime-de-banda-vps","tag-managed-cloud-vps","tag-managed-vps","tag-migrare-vps","tag-monitorizare-vps","tag-panou-de-control-vps","tag-performanta-vps","tag-preturi-vps","tag-recenzii-vps","tag-secure-vps-hosting","tag-securitate-vps","tag-server-privat-virtual","tag-server-vps","tag-stocare-vps","tag-vps-cpu","tag-vps-de-inalta-performanta-3","tag-vps-dedicat","tag-vps-gratuit","tag-vps-ieftin","tag-vps-linux","tag-vps-management","tag-vps-nvme","tag-vps-pentru-business","tag-vps-pentru-developeri","tag-vps-pentru-gaming","tag-vps-pentru-trading","tag-vps-pentru-website","tag-vps-ram","tag-vps-self-hosted","tag-vps-vs-cloud","tag-vps-vs-dedicat","tag-vps-windows"],"_links":{"self":[{"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/2446","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=2446"}],"version-history":[{"count":5,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/2446\/revisions"}],"predecessor-version":[{"id":2562,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/2446\/revisions\/2562"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/media\/2443"}],"wp:attachment":[{"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2446"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2446"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2446"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}