Skip to main content
We are aware of an issue with a recent Apache update that causes proxied sites to return a "421 Misdirected Request" error. Please see the following article for more information and updates:
Websites show 421 Misdirected Request error while using EA Nginx

Cant get lsphp command whitelisting in /etc/csf/csf.pignore to work

Comments

6 comments

  • fuzzylogic
    I don't do this but would try... pcmd:lsphp:/home/.*/public_html/wp-cron\.php
    and pcmd:lsphp:/home/.*/public_html/.*/wp-cron\.php
    Also note that Chirpy warns... [QUOTE] # It is strongly recommended that you use command line ignores very carefully # as any process can change what is reported to the OS.
    0
  • cPanelLauren
    This is also discussed on their forums here: Process Tracking and csf.pignore - ConfigServer Community Forum and it's also discussed in Section 8 of their readme here: Process Tracking and csf.pignore - ConfigServer Community Forum
    0
  • MrIver
    Thanks guys - looks like the code from fuzzylogic works :)
    0
  • LitespeedLucas
    Ideally you'd want to add the pignore for the lsphp binaries instead of specific scripts: pexe:/opt/cpanel/ea-php.*/root/usr/bin/lsphp.*
    0
  • MrIver
    Ideally you'd want to add the pignore for the lsphp binaries instead of specific scripts: pexe:/opt/cpanel/ea-php.*/root/usr/bin/lsphp.*

    But would this not whitelist all processes? Then we would not get any alerts for processes that might acutually be suspicious?
    0
  • cPanelLauren
    That would whitelist all lsphp processes it would not whitelist all processes
    0

Please sign in to leave a comment.