Skip to main content

Does the Sept. 2 Apache Status article apply to CPANEL-54008 / CSF whm-server-status?

Comments

12 comments

  • User Avatar
    cPRex Jurassic Moderator

    Hey there!  I've reached out to the CSF team about this for some clarification and I'll let you know once I have more details.

    1
  • User Avatar
    Metro2

    Thank you. The issues seem very closely related.

    0
  • User Avatar
    cPRex Jurassic Moderator

    Sorry about the delay on this - we had some (all good) personnel changes on the CSF team so my response was a bit delayed.  I'll answer these in order, and end with some good news.

    1. Yes, the September 2 article is describing the same change behind CPANEL-54008: v136 obfuscated whm-server-status, so any tool still requesting the old static URL (LFD included) gets a 404.
    2. Not currently.  CSF/LFD is still shipped pointing at the legacy whm-server-status URL by default. Updating that is the pending fix.
    3. Looking into the 16.31-1 release, I can confirm that was a security-only patch (CVE-2026-67402, the MESSENGER issue) and did not include the CPANEL-54008 fix. So no, it hasn't shipped yet.
    4. The NGINX reverse proxy doesn't change the recommended workaround, since PT_APACHESTATUS talks to Apache directly rather than through the proxy. You'd apply the same /server-status Location block to your port-8080 Apache template and set:
      PT_APACHESTATUS = "http://127.0.0.1:8080/server-status"
      then restart both Apache and CSF/LFD.

    Separately, the September 15 article about ea-apache24-config-runtime is an unrelated issue (an outdated package causing the WHM Apache Status page itself to fail) not the same bug, so no action needed there unless you're seeing that specific symptom too.

    THE GOOD NEWS - the fix should be shipping in tomorrow's cPanel build if everything goes well!

    0
  • User Avatar
    Metro2

    Thank you so much for the update!

    0
  • User Avatar
    cPRex Jurassic Moderator

    You're very welcome!!

    0
  • User Avatar
    Metro2

    Hi cPRex

    Just following up on this.

    My servers are currently running cPanel 138.0.11 / cpanel-csf 16.32-1.1.1.cpanel

    However, LFD is still generating the same error every minute:

    STATS: Unable to retrieve Apache Server Status [...] - Unable to download: Not Found

    I also noticed that the CSF 16.32 changelog only mentions hardening the iptables command, and I don't see CPANEL-54008 mentioned in the cPanel 138 changelog either.

    Since you mentioned on September 23 that the fix was expected in the next cPanel build, can you please check with the CSF team whether the CPANEL-54008 fix actually shipped, or whether it was delayed?

    If it has still not shipped, is the previously confirmed /server-status workaround still the recommended solution for cPanel NGINX servers?

    Thanks!

    0
  • User Avatar
    cPRex Jurassic Moderator

    Metro2 - this was indeed released as part of the September 3 Targeted Security Release, so it may not show up as a normal entry in the changelog. However, we are expecting this to be fixed at this time.

    Can you create a ticket so we can take a look?

    0
  • User Avatar
    Metro2

    cPRex thank you for the reply. Issue definitely still exists for me. I'm unable to create a ticket because my cPanel licenses are through the data center that I lease my dedicated servers from.

    0
  • User Avatar
    cPRex Jurassic Moderator

    It's just odd as we don't have other reports of this not working after the update, and my own personal machine is also working as expected.

    Can you create a ticket with the data center?

    0
  • User Avatar
    Metro2

    Oct  6 11:00:42 (hostname) lfd[3333526]: STATS: Unable to retrieve Apache Server Status [http://127.0.0.1/REDACTED?auto] - Unable to download: Not Found
    Oct  6 11:01:42 (hostname) lfd[3334262]: STATS: Unable to retrieve Apache Server Status [http://127.0.0.1/REDACTED?auto] - Unable to download: Not Found
    Oct  6 11:02:42 (hostname) lfd[3335216]: STATS: Unable to retrieve Apache Server Status [http://127.0.0.1/REDACTED?auto] - Unable to download: Not Found
    Oct  6 11:03:42 (hostname) lfd[3336070]: STATS: Unable to retrieve Apache Server Status [http://127.0.0.1/REDACTED?auto] - Unable to download: Not Found
    Oct  6 11:04:42 (hostname) lfd[3337193]: STATS: Unable to retrieve Apache Server Status [http://127.0.0.1/REDACTED?auto] - Unable to download: Not Found

    0
  • User Avatar
    Metro2

    In response to your question - I can try. That has not been an easy route in the past. Since this is already being tracked as CPANEL-54008, is there a specific case/reference number or wording I should give them so they can open the appropriate cPanel ticket on my behalf?

    0
  • User Avatar
    cPRex Jurassic Moderator

    You could do that, or even just direct them to this thread.

    0

Please sign in to leave a comment.