Learn how to debug CyberPanel issues. Our CyberPanel Support team is here to help you with your questions and concerns.

How to Debug CyberPanel Issues

CyberPanel is a powerful hosting control panel. However, we are likely to run into issues from time to time.

Fortunately, CyberPanel offers built-in tools and logging mechanisms to help us reach the issue’s root.

Today, we will walk through two ways to troubleshoot CyberPanel and help us quickly identify common errors.

Method 1: Use CyberPanel’s Built-in Logs and Debugging

CyberPanel includes a centralized error log and options for more detailed debug logging.

1. First, head to the global log file maintained by CyberPanel that contains internal errors generated by the panel. We can access it at:

   https://:8090/serverstatus/cyberCPMainLogFile

   This file helps catch general system or configuration errors.
2. Next, activate dynamic debugging with this command:

   touch /usr/local/CyberCP/debug

   Once this is enabled, CyberPanel will generate more detailed logs in:

   /home/cyberpanel/error-logs.txt

   If we open a support ticket, this log file helps diagnose the issue.
3. If we want to receive error logs via email, enable the email debug feature:

   touch /usr/local/CyberCP/emailDebug

   This will trigger CyberPanel to email logs, including SSL-related failures and other errors, to the admin account’s email address. Speaking of SSL, if you’re running into issues with certificates, such as invalid or expired certs, you may find it helpful to learn how to remove SSL from a CyberPanel site, especially before reissuing a new one.
4. If we see a “blacklisted domain” error while creating a new site, especially on domain names that match the server’s hostname, this is due to a security enhancement introduced in version 2.1.2. CyberPanel now restricts the creation of sites on specific internal hostnames to prevent misconfiguration or abuse.

Additionally, if your CyberPanel site suddenly becomes unreachable or displays a connection error, this guide on fixing the “This site can’t be reached” error in CyberPanel may help you get back online.

Method 2: Use Command-Line Logging for Deeper Insight

The system journal can help us determine what’s going wrong if the built-in logs don’t provide enough information.

1. First, use this command to capture real-time logs related to the LSCPD web server:

   journalctl -f | grep lscpd

   Once it’s running, return to CyberPanel and reproduce the issue. Then, check the terminal output to see what went wrong.
2. CyberPanel uses Postfix and Dovecot for email handling. To find out why emails aren’t being sent or received:
   • For outgoing email (SMTP/Postfix issues):

     journalctl -f | grep postfix
   • For incoming email and webmail (Dovecot/Rainloop issues):

     journalctl -f | grep dovecot

   After running these commands, try sending or receiving an email. The output will help isolate the root cause of the failure.
3. If CyberPanel throws a generic 500 error, enable Django’s debug mode to see more information. We can open the settings file with this command:

   nano /usr/local/CyberCP/CyberCP/settings.py

   Change “DEBUG = False” to “DEBUG = True”.

   Then, restart the LSCPD service:

   systemctl restart lscpd

   When the error occurs again, we will see a more detailed traceback, which will help us find the exact source of the issue.

[Need assistance with a different issue? Our team is available 24/7.]

Conclusion

We can easily troubleshoot CyberPanel issues by combining built-in logs, command-line tools, and optional email alerts.

In brief, our Support Experts demonstrated how to debug CyberPanel issues.