Server logs track server actions, including access details, errors, and their severity. In 10Web dashboard, you can search for errors, adjust the view, refresh logs, and access the three main types of server logs.
- ERROR.LOG
- ACCESS.LOG
- PHP-FRM.LOG
Note:
The server logs for live and staging environments are different. To access your staging environment server logs, please switch to the staging environment.
Viewing the server logs in your dashboard
To view your server access and error logs in 10Web dashboard:
- Log in to your 10Web account.
- On the Websites page, find the website you want to check and click Manage on its card.
- In the website's left sidebar, click Advanced to expand it, then under Hosting services, click Logs.
- At the top of the Logs page, use the drop-down menu (it shows ACCESS.LOG by default) to choose which log you want to view: ACCESS.LOG, ERROR.LOG, or PHP-FPM.LOG. You can also set how many lines to show, use Refresh to reload the log, or use the Search field to look for a specific entry.
Access.log
An access log records requests made to the server by clients or bots for files and files that are associated with the requested file. Access logs have a format by which the information is arranged in the list.
Access log format
$remote_addr - $remote_user [$time_local] $request $status $body_bytes_sent $http_referer $http_user_agent
Example
37.252.95.17 - - [12/Aug/2022:06:32:30 +0000] "GET /product-category/headphones/ HTTP/1.0" 200 87400 "https://uncommon-reptile.10web.me/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/104.0.0.0 Safari/537.36"
- $remote_addr - 37.252.95.17 - The IP address of the client trying to connect $remote_user - Authenticated user name.
- [$time_local] - [12/Aug/2022:06:32:30 +0000] - UTC local timestamp of when the request was made.
- $request - GET/product-category/headphones/HTTP - Defines the methods used to access the server: POST, GET, PUT, PATCH, DELETE, the URI identifying what is being accessed, and the protocol being used to access the server.
- $status - 200 - Success, redirection, client error, or server error codes.
- Body_bytes_sent - 87400 - The size of the request.
- $http_referer - https://uncommon-reptile.10web.me The URL that points to the URI.
- $http_user_agent - Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/104.0.0.0 Safari/537.36 - The type of browser and software used to make the request.
Error.log
The error.log records issues at different levels of severity while processing requests or running diagnostics. Viewing the error logs in the 10Web dashboard can guide you to find exactly where the error occurred. Once you find it, you can fix the error or correct the warning through SSH, an FTP client, or by contacting us via live chat.
Important:
If you are not a professional programmer, we recommend you contact customer care for support with fixing errors.
Error log format
UTC timestamp, severity level, error code, error ID, stderr message, client IP, site domain, HTTP/S request type, URI, protocol, upstream process handling request, internal host/port details, referrer URL.
Example
2022/08/12 06:28:30 [error] 3618#3618: *2472 FastCGI sent in stderr: "Unable to open primary script: /home/wplive/web/wp-live/wp-admin/index.php (No such file or directory)" while reading response header from upstream, client: 37.252.95.17, server: , request: "GET /wp-admin/? "fastcgi://unix:/var/run/php/php7.4-wplive.sock:", host: "uncommon-reptile.10web.me", referrer: "
- UTC timestamp - 2022/08/12 06:28:30 - Timestamp of when the error occurred.
- severity level - [error] - The level of the error that has occurred such as fatal or warning.
- error code - 3618#3618 - The code assigned to the error
- error ID - *2472 - the ID number assigned to the error.
- stderr message - Unable to open primary script: /home/wplive/web/wp-live/wp-admin/index.php (No such file or directory)" while reading response header from upstream - Explanation of the error.
- client IP - 37.252.95.17 - The IP address of the client.
- HTTP/S request type - GET - Defines the methods used to access the server: POST, GET, PUT, PATCH, DELETE
- URI - - Identifies what was being accessed.
- Protocol- HTTP - The protocol being used to request
- upstream process handling request -fastcgi://unix:/var/run/php/php7.4-wplive.sock - the system that takes care of the request
- internal host/port details - uncommon-reptile.10web.me - Name used by the server
- referrer URL - - The URL from which the request came
PHP-FPM.log
PHP - FPM stands for PHP FastCGI Process Manager. FPM manages and processes PHP code. If there are any errors in the PHP processes, this is where the record of those errors will be logged. The structure of the PHP - FPM line is the same as an error log.