Prevent usage of `suPHP_ConfigPath` in .htaccess

  • Resolved tomhale

    (@tomhale)


    7 years, 2 months ago

    By default, BPS writes:

    # CUSTOM CODE TOP PHP/PHP.INI HANDLER/CACHE CODE
# PHP/php.ini handler htaccess code
   suPHP_ConfigPath '/home/globa298/public_html/travel/prod'

    The problem is that cpanel logs an error:

    [Thu Jan 25 16:08:49.691029 2018] [core:alert] [pid 35615] [client 141.8.143.196:34550] /home/tomh9670/public_html/travel/prod/.htaccess: Invalid command 'suPHP_ConfigPath', perhaps misspelled or defined by a module not included in the server configuration
[Thu Jan 25 16:08:37.015887 2018] [core:alert] [pid 36691] [client 84.201.133.61:59826] /home/tomh9670/public_html/travel/prod/.htaccess: Invalid command 'suPHP_ConfigPath', perhaps misspelled or defined by a module not included in the server configuration

    How can I prevent the suPHP_ConfigPath from being written (or re-written even if I manually comment it out in .htaccess?

    • This topic was modified 7 years, 2 months ago by tomhale.
    • This topic was modified 7 years, 2 months ago by tomhale.
Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author AITpro

    (@aitpro)

    The BPS Setup Wizard checks your existing Root htaccess file for any pre-existing php/php.ini handler htaccess code and saves that pre-existing php/php.ini handler htaccess code to BPS Root Custom Code and also adds that pre-existing php/php.ini handler htaccess code to your new Root htaccess file that is created by the BPS Setup Wizard.

    If you do not want to keep/use that pre-existing php/php.ini handler htaccess code then do these steps:

    1. Go to BPS Custom Code > click the Root htaccess File Custom Code accordion tab.
    2. Delete the suPHP_ConfigPath htaccess code in this BPS Custom Code text box: 1. CUSTOM CODE TOP PHP/PHP.INI HANDLER/CACHE CODE
    3. Click the Save Root Custom Code button.
    4. Go to the Security Modes tab page and click the Root Folder BulletProof Mode Activate button.

    Plugin Author AITpro

    (@aitpro)

    Is the issue/problem still occurring or is it resolved?

    Plugin Author AITpro

    (@aitpro)

    Assuming all questions have been answered – the thread has been resolved. If the issue/problem is not resolved or you have additional questions about this specific thread topic then you can post them at any time. We still receive email notifications when threads have been resolved.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Prevent usage of `suPHP_ConfigPath` in .htaccess’ is closed to new replies.

Tags