How to Properly Debug CyberPanel | Troubleshooting CyberPanel

Have a Question?
< All Topics

How to Properly Debug CyberPanel | Troubleshooting CyberPanel

There are two ways to troubleshoot any problem while using CyberPanel.

First Way of Troubleshooting CyberPanel

There is a global error log file (this file only contains logs generated by CyberPanel). This file can be reached at

https://<IP Address>:8090/serverstatus/cyberCPMainLogFile

Improved and detailed dynamic logging


Run command:

 touch /usr/local/CyberCP/debug

This will start generating more debug logs. If you find any issue with CyberPanel, you can run this command and then capture the output of /home/cyberpanel/error-logs.txt and share it with our support team.


If you want logs in /home/cyberpanel/error-logs.txt to be emailed to you, please run touch /usr/local/CyberCP/emailDebug, you will get logs in your email. (Email of admin account will be used to send these notifications). This also includes notification if CyberPanel fails to obtain SSL for any domain.

Second Way of Troubleshooting CyberPanel

If you can not find anything reasonable using the first way, then open your command-line terminal and run

journalctl -f | grep lscpd

After running this command, go back to CyberPanel and do the same thing causing issues, and then come back to the terminal and capture the output.

Troubleshooting CyberPanel

Find errors in email problems

If for some reason your emails are not going through, you can use the below commands to capture the output and get to the bottom of the issue:

  1. journalctl -f | grep postfix (For email delivery issues)
  2. journalctl -f | grep dovecot (For issues related to Rainloop Webmail)

Run these commands and then perform the operation that was causing the error, which will get you to the bottom of the problem. If need our help, make sure to share the output logs depending on your support request.

Enable Django Debug Logs (To find out the reason for the 500 error on CyberPanel)

nano /usr/local/CyberCP/CyberCP/

find DEBUG = False and change it to DEBUG = True and then do systemctl restart lscpd

And then redo what you are doing and you will get the reason for 500 Error.

Table of Contents