How to Troubleshoot Error Message For: "Fatal error in LiteSpeed configuration."

In this article, we are going to discuss what steps to take if LiteSpeed Web Server plugin is reporting the following error inside of WHM.

Fatal error in LiteSpeed configuration.

Description 

When the error is reported above, it usually indicates that there is a value set in your LiteSpeed Configuration that caused an error to be reported when the service last started. By default, LiteSpeed Web Server should report errors to the Apache error log. Please note, access to the LiteSpeed "WebAdmin Console" will also be helpful in investigating this.

Troubleshooting Steps

When a Fatal error is reached, it should be reported to the Apache error_log, which is located at: /etc/apache2/logs/error_log 

As an example to help troubleshoot, here is a command you can use to help you determine where in the log the error took place:

# grep -i fatal /etc/apache2/logs/error_log
2020-01-01 12:22:32.000000 [FATAL] [1234] Fatal error in LiteSpeed configuration.

Once the error is found in the Apache error_log, you can view the whole log to determine more information about what led up to FATAL error.

2020-01-01 12:22:32.000000 [ERROR] [1234] [config:admin:listener] No listener is available for admin virtual host!
2020-01-01 12:22:32.000000 [FATAL] [1234] Fatal error in LiteSpeed configuration.

In the case of this error above I was able to go to LiteSpeed WebAdmin Console --> Configuration --> Listeners and determine a custom listener was assigned to an invalid port number.