Guide aaPanel file and log locations: cheat sheet

Guide aaPanel file and log locations: cheat sheet - Printable Version

+- AdminsForum (https://adminsforum.com)
+-- Forum: Free & open-source control panels (https://adminsforum.com/Forum-free-open-source-control-panels)
+--- Forum: aaPanel (https://adminsforum.com/Forum-aapanel)
+--- Thread: Guide aaPanel file and log locations: cheat sheet (/Thread-guide-aapanel-file-and-log-locations-cheat-sheet)

aaPanel file and log locations: cheat sheet - JAY - 10-07-2026

Where are aaPanel website files and logs?
On a standard installation, site files commonly live under /www/wwwroot/ and site logs under /www/wwwlogs/. Panel-managed software and configuration are commonly under /www/server/. Always confirm the selected site's document root and active service configuration; these examples are not universal paths.

Scope and review: Documentation reviewed 9 October 2026. These are common Linux aaPanel layouts. Custom roots, versions and web servers can differ. Exact paths and screenshots will be checked on the tutorial VPS; PHP 8.3 below is an example, not a version recommendation.

1. Website directory and logs

Code:

/www/wwwroot/example.com/
/www/wwwlogs/example.com.log
/www/wwwlogs/example.com.error.log

Replace example.com with the actual site. Open its aaPanel document-root and log controls to confirm the location. For frameworks, the public/running directory may be a subdirectory of the project. A blank or absent log is not evidence that the application is healthy.

2. Common web-server configuration locations

Code:

/www/server/nginx/conf/nginx.conf
/www/server/panel/vhost/nginx/
/www/server/panel/vhost/apache/
/www/server/panel/vhost/rewrite/

These are location examples, not commands to execute. Nginx, Apache and OpenLiteSpeed use different configurations. Prefer the panel's supported editor, save a backup and validate the correct service configuration before applying a change. Panel-generated files may be regenerated later.

3. PHP-FPM examples

Code:

/www/server/php/83/etc/php.ini
/www/server/php/83/etc/php-fpm.conf
/tmp/php-cgi-83.sock
/etc/init.d/php-fpm-83

Replace 83 with the installed version selected for the site. Confirm the actual listen value and upstream path: the command-line PHP version can differ from the website's PHP version. The socket is a service endpoint, not a file you should create manually.

4. Common data, panel and backup directories

Code:

/www/server/data/
/www/server/panel/
/www/backup/

Do not copy live database files as a substitute for a consistent database backup. Confirm the active data/backup paths in your configuration. A backup on the same disk does not protect against losing the server. Keep exports, archives and private configuration outside the site's public directory.

5. Read the relevant error, then verify
A read-only example for a confirmed site error-log path:

Code:

sudo tail -n 50 /www/wwwlogs/example.com.error.log

Reproduce the failing request once and correlate its time with the new log entry. Check both the web-server error and the relevant PHP/application log. Logs can contain credentials or personal data: redact them before sharing.

If a path is missing: Check whether the service is installed, which stack/version is active, and whether the site uses a custom directory or disabled logging. Do not create a guessed socket, recursively change permissions or delete files to make the example match.

Official references: Site directory and log controls; Service commands and common configuration paths.

Related: Diagnose a PHP-switching 502 · Website and SSL setup.