Guide CyberPanel Log Files and Config File Locations: Where Everything Lives

Guide CyberPanel Log Files and Config File Locations: Where Everything Lives - Printable Version

+- AdminsForum (https://adminsforum.com)
+-- Forum: Free & open-source control panels (https://adminsforum.com/Forum-free-open-source-control-panels)
+--- Forum: CyberPanel (https://adminsforum.com/Forum-cyberpanel)
+---- Forum: CyberPanel Guides & Tutorials (https://adminsforum.com/Forum-cyberpanel-guides-tutorials)
+----- Forum: CyberPanel Getting Started Guides (https://adminsforum.com/Forum-cyberpanel-getting-started-guides)
+----- Thread: Guide CyberPanel Log Files and Config File Locations: Where Everything Lives (/Thread-guide-cyberpanel-log-files-and-config-file-locations-where-everything-lives)

CyberPanel Log Files and Config File Locations: Where Everything Lives - JAY - 10-26-2026

CyberPanel Log Files and Config File Locations: Where Everything Lives

When something breaks on a CyberPanel server, the answer is almost always in a log file. The hard part is knowing which one. Here's the map, checked on our CyberPanel 3.0 test server.

Log files
Here are the log files that existed on our fresh server with one website:

Code:

/home/cyber.adminslab.com/logs/cyber.adminslab.com.access_log
/home/cyber.adminslab.com/logs/cyber.adminslab.com.error_log
/home/cyberpanel/error-logs.txt
/usr/local/lscp/logs/access.log
/usr/local/lscp/logs/error.log
/usr/local/lscp/logs/error.log.2026_10_24
/usr/local/lscp/logs/error.log.2026_10_24.01
/usr/local/lscp/logs/error.log.2026_10_24.02
/usr/local/lscp/logs/error.log.2026_10_24.03
/usr/local/lscp/logs/error.log.2026_10_24.04
/usr/local/lscp/logs/lsrestart.log
/usr/local/lscp/logs/stderr.log
/usr/local/lsws/logs/access.log
/usr/local/lsws/logs/error.log
/usr/local/lsws/logs/lsrestart.log
/usr/local/lsws/logs/stderr.log
/var/log/installLogs.txt

CyberPanel (the panel itself):
Code:
/home/cyberpanel/error-logs.txt
. Errors from panel actions: creating sites, issuing SSL, backups.
Panel web server (lscpd, port 8090):
Code:
/usr/local/lscp/logs/error.log
and
Code:
access.log
. Older entries move to dated files like
Code:
error.log.2026_10_24.01
(ours had four on install day), so check those too.
OpenLiteSpeed (all websites):
Code:
/usr/local/lsws/logs/error.log
,
Code:
access.log
,
Code:
stderr.log
(PHP fatal errors often land here) and
Code:
lsrestart.log
.
One website:
Code:
/home/yourdomain.com/logs/yourdomain.com.access_log
and
Code:
.error_log
.
Installer:
Code:
/var/log/installLogs.txt
. Read it if the install or an upgrade failed.
Mail (Postfix, Dovecot, OpenDKIM): Ubuntu 24.04 had no
Code:
/var/log/mail.log
on our server; use the journal:
Code:
journalctl -t postfix/smtp -t postfix/smtpd -t opendkim -n 100
.
Any service:
Code:
journalctl -u mariadb -n 50 --no-pager
(also
Code:
lscpd
,
Code:
lsws
,
Code:
pdns
,
Code:
pure-ftpd-mysql
,
Code:
dovecot
).

In the panel, Server has viewers for Access Logs, Error Logs, Email Logs and FTP Logs, and each website has a Logs tab.

Reading logs fast

Code:

tail -f /usr/local/lsws/logs/error.log          # watch live, Ctrl+C to stop
tail -n 50 /home/cyberpanel/error-logs.txt         # last 50 lines
grep -i "error" /home/yourdomain.com/logs/*error_log | tail -20
journalctl -u lscpd --since "1 hour ago" --no-pager

Tip: reproduce the problem with

Code:

tail -f

running in a second SSH window. The new lines that appear are the ones that matter.

Config file locations
All checked on our server:

OpenLiteSpeed main config:
Code:
/usr/local/lsws/conf/httpd_config.conf
A website's virtual host:
Code:
/usr/local/lsws/conf/vhosts/yourdomain.com/vhost.conf
(edit it from the panel: website > Config > vHost Conf)
PHP per version:
Code:
/usr/local/lsws/lsphp83/etc/php/8.3/litespeed/php.ini
(see changing PHP settings)
Website rewrite rules:
Code:
/home/yourdomain.com/public_html/.htaccess
Postfix:
Code:
/etc/postfix/main.cf
; Dovecot:
Code:
/etc/dovecot/dovecot.conf
; OpenDKIM:
Code:
/etc/opendkim.conf
and
Code:
/etc/opendkim/
Pure-FTPd:
Code:
/etc/pure-ftpd/conf/
(one setting per file)
PowerDNS:
Code:
/etc/powerdns/pdns.conf
MariaDB:
Code:
/etc/mysql/my.cnf
CyberPanel's own app settings:
Code:
/usr/local/CyberCP/CyberCP/settings.py
(don't edit unless you know why)
Saved passwords:
Code:
/etc/cyberpanel/
(root only; see resetting the admin password)

Before you edit a config file

Copy it:
Code:
cp file file.bak-$(date +%F)
Change one thing at a time.
Restart only the service you touched (
Code:
systemctl restart lsws
,
Code:
postfix
...), then check its log.
CyberPanel regenerates some files (vhost configs, OpenDKIM tables) when you change settings in the panel, so prefer the panel's editors where they exist.

More CyberPanel guides

Tested on CyberPanel 3.0 (build 8, OpenLiteSpeed edition) on Ubuntu 24.04, October 2026. Menu names can change slightly between versions.