WordPress Error Log
                     How to Set up and Use WordPress 
Error Log?
How to set up WordPress Error Logs?
There are two main server types: Apache and Nginx. Let’s see how to set up a WordPress error log for each of them.Apache is a powerful open-source solution for web servers. The logging capabilities in Apache are very flexible. Most log 
setting options are applicable to any operating system, but some of them are specific only for Unix or Linux.Apache by default is pretty well configured for logging one’s site. The standard httpd.conf file must have a section of logs with 
detailed comments for each directive. 
Apache WordPress Error Log
The WordPress error log contains messages from Apache like errors, 
notifications, warnings, etc. This log is very useful for finding and fixing 
server-side problems. It is written in the site’s Apache config file usually 
placed in /etc/apache/sites-available/ folder. Let’s see how to set up it:
If you want to store all information about errors in one log, this directive 
will suffice. However, you can specify a WordPress error log file for each 
domain.
Types of Errors
The following error levels are defined in Apache:
● emerg — emergency – the system does not function;
● alert — the error must be immediately corrected;
● crit is a critical error;
● error;
● warn — warning;
● notice — notification (normal operation);
● info — information message;
● debug — debug message.
WordPress Error Log Nginx
Log files are the first place to look for errors. Especially if it relates to a web 
server. In Nginx, there are only two main logs: error log and access log.
Logging of the Nginx errors occurs in a specific file, stderr, or Syslog. It 
collects all the errors that occurred during the operation of the webserver. 
By default, it is enabled globally:
To log only certain errors, you need to place a directive in the HTTP, server, 
stream, or location section. And so you can only log critical errors and 
alarms