• rafaelmagic

    (@rafaelmagic)


    Hi,

    Deleted all security plugins.

    I am running a VPS with CentOs.

    I tried all the INI’s, php.ini, php5.ini, .user.ini.

    When I hit Enable, I white screen.

    Waited 5 minutes on all runs.

    Still have a white screen.

    Nothing in Error Logs.

    Is their a CentOs VPS install workaround.

    https://wordpress.org/plugins/ninjafirewall/

Viewing 15 replies - 1 through 15 (of 42 total)
  • Plugin Author nintechnet

    (@nintechnet)

    Hi,

    Try to follow these steps and see if it helps.
    Regarding the INI file, you will probably need to use .user.ini.

    Thread Starter rafaelmagic

    (@rafaelmagic)

    Hi,

    Still getting White Screen.

    I set
    output_buffering = 4096
    session.save_handler files files
    session.save_path /tmp /tmp

    Wp Debug says:

    Warning: session_start(): Cannot send session cache limiter – headers already sent (output started at /home/mywebsite/public_html/wp-includes/functions.php:2908) in /home/mywebsite/public_html/wp-content/plugins/ninjafirewall/ninjafirewall.php on line 45

    Any suggestion?

    Plugin Author nintechnet

    (@nintechnet)

    Line 2908 of /wp-includes/functions.php shows that WordPress will display an error message because a plugin is using a deprecated function. Because of that, you get an error when NinjaFirewall is calling the PHP session_start() function.
    Can you try to disable each plugin one by one, until you can find which one is the problem ?

    Thread Starter rafaelmagic

    (@rafaelmagic)

    Hi,

    I installed a brand new install of WP and Ninja Firewall. I still white screen.

    Now my setup is this:

    Varnish (Cache)–Nginx (reverse proxy) –Apache

    Which might be why its white screening.

    Server also has ModSecurity with Commodo WAF Rules.

    Any advice. Thanks

    Thread Starter rafaelmagic

    (@rafaelmagic)

    DUH. I fixed it. Firewall was blocking me and doing its job.

    You might have to Whitelist your Internet IP.

    I personally used the user.ini

    Here is the Tutorial:

    http://nintechnet.com/nfwp/1.1.3/

    Brief Run Down:
    In the plugin directory look for the file:

    .htninja_example

    “This file must be named .htninja and must be located in the folder above your website document root : if your document root is /home/user/public_html/, the location of the file will be /home/user/.htninja “

    Look for the lines in that .htninja file:

    // Whitelist single IP 1.2.3.4:
    if ( $_SERVER[“REMOTE_ADDR”] == ‘YOUR IP ADDRESS’ ) {
    return ‘ALLOW’; // whitelist

    Replace YOUR IP ADDRESS with your Internet IP address.

    Multiple IP, find the corresponding line.

    Save and then enable the plugin.

    Then fix permission to read only or 444 on the .htninja file.

    CLOSE TICKET AS SOLVED.

    Plugin Author nintechnet

    (@nintechnet)

    Your problem is not solved. By adding your IP, the firewall will stop running immediately. That is why you don’t get any more errors.

    In most case, the white screen means there is a PHP error. Now you need to force PHP to display and/or log that error so we’ll know what is going on. See php.ini Error Settings

    Thread Starter rafaelmagic

    (@rafaelmagic)

    I finally got PHP ERRORS TO DISPLAY:

    In my user.ini
    I placed:
    error_reporting = E_ALL | E_STRICT
    display_errors = 1 (On didn’t work)
    session.save_path = tmp

    Created a tmp folder in root with permissions

    Errors Received:

    Warning: session_start(): open(tmp/sess_4d1d46f1875d88532a68adbca303148d, O_RDWR) failed: No such file or directory (2) in /home/directory/public_html/wp-content/plugins/ninjafirewall/ninjafirewall.php on line 45

    Warning: session_start(): Cannot send session cache limiter – headers already sent (output started at /home/directory/public_html/wp-content/plugins/ninjafirewall/ninjafirewall.php:45) in /home/youmag75/public_html/wp-content/plugins/ninjafirewall/ninjafirewall.php on line 45

    I just see line 45 Error:
    if (! session_id() ) { session_start(); }

    Tried to look for Php Coding Errors and found this discussion.
    http://stackoverflow.com/questions/6865957/php-logic-for-session-id-and-session-start

    Any advice?

    Plugin Author nintechnet

    (@nintechnet)

    session.save_path = tmp

    You need to add the full path to that directory otherwise you will keep getting that “No such file or directory” error.

    Thread Starter rafaelmagic

    (@rafaelmagic)

    Just did that. No more PHP errors.

    I could see the session.save_path working and files being created/

    WP-Debug has no errors.

    Still white screening.

    Thread Starter rafaelmagic

    (@rafaelmagic)

    I then checked your FAQ.

    http://ninjafirewall.com/wordpress/help.php#troubleshooting
    Blank page after installing NinjaFirewall :
    In some cases, right after installing it, you may get a blank page and/or the following error message :
    Warning: session_start() [function.session-start]: Cannot send session cache limiter – headers already sent (output started at …/…/wp-content/plugins/ninjafirewall/lib/firewall.php…
    The problem may come from your PHP session save handler (session.save_handler) configuration which is not set up to use files.

    HERE IS MY SESSIONS from phpinfo:
    session.auto_start Off Off
    session.cache_expire 180 180
    session.cache_limiter nocache nocache
    session.cookie_domain no value no value
    session.cookie_httponly Off Off
    session.cookie_lifetime 0 0
    session.cookie_path / /
    session.cookie_secure Off Off
    session.entropy_file /dev/urandom /dev/urandom
    session.entropy_length 32 32
    session.gc_divisor 100 100
    session.gc_maxlifetime 1440 1440
    session.gc_probability 1 1
    session.hash_bits_per_character 4 4
    session.hash_function 0 0
    session.name PHPSESSID PHPSESSID
    session.referer_check no value no value
    session.save_handler files files
    session.save_path /home/directory/public_html/tmp/ /home/directory/public_html/tmp/
    session.serialize_handler php php
    session.upload_progress.cleanup On On
    session.upload_progress.enabled On On
    session.upload_progress.freq 1% 1%
    session.upload_progress.min_freq 1 1
    session.upload_progress.name PHP_SESSION_UPLOAD_PROGRESS PHP_SESSION_UPLOAD_PROGRESS
    session.upload_progress.prefix upload_progress_ upload_progress_
    session.use_cookies On On
    session.use_only_cookies On On
    session.use_trans_sid 0 0

    Any further advice?

    Thread Starter rafaelmagic

    (@rafaelmagic)

    NinjaCheck (auto prepend disabled):
    N
    injaFirewall (WP edition) troublershooter v1.01

    ========================== %< ============================

    HTTP server: Apache
    PHP version: 5.4.26
    PHP SAPI: CGI-FCGI
    Loaded INI file: /home/directory/public_html/.user.ini
    auto_prepend_file: none (
    user_ini.filename: .user.ini
    user_ini.cache_ttl: 300
    user INI: .user.ini found
    PHPRC: /home/directory/public_html/.user.ini
    DOCUMENT_ROOT: /home/directory/public_html
    wp-config.php: found

    Warning: Cannot modify header information – headers already sent by (output started at /home/directory/public_html/ninjacheck.php:25) in /home/directory/public_html/wp-content/plugins/mainwp-child/mainwp-child.php on line 10

    Warning: Cannot modify header information – headers already sent by (output started at /home/directory/public_html/ninjacheck.php:25) in /home/directory/public_html/wp-content/plugins/wp-super-cache/wp-cache-phase2.php on line 91

    Warning: session_start(): Cannot send session cache limiter – headers already sent (output started at /home/directory/public_html/ninjacheck.php:25) in /home/directory/public_html/wp-content/plugins/ninjafirewall/ninjafirewall.php on line 45

    ABSPATH: /home/directory/public_html/
    WP version: 3.8.2
    WP_CONTENT_DIR: /home/directory/public_html/wp-content

    ========================== %< ============================

    Plugin Author nintechnet

    (@nintechnet)

    Can you try to edit ninjafirewall.php and to comment out lines 43, 44 and 46.
    Add ‘//’ at the beginning of the 3 lines so that it looks like this:

    // add_action('init', 'nfw_sessionstart', 1);
    // function nfw_sessionstart() {
            if (! session_id() ) { session_start(); }
    //}

    Just keep line 45.

    Thread Starter rafaelmagic

    (@rafaelmagic)

    OK.

    So I installed WP to brand new domain and the Only plugin is Ninja Firewall.

    I commented out lines 43, 44 and 46.

    In NinjaCheck.php I get the following 2 messages referencing Line 45:

    Warning: session_start(): Cannot send session cookie – headers already sent by (output started at /home/directory/public_html/ninjacheck.php:25) in /home/directory/public_html/wp-content/plugins/ninjafirewall/ninjafirewall.php on line 45

    Warning: session_start(): Cannot send session cache limiter – headers already sent (output started at /home/directory/public_html/ninjacheck.php:25) in /home/directory/public_html/wp-content/plugins/ninjafirewall/ninjafirewall.php on line 45

    I also sent a request for install help thru your site. I may just have a funky system that needs your help.

    Plugin Author nintechnet

    (@nintechnet)

    Note that if you sent us a ticket for the installation, you will not get an answer before April 18th because of holidays here in Thailand.

    Thread Starter rafaelmagic

    (@rafaelmagic)

    I understand about the Holidays. If your not on Holiday do you have any suggestions for:

    Warning: session_start(): Cannot send session cookie – headers already sent by (output started at /home/directory/public_html/ninjacheck.php:25) in /home/directory/public_html/wp-content/plugins/ninjafirewall/ninjafirewall.php on line 45

    Warning: session_start(): Cannot send session cache limiter – headers already sent (output started at /home/directory/public_html/ninjacheck.php:25) in /home/directory/public_html/wp-content/plugins/ninjafirewall/ninjafirewall.php on line 45

Viewing 15 replies - 1 through 15 (of 42 total)
  • The topic ‘VPS- Cent Os Install Help..’ is closed to new replies.