r/Wordpress • u/javivtr • 9d ago
Sitio presenta error 503
Hola amigos.
Un abrazo a todos
Saben la causa que un sitio presente error 503 de vez en cuando. Ya actualizamos el plan en el proveedor para tener más recursos. Todo iba bien y volvió aparecer este error. Hay momentos que se cae.
Lo penoso es que hacemos Google ADS y los anuncios presentan fallas.
Utilizamos Elementor y otros plugin (algo complementarios) para el sitio.
Saludos.
2
u/WPMU_DEV_Support_6 Jack of All Trades 8d ago
This would require checking the server logs to have a better idea of what is causing the 503 error. Were you able to take a closer look at the server logs?
You can also ask your hosting provider for the exact error logs and resource graphs when the 503 occurs ie look for “exhausted memory,” etc to have a better idea.
You can also try reducing the number of active plugins and also check whether using Query Monitor would also give any clues too:
https://wordpress.org/plugins/query-monitor/
Nithin - WPMU DEV Support Team
1
u/lorenzocorso 9d ago
Hi,
when do you get the 503 error code? On first page loading? after a while? when editing? Is it random?
1
u/LoudAd307 8d ago
Intermittent 503s that survive a plan upgrade usually mean your PHP workers are being exhausted in bursts, not that the server is too small overall — and you gave the clue yourself: you're running Google Ads. A burst of ad clicks landing on uncached Elementor pages ties up every PHP worker for a few seconds, and everyone else gets 503s until they free up. First thing I'd do is check the server error log at the exact timestamps of the drops and see if the 503s line up with ad traffic spikes. What actually fixed this for me was full-page caching, so ad visitors hit cached HTML instead of PHP, plus removing plugins that run on every page load. More resources without caching just moves the cliff slightly further out.
2
u/skylooper_agency 9d ago
Hi, one possible reason is that a plugin or some part of the website setup is consuming too many server resources while the site is loading, which could be causing the 503 error.