{"id":5742,"date":"2024-11-07T03:23:42","date_gmt":"2024-11-06T21:53:42","guid":{"rendered":"https:\/\/www.veeble.com\/kb\/?p=5742"},"modified":"2025-03-13T11:17:18","modified_gmt":"2025-03-13T05:47:18","slug":"fix-nginx-503-service-temporarily-unavailable-error","status":"publish","type":"post","link":"https:\/\/www.veeble.com\/kb\/fix-nginx-503-service-temporarily-unavailable-error\/","title":{"rendered":"How to Fix “NGINX 503 Service Temporarily Unavailable” Error"},"content":{"rendered":"\n
\n
\"NGINX<\/a><\/figure>\n<\/figure>\n\n\n\n

<\/p>\n\n\n\n

Seeing the “503 Service Temporarily Unavailable”<\/strong> error on your NGINX-powered website can be frustrating. But don\u2019t worry; some methods exist to troubleshoot and fix this issue. In this guide, I will help you solve this issue easily.<\/p>\n\n\n\n

Why 503 Service Unavailable Error?<\/strong>
A 503 error usually means the server is temporarily unable to handle the request. It\u2019s like the website\u2019s office is closed, even though it should be open. Often, it occurs because the server is overloaded or the back-end service (like PHP or a database) isn\u2019t running correctly. <\/pre>\n\n\n\n
<\/p>\n\n\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t\tStep-by-Step Fixes\t\t\t\t\t\t<\/div>\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t
\n\t\t\t\t\t\t
  1. Check If PHP-FPM Is Running<\/a>
  2. Try Restarting NGINX and PHP-FPM<\/a>
  3. Check if your server is overloaded<\/a>
  4. Check Out the Logs<\/a>
  5. Double-Check Your NGINX Config<\/a>
  6. Tweak PHP-FPM Settings<\/a>
  7. Empower Your Business with Veeble VPS Hosting<\/a><\/ol>\t\t\t\t\t<\/div>\n\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\n\n\n
    <\/p>\n\n\n
    Check If PHP-FPM Is Running<\/h3>\n\n\n
    If your site runs on PHP, first see if PHP-FPM<\/a> is even up. To do it, open a terminal and run the command:<\/p>\n\n\n\n
    sudo systemctl status php-fpm<\/code><\/pre>\n\n\n\n
    (If you\u2019re using a specific version, like PHP 7.4, try sudo systemctl status php7.4-fpm<\/code> instead.)
    If PHP-FPM is dead or inactive, bring it back to life with: sudo systemctl start php-fpm<\/code>
    If it doesn\u2019t start up, the logs can be your best friend. Check: \/var\/log\/php-fpm\/<\/code><\/p>\n\n\n\n
    \n
    \"check<\/a><\/figure>\n<\/figure>\n\n\n\n
    <\/p>\n\n\n
    Try Restarting NGINX and PHP-FPM<\/h3>\n\n\n
    Sometimes, turning things off and on again really does work!. Then try running the following commands:<\/p>\n\n\n\n
    sudo systemctl restart nginx
    sudo systemctl restart php-fpm<\/code><\/pre>\n\n\n\n
    This will reset connections and clear up temporary hiccups.<\/p>\n\n\n\n
    \n
    \"Restart<\/a><\/figure>\n<\/figure>\n\n\n\n
    <\/p>\n\n\n
    Check if your server is overloaded<\/h3>\n\n\n
    Use commands like top<\/a> or htop<\/a> to see what\u2019s eating up your resources. If a process is hogging everything, it might be time to optimize your setup or add caching.<\/p>\n\n\n\n
    top<\/code><\/pre>\n\n\n\n
    htop<\/code><\/pre>\n\n\n\n
    \n
    \"top<\/a><\/figure>\n<\/figure>\n\n\n\n
    Also read: https:\/\/www.veeble.com\/kb\/linux-memory-monitoring-optimization-commands\/<\/a> for references.<\/p>\n\n\n\n
    \"If resource constraints keep causing you problems, a VPS or cloud plan from Veeble<\/a> can offer the extra RAM and CPU power you need to handle more traffic smoothly.<\/em>\"<\/pre>\n\n\n\n
    <\/p>\n\n\n
    Check Out the Logs<\/h3>\n\n\n
    Logs are like the black box of your server. They hold clues about what went wrong. To find the clues, check out the error log files:<\/p>\n\n\n\n
    NGINX error logs: \/var\/log\/nginx\/error.log<\/code>
    PHP-FPM error logs: \/var\/log\/php-fpm\/error.log<\/code><\/p>\n\n\n\n
    sudo tail -f \/var\/log\/nginx\/error.log<\/code><\/pre>\n\n\n\n
    sudo tail -f \/var\/log\/php-fpm\/error.log<\/code><\/pre>\n\n\n\n
    The above commands read out the errors and give a clue on how to resolve the issue. Watch out for \u201cupstream\u201d errors, which often mean PHP-FPM isn\u2019t working right in \/var\/log\/php-fpm\/error.log<\/code><\/p>\n\n\n\n
    <\/p>\n\n\n
    Double-Check Your NGINX Config<\/h3>\n\n\n
    Sometimes, a tiny typo in your configuration can bring down the whole show. To check it, execute the below command:<\/p>\n\n\n\n
    sudo nginx -t<\/code><\/pre>\n\n\n\n
    If there are errors, fix them first and reload NGINX with the below command:<\/p>\n\n\n\n
    sudo systemctl reload nginx<\/code><\/pre>\n\n\n\n
    \n
    \"sudo<\/a><\/figure>\n<\/figure>\n\n\n\n
    <\/p>\n\n\n
    Tweak PHP-FPM Settings<\/h3>\n\n\n
    If your server is under heavy load, you might need to adjust PHP-FPM settings. The config file is usually at \/etc\/php\/7.4\/fpm\/pool.d\/www.conf<\/code>
    Try tweaking the following values and see if it resolves after tweaking it.<\/p>\n\n\n\n