{"id":5056,"date":"2026-11-01T10:52:40","date_gmt":"2026-11-01T10:52:40","guid":{"rendered":"https:\/\/zynoo.com\/blog\/502-bad-gateway-nginx\/"},"modified":"2026-11-01T16:14:13","modified_gmt":"2026-11-01T16:14:13","slug":"502-bad-gateway-nginx","status":"publish","type":"post","link":"https:\/\/zynoo.com\/blog\/es\/502-bad-gateway-nginx\/","title":{"rendered":"C\u00f3mo solucionar el error 502 Bad Gateway en Nginx (paso a paso)"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\" id=\"h-\">Un <strong>error 502 Bad Gateway en Nginx<\/strong> suele significar que Nginx no ha podido recibir una respuesta v\u00e1lida de un servidor de origen, como PHP-FPM, Node.js u otra aplicaci\u00f3n de backend.<\/p>\n\n<p class=\"wp-block-paragraph\">Las causas m\u00e1s habituales son servicios de aplicaciones detenidos, puertos o sockets de origen incorrectos y procesos de backend que fallan o cierran las conexiones de forma inesperada.<\/p>\n\n<p class=\"wp-block-paragraph\"><strong>Empieza por revisar los registros de errores de Nginx.<\/strong> A menudo muestran exactamente por qu\u00e9 ha fallado la conexi\u00f3n.<\/p>\n\n<p class=\"wp-block-paragraph\">Esta gu\u00eda presenta siete pasos pr\u00e1cticos para diagnosticar problemas en servidores Linux que ejecutan Nginx.<\/p>\n\n<h2 id=\"h-what-causes-a-502-bad-gateway-error-in-nginx\" class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"%C2%BFQue_provoca_un_error_502_Bad_Gateway_en_Nginx\"><\/span>\u00bfQu\u00e9 provoca un error 502 Bad Gateway en Nginx?<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n<p class=\"wp-block-paragraph\">Nginx suele actuar como proxy inverso: reenv\u00eda las solicitudes a las aplicaciones de backend y devuelve sus respuestas a los visitantes.<\/p>\n\n<p class=\"wp-block-paragraph\">Si el servicio de origen no responde correctamente, Nginx puede devolver el c\u00f3digo de estado HTTP 502.<\/p>\n\n<p class=\"wp-block-paragraph\">Entre las causas habituales se encuentran:<\/p>\n\n<ul class=\"wp-block-list\">\n<li>Servicios de backend que se han detenido o han fallado.<\/li>\n\n\n\n<li>Direcciones IP, puertos o sockets Unix de origen incorrectos.<\/li>\n\n\n\n<li>Fallos de PHP-FPM o de los procesos de la aplicaci\u00f3n.<\/li>\n\n\n\n<li>Problemas con los permisos de acceso al socket.<\/li>\n\n\n\n<li>Memoria o espacio en disco insuficientes.<\/li>\n\n\n\n<li>Conexiones con el servidor de origen no v\u00e1lidas o cerradas antes de tiempo.<\/li>\n<\/ul>\n\n<p class=\"wp-block-paragraph\">Las siguientes comprobaciones presuponen que tienes acceso por SSH y permisos para administrar tu servidor Linux.<\/p>\n\n<div class=\"wp-block-group zynoo-related-reading has-border-color has-text-color has-background is-layout-flow wp-block-group-is-layout-flow\" style=\"border-color:#c7d8ef;border-width:1px;border-radius:8px;border-left-color:#0069ff;border-left-width:3px;color:#24364f;background-color:#eaf2ff;margin-top:28px;margin-bottom:28px;padding-top:18px;padding-right:22px;padding-bottom:18px;padding-left:22px;font-size:16px;line-height:1.8\">\n<p class=\"wp-block-paragraph\"><strong>Si no sabes c\u00f3mo acceder a un servidor remoto,<\/strong> lee nuestra <a href=\"https:\/\/zynoo.com\/blog\/es\/ssh-commands\/\">gu\u00eda de comandos SSH para principiantes<\/a> antes de continuar.<\/p>\n<\/div>\n\n<figure class=\"wp-block-image size-large\"><img fetchpriority=\"high\" decoding=\"async\" width=\"1024\" height=\"576\" src=\"https:\/\/zynoo.com\/blog\/wp-content\/uploads\/2026\/11\/what-cause-502-Bad-Gateway-Nginx-1024x576.webp\" alt=\"Causas del error 502 Bad Gateway en Nginx\" class=\"wp-image-5037\" srcset=\"https:\/\/zynoo.com\/blog\/wp-content\/uploads\/2026\/11\/what-cause-502-Bad-Gateway-Nginx-1024x576.webp 1024w, https:\/\/zynoo.com\/blog\/wp-content\/uploads\/2026\/11\/what-cause-502-Bad-Gateway-Nginx-300x169.webp 300w, https:\/\/zynoo.com\/blog\/wp-content\/uploads\/2026\/11\/what-cause-502-Bad-Gateway-Nginx-768x432.webp 768w, https:\/\/zynoo.com\/blog\/wp-content\/uploads\/2026\/11\/what-cause-502-Bad-Gateway-Nginx-1536x864.webp 1536w, https:\/\/zynoo.com\/blog\/wp-content\/uploads\/2026\/11\/what-cause-502-Bad-Gateway-Nginx.webp 1672w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n<h2 id=\"h-1-check-the-nginx-error-logs\" class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"1_Revisa_los_registros_de_errores_de_Nginx\"><\/span>1. Revisa los registros de errores de Nginx<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n<p class=\"wp-block-paragraph\">Los registros de errores de Nginx suelen ser la forma m\u00e1s r\u00e1pida de identificar la causa de un error 502.<\/p>\n\n<p class=\"wp-block-paragraph\">Con\u00e9ctate a tu servidor por SSH y ejecuta:<\/p>\n\n<pre class=\"wp-block-code\"><code>sudo tail -n 50 \/var\/log\/nginx\/error.log<\/code><\/pre>\n\n<p class=\"wp-block-paragraph\">Esto muestra las \u00faltimas 50 entradas del registro.<\/p>\n\n<p class=\"wp-block-paragraph\">Para diagnosticar el problema en tiempo real, utiliza:<\/p>\n\n<pre class=\"wp-block-code\"><code>sudo tail -f \/var\/log\/nginx\/error.log<\/code><\/pre>\n\n<p class=\"wp-block-paragraph\">Vuelve a cargar la p\u00e1gina web afectada y comprueba si aparecen mensajes nuevos.<\/p>\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><tbody><tr><th>Mensaje del registro<\/th><th>Problema probable<\/th><\/tr><tr><td><code>connect() failed (111: Connection refused)<\/code><\/td><td>El backend no acepta conexiones<\/td><\/tr><tr><td><code>No such file or directory<\/code><\/td><td>No se encuentra el socket de origen configurado<\/td><\/tr><tr><td><code>Permission denied<\/code><\/td><td>Nginx no puede acceder al socket o al recurso<\/td><\/tr><tr><td><code>upstream prematurely closed connection<\/code><\/td><td>El backend ha cerrado la conexi\u00f3n de forma inesperada<\/td><\/tr><tr><td><code>upstream sent invalid header<\/code><\/td><td>El backend ha devuelto cabeceras de respuesta mal formadas<\/td><\/tr><\/tbody><\/table><\/figure>\n\n<p class=\"wp-block-paragraph\">Es posible que tu configuraci\u00f3n de alojamiento utilice otra ubicaci\u00f3n para los registros.<\/p>\n\n<p class=\"wp-block-paragraph\"><strong>No cambies la configuraci\u00f3n de Nginx hasta que hayas identificado la causa probable.<\/strong><\/p>\n\n<h2 id=\"h-2-check-whether-the-backend-service-is-running\" class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"2_Comprueba_si_el_servicio_de_backend_esta_en_ejecucion\"><\/span>2. Comprueba si el servicio de backend est\u00e1 en ejecuci\u00f3n<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n<p class=\"wp-block-paragraph\">Un error 502 suele producirse porque la aplicaci\u00f3n situada detr\u00e1s de Nginx se ha detenido.<\/p>\n\n<p class=\"wp-block-paragraph\">Si systemd gestiona el servicio de la aplicaci\u00f3n, ejecuta:<\/p>\n\n<pre class=\"wp-block-code\"><code>sudo systemctl status myapp<\/code><\/pre>\n\n<p class=\"wp-block-paragraph\">Sustituye <code>myapp<\/code> por el nombre real de tu servicio.<\/p>\n\n<p class=\"wp-block-paragraph\">En las aplicaciones basadas en PHP que utilizan PHP-FPM, el servicio podr\u00eda tener un nombre como:<\/p>\n\n<pre class=\"wp-block-code\"><code>sudo systemctl status php8.3-fpm<\/code><\/pre>\n\n<p class=\"wp-block-paragraph\">La versi\u00f3n de PHP instalada y el nombre del servicio pueden variar.<\/p>\n\n<p class=\"wp-block-paragraph\">Si el servicio ha fallado, examina sus registros:<\/p>\n\n<pre class=\"wp-block-code\"><code>sudo journalctl -u myapp -n 50<\/code><\/pre>\n\n<p class=\"wp-block-paragraph\">Busca fallos, dependencias ausentes, errores de configuraci\u00f3n o problemas relacionados con la memoria.<\/p>\n\n<p class=\"wp-block-paragraph\">Reinicia el servicio solo despu\u00e9s de identificar y solucionar el problema subyacente.<\/p>\n\n<h2 id=\"h-3-verify-the-upstream-port-or-socket\" class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"3_Comprueba_el_puerto_o_el_socket_de_origen\"><\/span>3. Comprueba el puerto o el socket de origen<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n<p class=\"wp-block-paragraph\">Nginx debe reenviar las solicitudes a la direcci\u00f3n correcta del backend.<\/p>\n\n<p class=\"wp-block-paragraph\">Por ejemplo, la configuraci\u00f3n de un proxy inverso podr\u00eda contener:<\/p>\n\n<pre class=\"wp-block-code\"><code>location \/ {\n    proxy_pass http:\/\/127.0.0.1:3000;\n}<\/code><\/pre>\n\n<p class=\"wp-block-paragraph\">Esto indica a Nginx que reenv\u00ede las solicitudes a una aplicaci\u00f3n HTTP que escucha en el puerto 3000.<\/p>\n\n<p class=\"wp-block-paragraph\">Comprueba si hay alg\u00fan servicio escuchando en ese puerto:<\/p>\n\n<pre class=\"wp-block-code\"><code>sudo ss -ltnp | grep ':3000'<\/code><\/pre>\n\n<p class=\"wp-block-paragraph\">Tambi\u00e9n puedes probar directamente un backend HTTP:<\/p>\n\n<pre class=\"wp-block-code\"><code>curl -i http:\/\/127.0.0.1:3000\/<\/code><\/pre>\n\n<p class=\"wp-block-paragraph\">Si el backend no est\u00e1 disponible, investiga la configuraci\u00f3n de su servicio antes de cambiar Nginx.<\/p>\n\n<h3 id=\"h-check-php-fpm-sockets\" class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Comprueba_los_sockets_de_PHP-FPM\"><\/span>Comprueba los sockets de PHP-FPM<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n<p class=\"wp-block-paragraph\">PHP-FPM suele utilizar sockets Unix o puertos TCP.<\/p>\n\n<p class=\"wp-block-paragraph\">Una configuraci\u00f3n de Nginx podr\u00eda contener:<\/p>\n\n<pre class=\"wp-block-code\"><code>fastcgi_pass unix:\/run\/php\/php8.3-fpm.sock;<\/code><\/pre>\n\n<p class=\"wp-block-paragraph\">Comprueba si existe el socket configurado:<\/p>\n\n<pre class=\"wp-block-code\"><code>ls -l \/run\/php\/<\/code><\/pre>\n\n<p class=\"wp-block-paragraph\">La ruta del socket debe coincidir con el ajuste <code>listen<\/code> del pool de PHP-FPM, y Nginx debe tener permiso para conectarse.<\/p>\n\n<p class=\"wp-block-paragraph\"><strong>Importante:<\/strong> <code>proxy_pass<\/code> se utiliza para servidores de origen HTTP, mientras que <code>fastcgi_pass<\/code> se utiliza para servicios <a href=\"https:\/\/en.wikipedia.org\/wiki\/FastCGI\">FastCGI<\/a> como PHP-FPM. No son intercambiables.<\/p>\n\n<div class=\"wp-block-group zynoo-related-reading has-border-color has-text-color has-background is-layout-flow wp-block-group-is-layout-flow\" style=\"border-color:#c7d8ef;border-width:1px;border-radius:8px;border-left-color:#0069ff;border-left-width:3px;color:#24364f;background-color:#eaf2ff;margin-top:28px;margin-bottom:28px;padding-top:18px;padding-right:22px;padding-bottom:18px;padding-left:22px;font-size:16px;line-height:1.8\">\n<p class=\"wp-block-paragraph\"><strong>Si est\u00e1s configurando Nginx por primera vez, aseg\u00farate de que proxy_pass apunte a la direcci\u00f3n correcta del backend.<\/strong> Nuestro <a href=\"https:\/\/zynoo.com\/blog\/es\/nginx-reverse-proxy-ubuntu\/\">tutorial para configurar un proxy inverso con Nginx en Ubuntu<\/a> muestra c\u00f3mo configurar el reenv\u00edo de solicitudes, probar la configuraci\u00f3n y habilitar HTTPS.<\/p>\n<\/div>\n\n<h2 id=\"h-4-check-server-memory-and-disk-space\" class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"4_Comprueba_la_memoria_y_el_espacio_en_disco_del_servidor\"><\/span>4. Comprueba la memoria y el espacio en disco del servidor<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n<p class=\"wp-block-paragraph\">Las aplicaciones de backend pueden fallar o dejar de responder cuando el servidor se queda sin recursos.<\/p>\n\n<p class=\"wp-block-paragraph\">Comprueba la memoria:<\/p>\n\n<pre class=\"wp-block-code\"><code>free -h<\/code><\/pre>\n\n<p class=\"wp-block-paragraph\">Comprueba el espacio en disco:<\/p>\n\n<pre class=\"wp-block-code\"><code>df -h<\/code><\/pre>\n\n<p class=\"wp-block-paragraph\">Comprueba los procesos en ejecuci\u00f3n:<\/p>\n\n<pre class=\"wp-block-code\"><code>top<\/code><\/pre>\n\n<p class=\"wp-block-paragraph\">Si una aplicaci\u00f3n se ha terminado por falta de memoria, puede que encuentres mensajes relacionados en el registro del sistema:<\/p>\n\n<pre class=\"wp-block-code\"><code>sudo journalctl -k --since \"1 hour ago\"<\/code><\/pre>\n\n<p class=\"wp-block-paragraph\">Busca eventos de falta de memoria o mensajes de terminaci\u00f3n de procesos.<\/p>\n\n<p class=\"wp-block-paragraph\">Si se ha agotado el espacio en disco, averigua qu\u00e9 lo est\u00e1 ocupando antes de eliminar archivos.<\/p>\n\n<div class=\"wp-block-group zynoo-related-reading has-border-color has-text-color has-background is-layout-flow wp-block-group-is-layout-flow\" style=\"border-color:#c7d8ef;border-width:1px;border-radius:8px;border-left-color:#0069ff;border-left-width:3px;color:#24364f;background-color:#eaf2ff;margin-top:28px;margin-bottom:28px;padding-top:18px;padding-right:22px;padding-bottom:18px;padding-left:22px;font-size:16px;line-height:1.8\">\n<p class=\"wp-block-paragraph\"><strong>Para consultar m\u00e1s comandos de supervisi\u00f3n,<\/strong> visita nuestra <a href=\"https:\/\/zynoo.com\/blog\/es\/linux-commands-for-server-management\/\">gu\u00eda de comandos esenciales de Linux para administrar servidores<\/a>.<\/p>\n<\/div>\n\n<h2 id=\"h-5-check-socket-permissions-and-application-logs\" class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"5_Comprueba_los_permisos_del_socket_y_los_registros_de_la_aplicacion\"><\/span>5. Comprueba los permisos del socket y los registros de la aplicaci\u00f3n<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n<p class=\"wp-block-paragraph\">A veces el backend est\u00e1 en ejecuci\u00f3n, pero Nginx no puede comunicarse con \u00e9l.<\/p>\n\n<p class=\"wp-block-paragraph\">Si utilizas sockets Unix, revisa su propietario y sus permisos:<\/p>\n\n<pre class=\"wp-block-code\"><code>ls -l \/run\/php\/<\/code><\/pre>\n\n<p class=\"wp-block-paragraph\">Si los registros indican un error de permisos, comprueba tambi\u00e9n los directorios de la ruta que conduce al socket.<\/p>\n\n<p class=\"wp-block-paragraph\">Los permisos adecuados dependen del usuario de los procesos de trabajo de Nginx y de la configuraci\u00f3n del servicio de backend.<\/p>\n\n<p class=\"wp-block-paragraph\">Evita conceder permisos demasiado amplios, como <code>chmod 777<\/code>. En su lugar, ajusta la configuraci\u00f3n del servicio o del pool correspondiente para que los procesos autorizados puedan acceder al socket.<\/p>\n\n<p class=\"wp-block-paragraph\">Si los registros de errores indican que el servidor de origen ha cerrado la conexi\u00f3n antes de tiempo, examina los registros de la aplicaci\u00f3n de backend en busca de fallos, excepciones o solicitudes fallidas.<\/p>\n\n<h2 id=\"h-6-test-your-nginx-configuration\" class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"6_Comprueba_la_configuracion_de_Nginx\"><\/span>6. Comprueba la configuraci\u00f3n de Nginx<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n<p class=\"wp-block-paragraph\">Una configuraci\u00f3n incorrecta del proxy o ciertos cambios de configuraci\u00f3n tambi\u00e9n pueden interrumpir la comunicaci\u00f3n con el servidor de origen.<\/p>\n\n<p class=\"wp-block-paragraph\">Antes de aplicar cambios, valida la configuraci\u00f3n de Nginx:<\/p>\n\n<pre class=\"wp-block-code\"><code>sudo nginx -t<\/code><\/pre>\n\n<p class=\"wp-block-paragraph\">Si la prueba se completa correctamente, recarga Nginx:<\/p>\n\n<pre class=\"wp-block-code\"><code>sudo systemctl reload nginx<\/code><\/pre>\n\n<p class=\"wp-block-paragraph\">La recarga aplica los cambios de configuraci\u00f3n v\u00e1lidos sin reiniciar el servicio innecesariamente.<\/p>\n\n<p class=\"wp-block-paragraph\">Si la prueba falla, corrige primero el error de configuraci\u00f3n indicado.<\/p>\n\n<p class=\"wp-block-paragraph\">No aumentes a ciegas los tiempos de espera del proxy ni los l\u00edmites de los b\u00faferes. Estos ajustes no solucionar\u00e1n un backend detenido, un socket incorrecto ni una conexi\u00f3n rechazada.<\/p>\n\n<h2 id=\"h-7-confirm-that-the-502-error-is-fixed\" class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"7_Confirma_que_se_ha_solucionado_el_error_502\"><\/span>7. Confirma que se ha solucionado el error 502<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n<p class=\"wp-block-paragraph\">Despu\u00e9s de solucionar el problema subyacente, prueba la URL afectada:<\/p>\n\n<pre class=\"wp-block-code\"><code>curl -I https:\/\/example.com<\/code><\/pre>\n\n<p class=\"wp-block-paragraph\">Sustituye <code>example.com<\/code> por tu dominio real.<\/p>\n\n<p class=\"wp-block-paragraph\">Una solicitud correcta suele devolver un estado HTTP apropiado, como <code>200 OK<\/code>, aunque las redirecciones y otras respuestas v\u00e1lidas pueden generar c\u00f3digos diferentes.<\/p>\n\n<p class=\"wp-block-paragraph\">Abre tambi\u00e9n el sitio web en tu navegador y vuelve a revisar los registros de errores de Nginx.<\/p>\n\n<p class=\"wp-block-paragraph\">Si el error reaparece cuando aumenta la carga, supervisa el servicio de backend y el uso de recursos mientras reproduces el problema.<\/p>\n\n<h2 id=\"h-how-to-prevent-nginx-502-errors\" class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Como_prevenir_los_errores_502_en_Nginx\"><\/span>C\u00f3mo prevenir los errores 502 en Nginx<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n<p class=\"wp-block-paragraph\">No todos los fallos del backend se pueden evitar, pero una buena administraci\u00f3n del servidor reduce las interrupciones evitables.<\/p>\n\n<ul class=\"wp-block-list\">\n<li>Supervisa el estado de Nginx y del servicio de backend.<\/li>\n\n\n\n<li>Revisa los registros de la aplicaci\u00f3n despu\u00e9s de cada despliegue.<\/li>\n\n\n\n<li>Configura pol\u00edticas adecuadas de recuperaci\u00f3n de servicios.<\/li>\n\n\n\n<li>Supervisa el uso de memoria, almacenamiento y conexiones.<\/li>\n\n\n\n<li>Valida los cambios de configuraci\u00f3n antes de aplicarlos.<\/li>\n\n\n\n<li>Prueba las aplicaciones directamente antes de dirigir el tr\u00e1fico a trav\u00e9s de Nginx.<\/li>\n<\/ul>\n\n<p class=\"wp-block-paragraph\">Si una aplicaci\u00f3n necesita m\u00e1s recursos, mide su uso real antes de decidir si aumentas la capacidad del servidor.<\/p>\n\n<div class=\"wp-block-group zynoo-related-reading has-border-color has-text-color has-background is-layout-flow wp-block-group-is-layout-flow\" style=\"border-color:#c7d8ef;border-width:1px;border-radius:8px;border-left-color:#0069ff;border-left-width:3px;color:#24364f;background-color:#eaf2ff;margin-top:28px;margin-bottom:28px;padding-top:18px;padding-right:22px;padding-bottom:18px;padding-left:22px;font-size:16px;line-height:1.8\">\n<p class=\"wp-block-paragraph\">Un error 502 indica que el servidor de origen ha enviado una respuesta no v\u00e1lida, mientras que un <strong>error 504<\/strong> se produce cuando el servidor de origen tarda demasiado en responder. Si est\u00e1s experimentando este \u00faltimo, sigue nuestra gu\u00eda para solucionar el <a href=\"https:\/\/zynoo.com\/blog\/es\/504-gateway-timeout\/\">error 504 Gateway Timeout<\/a> e investigar las aplicaciones lentas, los recursos del servidor y la configuraci\u00f3n de los tiempos de espera del proxy.<\/p>\n<\/div>\n\n<h2 id=\"h-frequently-asked-questions\" class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Preguntas_frecuentes\"><\/span>Preguntas frecuentes<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n<div class=\"schema-faq wp-block-yoast-faq-block\"><div class=\"schema-faq-section\" id=\"faq-question-1793529208055\"><strong class=\"schema-faq-question\">\u00bfQu\u00e9 significa 502 Bad Gateway en Nginx?<\/strong> <p class=\"schema-faq-answer\">Significa que Nginx, al actuar como puerta de enlace o proxy, ha recibido una respuesta no v\u00e1lida de un servidor de origen. La causa suele ser un servicio de backend detenido o un problema de conexi\u00f3n con el servidor de origen.<\/p> <\/div> <div class=\"schema-faq-section\" id=\"faq-question-1793529240063\"><strong class=\"schema-faq-question\">\u00bfReiniciar Nginx soluciona un error 502?<\/strong> <p class=\"schema-faq-answer\">No necesariamente. Reiniciar o recargar Nginx no solucionar\u00e1 una aplicaci\u00f3n que no est\u00e1 disponible, un puerto de backend incorrecto ni la ausencia de un socket de PHP-FPM.<\/p> <\/div> <div class=\"schema-faq-section\" id=\"faq-question-1793529252450\"><strong class=\"schema-faq-question\">\u00bfCu\u00e1l es la diferencia entre HTTP 502 y HTTP 504?<\/strong> <p class=\"schema-faq-answer\">Un error 502 indica que el servidor de origen ha enviado una respuesta no v\u00e1lida, mientras que un error 504 significa que la puerta de enlace no ha recibido una respuesta del servidor de origen dentro del tiempo de espera establecido.<\/p> <\/div> <div class=\"schema-faq-section\" id=\"faq-question-1793529289265\"><strong class=\"schema-faq-question\">\u00bfPuede una cantidad insuficiente de RAM provocar un error 502 Bad Gateway?<\/strong> <p class=\"schema-faq-answer\">S\u00ed. Si se agota la memoria, los procesos de backend pueden fallar o terminarse, lo que impide que Nginx se comunique con ellos.<\/p> <\/div> <div class=\"schema-faq-section\" id=\"faq-question-1793529308749\"><strong class=\"schema-faq-question\">\u00bfNginx es siempre la causa de un error 502?<\/strong> <p class=\"schema-faq-answer\">No. Otras puertas de enlace, proxies, CDN y balanceadores de carga tambi\u00e9n pueden devolver errores HTTP 502.<\/p> <\/div> <\/div>\n\n<h2 id=\"h-conclusion\" class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Conclusion\"><\/span>Conclusi\u00f3n<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n<p class=\"wp-block-paragraph\">Para solucionar un <strong>error 502 Bad Gateway en Nginx<\/strong>, primero hay que averiguar por qu\u00e9 la aplicaci\u00f3n de origen no responde correctamente.<\/p>\n\n<p class=\"wp-block-paragraph\">Revisa primero los registros de errores de Nginx, confirma que el servicio de backend est\u00e1 en ejecuci\u00f3n y comprueba el puerto o el socket configurado. Despu\u00e9s, investiga los l\u00edmites de recursos, los permisos y los fallos de la aplicaci\u00f3n.<\/p>\n\n<p class=\"wp-block-paragraph\">En la mayor\u00eda de los casos, identificar el fallo concreto del servidor de origen es m\u00e1s eficaz que reiniciar Nginx repetidamente o cambiar los tiempos de espera.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Un error 502 Bad Gateway en Nginx suele significar que Nginx no ha podido recibir una respuesta v\u00e1lida de un servidor de origen, como PHP-FPM, Node.js u otra aplicaci\u00f3n de backend. Las causas m\u00e1s habituales son servicios de aplicaciones detenidos, puertos o sockets de origen incorrectos y procesos de backend que fallan o cierran las [&hellip;]<\/p>\n","protected":false},"author":8,"featured_media":5057,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"default","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"categories":[507],"tags":[],"class_list":["post-5056","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-tutoriales-linux"],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v27.4 (Yoast SEO v28.8) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>C\u00f3mo solucionar el error 502 Bad Gateway en Nginx (paso a paso)<\/title>\n<meta name=\"description\" content=\"Soluciona los errores 502 Bad Gateway en Nginx revisando los registros, los servidores de origen, PHP-FPM, la configuraci\u00f3n del proxy y los recursos del servidor con comandos de Linux.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/zynoo.com\/blog\/es\/502-bad-gateway-nginx\/\" \/>\n<meta property=\"og:locale\" content=\"es_ES\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"C\u00f3mo solucionar el error 502 Bad Gateway en Nginx (paso a paso)\" \/>\n<meta property=\"og:description\" content=\"Soluciona los errores 502 Bad Gateway en Nginx revisando los registros, los servidores de origen, PHP-FPM, la configuraci\u00f3n del proxy y los recursos del servidor con comandos de Linux.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/zynoo.com\/blog\/es\/502-bad-gateway-nginx\/\" \/>\n<meta property=\"og:site_name\" content=\"ZYNOO Blog\" \/>\n<meta property=\"article:published_time\" content=\"2026-11-01T10:52:40+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-11-01T16:14:13+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/zynoo.com\/blog\/wp-content\/uploads\/2026\/11\/502-Bad-Gateway-Nginx.webp\" \/>\n\t<meta property=\"og:image:width\" content=\"1672\" \/>\n\t<meta property=\"og:image:height\" content=\"941\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/webp\" \/>\n<meta name=\"author\" content=\"Adam Weller\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Escrito por\" \/>\n\t<meta name=\"twitter:data1\" content=\"Adam Weller\" \/>\n\t<meta name=\"twitter:label2\" content=\"Tiempo de lectura\" \/>\n\t<meta name=\"twitter:data2\" content=\"6 minutos\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"TechArticle\",\"@id\":\"https:\\\/\\\/zynoo.com\\\/blog\\\/es\\\/502-bad-gateway-nginx\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/zynoo.com\\\/blog\\\/es\\\/502-bad-gateway-nginx\\\/\"},\"author\":{\"name\":\"Adam Weller\",\"@id\":\"https:\\\/\\\/zynoo.com\\\/blog\\\/es\\\/#\\\/schema\\\/person\\\/dc0f08d1e3da74e3d4ae21a072525738\"},\"headline\":\"C\u00f3mo solucionar el error 502 Bad Gateway en Nginx (paso a paso)\",\"datePublished\":\"2026-11-01T10:52:40+00:00\",\"dateModified\":\"2026-11-01T16:14:13+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/zynoo.com\\\/blog\\\/es\\\/502-bad-gateway-nginx\\\/\"},\"wordCount\":1628,\"publisher\":{\"@id\":\"https:\\\/\\\/zynoo.com\\\/blog\\\/es\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/zynoo.com\\\/blog\\\/es\\\/502-bad-gateway-nginx\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/zynoo.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/502-Bad-Gateway-Nginx.webp\",\"articleSection\":[\"Tutoriales de Linux\"],\"inLanguage\":\"es\"},{\"@type\":[\"WebPage\",\"FAQPage\"],\"@id\":\"https:\\\/\\\/zynoo.com\\\/blog\\\/es\\\/502-bad-gateway-nginx\\\/\",\"url\":\"https:\\\/\\\/zynoo.com\\\/blog\\\/es\\\/502-bad-gateway-nginx\\\/\",\"name\":\"C\u00f3mo solucionar el error 502 Bad Gateway en Nginx (paso a paso)\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/zynoo.com\\\/blog\\\/es\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/zynoo.com\\\/blog\\\/es\\\/502-bad-gateway-nginx\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/zynoo.com\\\/blog\\\/es\\\/502-bad-gateway-nginx\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/zynoo.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/502-Bad-Gateway-Nginx.webp\",\"datePublished\":\"2026-11-01T10:52:40+00:00\",\"dateModified\":\"2026-11-01T16:14:13+00:00\",\"description\":\"Soluciona los errores 502 Bad Gateway en Nginx revisando los registros, los servidores de origen, PHP-FPM, la configuraci\u00f3n del proxy y los recursos del servidor con comandos de Linux.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/zynoo.com\\\/blog\\\/es\\\/502-bad-gateway-nginx\\\/#breadcrumb\"},\"mainEntity\":[{\"@id\":\"https:\\\/\\\/zynoo.com\\\/blog\\\/es\\\/502-bad-gateway-nginx\\\/#faq-question-1793529208055\"},{\"@id\":\"https:\\\/\\\/zynoo.com\\\/blog\\\/es\\\/502-bad-gateway-nginx\\\/#faq-question-1793529240063\"},{\"@id\":\"https:\\\/\\\/zynoo.com\\\/blog\\\/es\\\/502-bad-gateway-nginx\\\/#faq-question-1793529252450\"},{\"@id\":\"https:\\\/\\\/zynoo.com\\\/blog\\\/es\\\/502-bad-gateway-nginx\\\/#faq-question-1793529289265\"},{\"@id\":\"https:\\\/\\\/zynoo.com\\\/blog\\\/es\\\/502-bad-gateway-nginx\\\/#faq-question-1793529308749\"}],\"inLanguage\":\"es\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/zynoo.com\\\/blog\\\/es\\\/502-bad-gateway-nginx\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"es\",\"@id\":\"https:\\\/\\\/zynoo.com\\\/blog\\\/es\\\/502-bad-gateway-nginx\\\/#primaryimage\",\"url\":\"https:\\\/\\\/zynoo.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/502-Bad-Gateway-Nginx.webp\",\"contentUrl\":\"https:\\\/\\\/zynoo.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/502-Bad-Gateway-Nginx.webp\",\"width\":1672,\"height\":941,\"caption\":\"Error 502 Bad Gateway en Nginx\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/zynoo.com\\\/blog\\\/es\\\/502-bad-gateway-nginx\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/zynoo.com\\\/blog\\\/es\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Tutoriales de Linux\",\"item\":\"https:\\\/\\\/zynoo.com\\\/blog\\\/es\\\/category\\\/tutoriales-linux\\\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"C\u00f3mo solucionar el error 502 Bad Gateway en Nginx (paso a paso)\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/zynoo.com\\\/blog\\\/es\\\/#website\",\"url\":\"https:\\\/\\\/zynoo.com\\\/blog\\\/es\\\/\",\"name\":\"Zynoo Blog\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\\\/\\\/zynoo.com\\\/blog\\\/es\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/zynoo.com\\\/blog\\\/es\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"es\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/zynoo.com\\\/blog\\\/es\\\/#organization\",\"name\":\"ZYNOO\",\"url\":\"https:\\\/\\\/zynoo.com\\\/blog\\\/es\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"es\",\"@id\":\"https:\\\/\\\/zynoo.com\\\/blog\\\/es\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/zynoo.com\\\/blog\\\/wp-content\\\/uploads\\\/2025\\\/08\\\/logo.png\",\"contentUrl\":\"https:\\\/\\\/zynoo.com\\\/blog\\\/wp-content\\\/uploads\\\/2025\\\/08\\\/logo.png\",\"width\":149,\"height\":31,\"caption\":\"ZYNOO\"},\"image\":{\"@id\":\"https:\\\/\\\/zynoo.com\\\/blog\\\/es\\\/#\\\/schema\\\/logo\\\/image\\\/\"}},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/zynoo.com\\\/blog\\\/es\\\/#\\\/schema\\\/person\\\/dc0f08d1e3da74e3d4ae21a072525738\",\"name\":\"Adam Weller\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"es\",\"@id\":\"https:\\\/\\\/zynoo.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/adam-weller-v2-96x96.jpg\",\"url\":\"https:\\\/\\\/zynoo.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/adam-weller-v2-96x96.jpg\",\"contentUrl\":\"https:\\\/\\\/zynoo.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/adam-weller-v2-96x96.jpg\",\"caption\":\"Adam Weller\"},\"description\":\"Adam Weller covers web hosting, Linux and online projects for the ZYNOO blog.\",\"url\":\"https:\\\/\\\/zynoo.com\\\/blog\\\/es\\\/author\\\/adam-weller\\\/\"},{\"@type\":\"Question\",\"@id\":\"https:\\\/\\\/zynoo.com\\\/blog\\\/es\\\/502-bad-gateway-nginx\\\/#faq-question-1793529208055\",\"position\":1,\"url\":\"https:\\\/\\\/zynoo.com\\\/blog\\\/es\\\/502-bad-gateway-nginx\\\/#faq-question-1793529208055\",\"name\":\"\u00bfQu\u00e9 significa 502 Bad Gateway en Nginx?\",\"answerCount\":1,\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Significa que Nginx, al actuar como puerta de enlace o proxy, ha recibido una respuesta no v\u00e1lida de un servidor de origen. La causa suele ser un servicio de backend detenido o un problema de conexi\u00f3n con el servidor de origen.\",\"inLanguage\":\"es\"},\"inLanguage\":\"es\"},{\"@type\":\"Question\",\"@id\":\"https:\\\/\\\/zynoo.com\\\/blog\\\/es\\\/502-bad-gateway-nginx\\\/#faq-question-1793529240063\",\"position\":2,\"url\":\"https:\\\/\\\/zynoo.com\\\/blog\\\/es\\\/502-bad-gateway-nginx\\\/#faq-question-1793529240063\",\"name\":\"\u00bfReiniciar Nginx soluciona un error 502?\",\"answerCount\":1,\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"No necesariamente. Reiniciar o recargar Nginx no solucionar\u00e1 una aplicaci\u00f3n que no est\u00e1 disponible, un puerto de backend incorrecto ni la ausencia de un socket de PHP-FPM.\",\"inLanguage\":\"es\"},\"inLanguage\":\"es\"},{\"@type\":\"Question\",\"@id\":\"https:\\\/\\\/zynoo.com\\\/blog\\\/es\\\/502-bad-gateway-nginx\\\/#faq-question-1793529252450\",\"position\":3,\"url\":\"https:\\\/\\\/zynoo.com\\\/blog\\\/es\\\/502-bad-gateway-nginx\\\/#faq-question-1793529252450\",\"name\":\"\u00bfCu\u00e1l es la diferencia entre HTTP 502 y HTTP 504?\",\"answerCount\":1,\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Un error 502 indica que el servidor de origen ha enviado una respuesta no v\u00e1lida, mientras que un error 504 significa que la puerta de enlace no ha recibido una respuesta del servidor de origen dentro del tiempo de espera establecido.\",\"inLanguage\":\"es\"},\"inLanguage\":\"es\"},{\"@type\":\"Question\",\"@id\":\"https:\\\/\\\/zynoo.com\\\/blog\\\/es\\\/502-bad-gateway-nginx\\\/#faq-question-1793529289265\",\"position\":4,\"url\":\"https:\\\/\\\/zynoo.com\\\/blog\\\/es\\\/502-bad-gateway-nginx\\\/#faq-question-1793529289265\",\"name\":\"\u00bfPuede una cantidad insuficiente de RAM provocar un error 502 Bad Gateway?\",\"answerCount\":1,\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"S\u00ed. Si se agota la memoria, los procesos de backend pueden fallar o terminarse, lo que impide que Nginx se comunique con ellos.\",\"inLanguage\":\"es\"},\"inLanguage\":\"es\"},{\"@type\":\"Question\",\"@id\":\"https:\\\/\\\/zynoo.com\\\/blog\\\/es\\\/502-bad-gateway-nginx\\\/#faq-question-1793529308749\",\"position\":5,\"url\":\"https:\\\/\\\/zynoo.com\\\/blog\\\/es\\\/502-bad-gateway-nginx\\\/#faq-question-1793529308749\",\"name\":\"\u00bfNginx es siempre la causa de un error 502?\",\"answerCount\":1,\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"No. Otras puertas de enlace, proxies, CDN y balanceadores de carga tambi\u00e9n pueden devolver errores HTTP 502.\",\"inLanguage\":\"es\"},\"inLanguage\":\"es\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"C\u00f3mo solucionar el error 502 Bad Gateway en Nginx (paso a paso)","description":"Soluciona los errores 502 Bad Gateway en Nginx revisando los registros, los servidores de origen, PHP-FPM, la configuraci\u00f3n del proxy y los recursos del servidor con comandos de Linux.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/zynoo.com\/blog\/es\/502-bad-gateway-nginx\/","og_locale":"es_ES","og_type":"article","og_title":"C\u00f3mo solucionar el error 502 Bad Gateway en Nginx (paso a paso)","og_description":"Soluciona los errores 502 Bad Gateway en Nginx revisando los registros, los servidores de origen, PHP-FPM, la configuraci\u00f3n del proxy y los recursos del servidor con comandos de Linux.","og_url":"https:\/\/zynoo.com\/blog\/es\/502-bad-gateway-nginx\/","og_site_name":"ZYNOO Blog","article_published_time":"2026-11-01T10:52:40+00:00","article_modified_time":"2026-11-01T16:14:13+00:00","og_image":[{"width":1672,"height":941,"url":"https:\/\/zynoo.com\/blog\/wp-content\/uploads\/2026\/11\/502-Bad-Gateway-Nginx.webp","type":"image\/webp"}],"author":"Adam Weller","twitter_card":"summary_large_image","twitter_misc":{"Escrito por":"Adam Weller","Tiempo de lectura":"6 minutos"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"TechArticle","@id":"https:\/\/zynoo.com\/blog\/es\/502-bad-gateway-nginx\/#article","isPartOf":{"@id":"https:\/\/zynoo.com\/blog\/es\/502-bad-gateway-nginx\/"},"author":{"name":"Adam Weller","@id":"https:\/\/zynoo.com\/blog\/es\/#\/schema\/person\/dc0f08d1e3da74e3d4ae21a072525738"},"headline":"C\u00f3mo solucionar el error 502 Bad Gateway en Nginx (paso a paso)","datePublished":"2026-11-01T10:52:40+00:00","dateModified":"2026-11-01T16:14:13+00:00","mainEntityOfPage":{"@id":"https:\/\/zynoo.com\/blog\/es\/502-bad-gateway-nginx\/"},"wordCount":1628,"publisher":{"@id":"https:\/\/zynoo.com\/blog\/es\/#organization"},"image":{"@id":"https:\/\/zynoo.com\/blog\/es\/502-bad-gateway-nginx\/#primaryimage"},"thumbnailUrl":"https:\/\/zynoo.com\/blog\/wp-content\/uploads\/2026\/11\/502-Bad-Gateway-Nginx.webp","articleSection":["Tutoriales de Linux"],"inLanguage":"es"},{"@type":["WebPage","FAQPage"],"@id":"https:\/\/zynoo.com\/blog\/es\/502-bad-gateway-nginx\/","url":"https:\/\/zynoo.com\/blog\/es\/502-bad-gateway-nginx\/","name":"C\u00f3mo solucionar el error 502 Bad Gateway en Nginx (paso a paso)","isPartOf":{"@id":"https:\/\/zynoo.com\/blog\/es\/#website"},"primaryImageOfPage":{"@id":"https:\/\/zynoo.com\/blog\/es\/502-bad-gateway-nginx\/#primaryimage"},"image":{"@id":"https:\/\/zynoo.com\/blog\/es\/502-bad-gateway-nginx\/#primaryimage"},"thumbnailUrl":"https:\/\/zynoo.com\/blog\/wp-content\/uploads\/2026\/11\/502-Bad-Gateway-Nginx.webp","datePublished":"2026-11-01T10:52:40+00:00","dateModified":"2026-11-01T16:14:13+00:00","description":"Soluciona los errores 502 Bad Gateway en Nginx revisando los registros, los servidores de origen, PHP-FPM, la configuraci\u00f3n del proxy y los recursos del servidor con comandos de Linux.","breadcrumb":{"@id":"https:\/\/zynoo.com\/blog\/es\/502-bad-gateway-nginx\/#breadcrumb"},"mainEntity":[{"@id":"https:\/\/zynoo.com\/blog\/es\/502-bad-gateway-nginx\/#faq-question-1793529208055"},{"@id":"https:\/\/zynoo.com\/blog\/es\/502-bad-gateway-nginx\/#faq-question-1793529240063"},{"@id":"https:\/\/zynoo.com\/blog\/es\/502-bad-gateway-nginx\/#faq-question-1793529252450"},{"@id":"https:\/\/zynoo.com\/blog\/es\/502-bad-gateway-nginx\/#faq-question-1793529289265"},{"@id":"https:\/\/zynoo.com\/blog\/es\/502-bad-gateway-nginx\/#faq-question-1793529308749"}],"inLanguage":"es","potentialAction":[{"@type":"ReadAction","target":["https:\/\/zynoo.com\/blog\/es\/502-bad-gateway-nginx\/"]}]},{"@type":"ImageObject","inLanguage":"es","@id":"https:\/\/zynoo.com\/blog\/es\/502-bad-gateway-nginx\/#primaryimage","url":"https:\/\/zynoo.com\/blog\/wp-content\/uploads\/2026\/11\/502-Bad-Gateway-Nginx.webp","contentUrl":"https:\/\/zynoo.com\/blog\/wp-content\/uploads\/2026\/11\/502-Bad-Gateway-Nginx.webp","width":1672,"height":941,"caption":"Error 502 Bad Gateway en Nginx"},{"@type":"BreadcrumbList","@id":"https:\/\/zynoo.com\/blog\/es\/502-bad-gateway-nginx\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/zynoo.com\/blog\/es\/"},{"@type":"ListItem","position":2,"name":"Tutoriales de Linux","item":"https:\/\/zynoo.com\/blog\/es\/category\/tutoriales-linux\/"},{"@type":"ListItem","position":3,"name":"C\u00f3mo solucionar el error 502 Bad Gateway en Nginx (paso a paso)"}]},{"@type":"WebSite","@id":"https:\/\/zynoo.com\/blog\/es\/#website","url":"https:\/\/zynoo.com\/blog\/es\/","name":"Zynoo Blog","description":"","publisher":{"@id":"https:\/\/zynoo.com\/blog\/es\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/zynoo.com\/blog\/es\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"es"},{"@type":"Organization","@id":"https:\/\/zynoo.com\/blog\/es\/#organization","name":"ZYNOO","url":"https:\/\/zynoo.com\/blog\/es\/","logo":{"@type":"ImageObject","inLanguage":"es","@id":"https:\/\/zynoo.com\/blog\/es\/#\/schema\/logo\/image\/","url":"https:\/\/zynoo.com\/blog\/wp-content\/uploads\/2025\/08\/logo.png","contentUrl":"https:\/\/zynoo.com\/blog\/wp-content\/uploads\/2025\/08\/logo.png","width":149,"height":31,"caption":"ZYNOO"},"image":{"@id":"https:\/\/zynoo.com\/blog\/es\/#\/schema\/logo\/image\/"}},{"@type":"Person","@id":"https:\/\/zynoo.com\/blog\/es\/#\/schema\/person\/dc0f08d1e3da74e3d4ae21a072525738","name":"Adam Weller","image":{"@type":"ImageObject","inLanguage":"es","@id":"https:\/\/zynoo.com\/blog\/wp-content\/uploads\/2026\/11\/adam-weller-v2-96x96.jpg","url":"https:\/\/zynoo.com\/blog\/wp-content\/uploads\/2026\/11\/adam-weller-v2-96x96.jpg","contentUrl":"https:\/\/zynoo.com\/blog\/wp-content\/uploads\/2026\/11\/adam-weller-v2-96x96.jpg","caption":"Adam Weller"},"description":"Adam Weller covers web hosting, Linux and online projects for the ZYNOO blog.","url":"https:\/\/zynoo.com\/blog\/es\/author\/adam-weller\/"},{"@type":"Question","@id":"https:\/\/zynoo.com\/blog\/es\/502-bad-gateway-nginx\/#faq-question-1793529208055","position":1,"url":"https:\/\/zynoo.com\/blog\/es\/502-bad-gateway-nginx\/#faq-question-1793529208055","name":"\u00bfQu\u00e9 significa 502 Bad Gateway en Nginx?","answerCount":1,"acceptedAnswer":{"@type":"Answer","text":"Significa que Nginx, al actuar como puerta de enlace o proxy, ha recibido una respuesta no v\u00e1lida de un servidor de origen. La causa suele ser un servicio de backend detenido o un problema de conexi\u00f3n con el servidor de origen.","inLanguage":"es"},"inLanguage":"es"},{"@type":"Question","@id":"https:\/\/zynoo.com\/blog\/es\/502-bad-gateway-nginx\/#faq-question-1793529240063","position":2,"url":"https:\/\/zynoo.com\/blog\/es\/502-bad-gateway-nginx\/#faq-question-1793529240063","name":"\u00bfReiniciar Nginx soluciona un error 502?","answerCount":1,"acceptedAnswer":{"@type":"Answer","text":"No necesariamente. Reiniciar o recargar Nginx no solucionar\u00e1 una aplicaci\u00f3n que no est\u00e1 disponible, un puerto de backend incorrecto ni la ausencia de un socket de PHP-FPM.","inLanguage":"es"},"inLanguage":"es"},{"@type":"Question","@id":"https:\/\/zynoo.com\/blog\/es\/502-bad-gateway-nginx\/#faq-question-1793529252450","position":3,"url":"https:\/\/zynoo.com\/blog\/es\/502-bad-gateway-nginx\/#faq-question-1793529252450","name":"\u00bfCu\u00e1l es la diferencia entre HTTP 502 y HTTP 504?","answerCount":1,"acceptedAnswer":{"@type":"Answer","text":"Un error 502 indica que el servidor de origen ha enviado una respuesta no v\u00e1lida, mientras que un error 504 significa que la puerta de enlace no ha recibido una respuesta del servidor de origen dentro del tiempo de espera establecido.","inLanguage":"es"},"inLanguage":"es"},{"@type":"Question","@id":"https:\/\/zynoo.com\/blog\/es\/502-bad-gateway-nginx\/#faq-question-1793529289265","position":4,"url":"https:\/\/zynoo.com\/blog\/es\/502-bad-gateway-nginx\/#faq-question-1793529289265","name":"\u00bfPuede una cantidad insuficiente de RAM provocar un error 502 Bad Gateway?","answerCount":1,"acceptedAnswer":{"@type":"Answer","text":"S\u00ed. Si se agota la memoria, los procesos de backend pueden fallar o terminarse, lo que impide que Nginx se comunique con ellos.","inLanguage":"es"},"inLanguage":"es"},{"@type":"Question","@id":"https:\/\/zynoo.com\/blog\/es\/502-bad-gateway-nginx\/#faq-question-1793529308749","position":5,"url":"https:\/\/zynoo.com\/blog\/es\/502-bad-gateway-nginx\/#faq-question-1793529308749","name":"\u00bfNginx es siempre la causa de un error 502?","answerCount":1,"acceptedAnswer":{"@type":"Answer","text":"No. Otras puertas de enlace, proxies, CDN y balanceadores de carga tambi\u00e9n pueden devolver errores HTTP 502.","inLanguage":"es"},"inLanguage":"es"}]}},"_links":{"self":[{"href":"https:\/\/zynoo.com\/blog\/es\/wp-json\/wp\/v2\/posts\/5056","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/zynoo.com\/blog\/es\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/zynoo.com\/blog\/es\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/zynoo.com\/blog\/es\/wp-json\/wp\/v2\/users\/8"}],"replies":[{"embeddable":true,"href":"https:\/\/zynoo.com\/blog\/es\/wp-json\/wp\/v2\/comments?post=5056"}],"version-history":[{"count":4,"href":"https:\/\/zynoo.com\/blog\/es\/wp-json\/wp\/v2\/posts\/5056\/revisions"}],"predecessor-version":[{"id":5442,"href":"https:\/\/zynoo.com\/blog\/es\/wp-json\/wp\/v2\/posts\/5056\/revisions\/5442"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/zynoo.com\/blog\/es\/wp-json\/wp\/v2\/media\/5057"}],"wp:attachment":[{"href":"https:\/\/zynoo.com\/blog\/es\/wp-json\/wp\/v2\/media?parent=5056"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/zynoo.com\/blog\/es\/wp-json\/wp\/v2\/categories?post=5056"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/zynoo.com\/blog\/es\/wp-json\/wp\/v2\/tags?post=5056"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}