3

Managing a cPanel server often involves dealing with issues that appear suddenly even when websites are still running normally. Two errors that can confuse server administrators are “Failed to receive status information from Apache” when checking Apache status and the AutoSSL message “domain.tld is unmanaged.”

Although these messages are different, both can usually be investigated through cPanel & WHM, service configuration, and command-line checks. Understanding what each error means makes troubleshooting much faster and helps prevent unnecessary changes to a working server.

In this guide, we will look at the possible causes of both problems and discuss practical ways to diagnose them.

1. Apache Status: “Failed to Receive Status Information from Apache”

Apache is responsible for serving HTTP and HTTPS requests on many cPanel servers. When WHM cannot retrieve Apache’s current status, it may display an error similar to:

“Failed to receive status information from Apache.”

This does not necessarily mean that Apache is completely down. In some situations, Apache may still be serving websites while cPanel is unable to obtain the expected service-status information.

Check Whether Apache Is Running

The first step is to determine whether the Apache service itself is active.

From the command line, check the service status using the appropriate system service command. You can also use cPanel’s service-management tools to determine whether Apache is running.

If Apache is stopped, inspect the service logs and attempt to identify why it failed. Common causes include configuration errors, unavailable ports, missing modules, or problems introduced by a recent configuration change.

If Apache is running, the problem may instead involve communication between cPanel’s monitoring system and the Apache service.

Test the Apache Configuration

A damaged or invalid Apache configuration is another common area to investigate.

Before restarting Apache after making changes, run a configuration syntax test. On systems using Apache’s standard configuration tools, this can help identify syntax errors and invalid directives.

Pay particular attention to recent changes involving:

• Virtual hosts
• SSL configuration
• Apache modules
• Custom directives
• Include files
• PHP handlers
• Third-party applications

A single invalid directive can prevent Apache from reloading correctly.

Review Apache Logs

Apache logs can provide useful information when the service status shown by WHM does not match what you expect.

Look for errors around the time the problem appeared. Messages involving configuration parsing, modules, permissions, sockets, or SSL certificates can point toward the underlying issue.

If Apache is running but WHM continues to report a status problem, compare the command-line service status with the information displayed in WHM. This distinction helps determine whether you are dealing with an actual Apache failure or a monitoring/status-reporting problem.

Restart Only After Identifying the Cause

Restarting Apache may temporarily clear a service-status issue, but repeatedly restarting it without finding the underlying cause is not a reliable solution.

If you have identified and corrected a configuration problem, restart or reload Apache and then verify that websites, HTTPS connections, and PHP applications continue to work.

If the error persists, review cPanel’s service-monitoring configuration and relevant logs before making further changes.

2. AutoSSL Error: “domain.tld is unmanaged”

Another common cPanel issue occurs when AutoSSL attempts to issue or renew a certificate but reports:

“domain.tld is unmanaged.”

This message can be confusing because the domain may exist in cPanel and the website may be working normally.

The important point is that a domain being present on the server does not always mean that cPanel considers it eligible for AutoSSL management.

What Does “Unmanaged” Mean?

AutoSSL is responsible for automatically obtaining and renewing SSL certificates for eligible domains. When a domain is marked as unmanaged, AutoSSL is essentially indicating that it should not currently manage the certificate for that domain.

This can happen because of domain configuration, SSL-management settings, certificate ownership, or changes made outside the normal cPanel workflow.

Check the Domain in cPanel

Start by opening the affected cPanel account and checking the domain configuration.

Confirm that the domain is correctly associated with the expected cPanel account and that it is not configured in a way that prevents AutoSSL from managing its certificate.

Also check whether the domain has been excluded from AutoSSL.

In WHM, administrators can review the AutoSSL configuration and examine the relevant account and domain settings.

Verify AutoSSL Configuration

WHM provides settings that control how AutoSSL operates on the server. Confirm that an AutoSSL provider is configured and that the affected account is permitted to use AutoSSL.

If AutoSSL has been disabled for the account or domain, the certificate will not be automatically managed.

After correcting the configuration, run AutoSSL again for the affected account and review the resulting log.

Check DNS and Domain Resolution

Certificate issuance also depends on domain validation.

Make sure the domain resolves to the server’s correct public IP address. Check both the main domain and relevant subdomains that you expect AutoSSL to cover.

Incorrect DNS records, stale DNS information, proxy services, or firewall restrictions can prevent validation from completing successfully.

For domains using external DNS providers, verify that the necessary records point to the correct hosting server.

Review Existing Certificates

An existing SSL certificate can also complicate troubleshooting.

Check the domain’s current SSL configuration and determine whether the certificate was manually installed or issued by another certificate authority.

If a certificate was installed manually, understand how that certificate is being managed before changing anything. Removing or replacing certificates without checking the existing configuration can cause unexpected HTTPS problems.

Run AutoSSL Again

After correcting the domain, account, or DNS configuration, run AutoSSL again for the affected account.

Review the AutoSSL log instead of relying only on the final success or failure message. The log normally provides more information about certificate validation, domain eligibility, DNS, and installation.

Once AutoSSL completes successfully, open the domain over HTTPS and verify that the correct certificate is being served.

Preventing These Problems

Regular server maintenance can reduce the likelihood of recurring Apache and AutoSSL issues.

Keep cPanel & WHM updated, monitor Apache and system logs, avoid unnecessary manual modifications to generated configuration files, and document custom server changes.

For AutoSSL, periodically verify DNS records and make sure domains remain correctly associated with their cPanel accounts.

Conclusion

The messages “Failed to receive status information from Apache” and “domain.tld is unmanaged” can look alarming, but they do not automatically indicate that your entire cPanel server is broken.

For Apache, begin by confirming the service state, checking configuration syntax, and reviewing logs. For AutoSSL, verify domain ownership within cPanel, AutoSSL eligibility, DNS resolution, and existing certificate configuration.

The best troubleshooting approach is to identify the exact layer where the problem occurs before making changes. By working methodically through service status, configuration, logs, and domain settings, administrators can resolve these issues while minimizing downtime and avoiding unnecessary configuration changes.