DE

↑ ↓ select, Enter open, Esc close

Show nginx errors of a Plesk domain (502, 504)

harmless rootPleskdebian, ubuntu
Adjust the values, the command updates live
root@server
tail -n 50 /var/www/vhosts/system/example.com/logs/proxy_error_log

Prints the last 50 lines of a domain’s nginx error log. With 502 Bad Gateway or 504 Gateway Timeout, this shows whether Apache or PHP-FPM did not respond or the connection was dropped.

Also searched as

  • 502 bad gateway plesk cause
  • 504 gateway timeout domain plesk
  • nginx error log domain plesk

Related one-liners

All in Plesk

Check the Plesk installer log after a failed update

#tail -n 100 /var/log/plesk/install/autoinstaller3.log
harmlessPlesk

Follow the Plesk panel log in real time

#tail -f /var/log/plesk/panel.log
harmlessPlesk

Regenerate the web server configuration of a domain

#plesk sbin httpdmng --reconfigure-domain example.com
cautionPlesk

Repair a domain's web server configuration with plesk repair

#plesk repair web example.com -y
cautionPlesk

Check whether nginx is enabled in Plesk

#plesk sbin nginxmng --status
harmlessnginx

Find the cause of a 502 Bad Gateway in the nginx log

#grep -E "upstream|connect\(\) failed" /var/log/nginx/error.log | tail -20
harmlessnginx

Read first, then run.

The commands on myline.de act directly on servers, files and databases. A wrong path or placeholder can delete data irreversibly or make a server unreachable.

  • All commands are provided without warranty and are not tested on every system.
  • Understand what a command does before running it, and check every placeholder.
  • Make a backup first and, if possible, try it on a test system.
  • You run commands at your own risk. Liability for damages is excluded to the extent permitted by law.