Random General Questions

Home Forums BulletProof Security Pro Random General Questions

Viewing 15 posts - 271 through 285 (of 350 total)
  • Author
    Posts
  • #29276
    AbZu2
    Participant

    This is the content of my wp-admin/.htaccess file:
    [wp-admin htaccess file/code checked – good – deleted]

    This is the contents of my public-html/.htaccess file:

    #   BULLETPROOF PRO 11.7.1 SECURE .HTACCESS          
    
    # CUSTOM CODE TOP PHP/PHP.INI HANDLER/CACHE CODE
    # PHP/php.ini handler htaccess code
    AddHandler application/x-httpd-phpbeta .php
    
    [the rest of the root htaccess file code was checked, is good - deleted]
    
    #29280
    AbZu2
    Participant

    Found the following in public-html/wp-config.php What should I delete ?

    // ** MySQL settings - You can get this info from your web host ** //
    /** The name of the database for WordPress */
    //define('WP_CACHE', true); //Added by WP-Cache Manager
    define( 'WPCACHEHOME', '/xxxx/xxxx/public_html/wp-content/plugins/wp-super-cache/' ); //Added by WP-Cache Manager
    
    #29281
    AITpro Admin
    Keymaster

    I believe the problem code is your PHP handler code:  AddHandler application/x-httpd-phpbeta .php.  Delete your root htaccess file if you have not already deleted it yet.  Go to Custom Code > Root htaccess File Custom Code accordion tab > CUSTOM CODE TOP PHP/PHP.INI HANDLER/CACHE CODE > comment out your PHP handler code with a # sign:  #AddHandler application/x-httpd-phpbeta .php and do the Custom Code steps below.  Let me know if your site crashes again or not.  I do not recognize your PHP handler code and have never seen “beta” added to that code before.  Make sure you are using valid PHP handler code that is provided your specific web host.

    Root htaccess File Custom Code Setup Steps
    1. Enter your custom code in the appropriate Root Custom Code text box.
    2. Click the Save Root Custom Code button to save your Root custom code.
    3. Go to the BPS Security Modes page and click the Root Folder BulletProof Mode Activate button.

    #29283
    AbZu2
    Participant

    Which .htaccess file should I delete ¿ public-html/ or wp-admin/ ?

    #29284
    AITpro Admin
    Keymaster

    Oops you posted your database connection information from your wp-config.php file, which I have deleted.  You need to delete this WP Super Cache code out of your wp-config.php file if you have removed/deleted the WP Super Cache plugin already.  See the steps I posted in my previous reply.

    //define('WP_CACHE', true);
    //Added by WP-Cache Manager
    define( 'WPCACHEHOME', '/xxxxx/xxxxx/public_html/wp-content/plugins/wp-super-cache/' ); //Added by WP-Cache Manager
    #29285
    AITpro Admin
    Keymaster

    You would delete your root htaccess file, which is the htaccess file that is installed in your root WordPress installation folder or /public_html/ if that is where your root WordPress installation is installed.

    #29286
    AbZu2
    Participant

    Can’t access my admin dashboard, thus can’t access BPS plugin to follow your suggestions. Want to have confirmation which .htaccess file I should delete.

    #29289
    AITpro Admin
    Keymaster

    Yes, see my reply above.  We were probably posting at the same time.

    #29290
    AbZu2
    Participant

    My mind is starting to spin Deleted public-html/.htaccess as suggested. Managed to get a bare bones dashboard to load but when I clicked on BPS custom code I got the same 500 Internal Server Error

    Blocked can’t get to:

    Go to Custom Code > Root htaccess File Custom Code accordion tab > CUSTOM CODE TOP PHP/PHP.INI HANDLER/CACHE CODE > comment out your PHP handler code with a # sign:  #AddHandler application/x-httpd-phpbeta .php and do the Custom Code steps below.

     

    #29291
    AITpro Admin
    Keymaster

    Oops yeah left out a critical step:  Use FTP and delete this file first:  /wp-content/bps-backup/autorestore/root-files/auto_.htaccess and then delete your root htaccess file again.  AutoRestore restored the bad root htaccess file.  😉

    I checked BlueHost PHP handlers and I see your PHP handler code is valid, but BlueHost has a warning about using that PHP handler code so for now comment it out and see if that is the problem after you get back into your site.

    https://my.bluehost.com/cgi/help/htaccess-php-handlers
    PHP 5.6 (Still In Beta Phase, use at your own risk.)

    # Use PHP5.6 as default
    AddHandler application/x-httpd-phpbeta .php

    PHP 5.6 Single php.ini (Still In Beta Phase, use at your own risk.)

    # Use PHP5.6 Single php.ini as default
    AddHandler application/x-httpd-phpbetas .php
    #29293
    AbZu2
    Participant

    OK deleted the recommended lines from wp-config.php but I still can’t get anywhere. Made a backup of .htaccess before deleting it just in case.

    #29294
    AITpro Admin
    Keymaster

    Most likely your PHP handler code is good and what caused your website to crash was the leftover WP Super Cache code in your wp-config.php file and missing WPSC htaccess code in your root htaccess file.  So once you get back into your site then turn off AutoRestore and do the steps to remove/delete the WPSC code out of your wp-config.php file.

    #29298
    AbZu2
    Participant

    For some reason I needed the latest PHP and ended up with 5.6 which was in beta. Perhaps i should revert to the latest stable version. Sent you an email to info, please confirm reception and if the information is of any use. Trusting in you. Will try your latest suggestions before my face smashes my keyboard. Getting late. Start fading out after 2am.

    #29300
    AITpro Admin
    Keymaster

    I need FTP Login information to be able to fix this so send me FTP login info to your hosting account.  Yeah I think your PHP handler is fine.  I just had never seen “beta” used before in a PHP handler.

    #29302
    AbZu2
    Participant

    Good >> Use FTP and delete this file first:  /wp-content/bps-backup/autorestore/root-files/auto_.htaccess and then delete your root htaccess file again.  AutoRestore restored the bad root htaccess file.
    … worked. I am now back in my admin dashboard. Really want to get this solved. So what do you suggest now. TIA
    BTW haven’t delt with the PHP  issue at the moment. When I have sorted out the major issues I will revert to a stable non-beta version of PHP.

Viewing 15 posts - 271 through 285 (of 350 total)
  • You must be logged in to reply to this topic.