Aruba.it Hosting – Special requirements for BPS Pro installation and setup

Home Forums BulletProof Security Pro Aruba.it Hosting – Special requirements for BPS Pro installation and setup

This topic contains 0 replies, has 1 voice, and was last updated by  AITpro Admin 1 year, 6 months ago.

Viewing 1 post (of 1 total)
  • Author
    Posts
  • #31841

    AITpro Admin
    Keymaster

    Aruba.it Hosting: https://www.aruba.it/en/home.aspx requires these additional BPS Pro installation and setup steps:

    After activating BPS Pro on a website hosted on Aruba.it hosting these steps need to be done first before running the Pre-Installation Wizard.
    1. Go to BPS Pro > B-Core > Custom Code > Root htaccess File Custom Code accordion tab.
    2. Copy this code below to this BPS Custom Code text box: CUSTOM CODE DO NOT SHOW DIRECTORY LISTING/DIRECTORY INDEX.
    3. Click the Save Root Custom Code button.
    4. You can then run the Pre-Installation Wizard and Setup Wizard.

    # DO NOT SHOW DIRECTORY LISTING
    # Disallow mod_autoindex from displaying a directory listing
    # If a 500 Internal Server Error occurs when activating Root BulletProof Mode
    # copy the entire DO NOT SHOW DIRECTORY LISTING and DIRECTORY INDEX sections of code
    # and paste it into BPS Custom Code and comment out Options -Indexes
    # by adding a # sign in front of it.
    # Example: #Options -Indexes
    #Options -Indexes
    
    # DIRECTORY INDEX FORCE INDEX.PHP
    # Use index.php as default directory index file. index.html will be ignored.
    # If a 500 Internal Server Error occurs when activating Root BulletProof Mode
    # copy the entire DO NOT SHOW DIRECTORY LISTING and DIRECTORY INDEX sections of code
    # and paste it into BPS Custom Code and comment out DirectoryIndex
    # by adding a # sign in front of it.
    # Example: #DirectoryIndex index.php index.html /index.php
    #DirectoryIndex index.php index.html /index.php

    Aruba.it hosting uses 755 file permissions for these files:  index.php, wp-blog-header.php and wp-config.php and does not allow locking these files with F-Lock.  Also F-Lock uses standard 644 file permissions to unlock files, but Aruba.it file permissions MUST be 755 file permissions. 

    When you run the Setup Wizard these files will be locked in F-Lock:  index.php, wp-blog-header.php and wp-config.php.  Locking these files will cause a 500 error when trying to view any frontend website pages or posts or menu links.

    Manual Solution Steps:
    1. After running the Wizards. You will need to go to F-Lock and choose: “Checking and Alerts Off” settings for all files except for your root htaccess file.
    2. You will also need to use FTP or your web host control panel file manager and manually change the file permissions for these files: index.php, wp-blog-header.php and wp-config.php back to 755 file permissions.

Viewing 1 post (of 1 total)

You must be logged in to reply to this topic.