Warning: Failed to open stream

  • Resolved rsp7

    (@rsp7)


    11 years, 1 month ago

    Have run into below mentioned warning after started having trouble when a user wants to compose a new message and ends up with the white screen of death. Admin has no problems with compiling new message.

    Tried ** Memory Limit */define(‘WP_MEMORY_LIMIT’, ‘64M’); which didn’t help. Disabling plugins pointed to either bps or akismet – disabling one of these or both allowed the user to compile a new message

    Then installed Debug Bar and turned on debugging gives me this:

    WARNING: wp-content/plugins/bulletproof-security/includes/functions.php:1510 – file_get_contents(/../htdocs/www/wp-content/.htaccess): failed to open stream: No such file or directory
    require_once(‘wp-admin/admin-header.php’), do_action(‘admin_notices’), call_user_func_array, bps_hud_check_sucuri, file_get_contents

    Not sure what else to try so any suggestions are welcome – thanks in advance

    https://wordpress.org/plugins/bulletproof-security/

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author AITpro

    (@aitpro)

    11 years, 1 month ago

    You can disregard the Debug Bar error. Not sure why Debug Bar would generate an error there. That code goes with a Dismiss Notice that checks for a known issue with a sucuri wp-content .htaccess file and then generates a help message with instructions. Anyway not relevant to whatever issue/problem is occurring.

    Check your BPS Security Log and post a Security Log entry that is relevant to what is being blocked. If you do not see a Security Log entry that is related to the issue/problem then most likely the issue/problem is not related to or being caused by BPS and you would want to do the standard WordPress troubleshooting steps: ie either deactivate plugins one by one and test or deactivate all of your plugins and test.

    You should have a PHP Configuration maximum memory limit of at least 128M. Anything lower than that and you will most likely run into out of memory issues randomly/intermittently. You can check your max memory limit on the BPS System Info page. If it is lower than 128M contact your host and have them increase the memory limit to 128M.

    Plugin Author AITpro

    (@aitpro)

    11 years, 1 month ago

    Oops forgot to post the standard BPS troubleshooting steps. 😉

    Source: http://forum.ait-pro.com/forums/topic/read-me-first-free/#bps-free-general-troubleshooting

    1. Optional (not necessary): Make a backup of your .htaccess on the htaccess Core >>> Backup & Restore tab page.
    2. On the Security Modes page, select the Deactivate Root Folder BulletProof Mode (Default Mode) Radio button and click the Activate|Deactivate button.
    See Custom Code Note
    3. On the Security Modes page, select the Deactivate wp-admin Folder BulletProof Mode Radio button and click the Activate|Deactivate button.
    See Custom Code Note
    4. If an issue/problem is related to Login Security turn Off Login Security on the Login Security & Monitoring page.

    Custom Code Note: If you have isolated a problem to the root or wp-admin .htaccess file and you have added additional custom .htaccess code or additional .htaccess code from another plugin to BPS Custom Code then cut (not Copy) all of your additional custom .htaccess code out of all BPS Custom Code text boxes and save that custom .htaccess code to a Notepad or Notepad++ text file, Click the Save Root Custom Code button (or the wp-admin Custom Code button), click the AutoMagic buttons on the Security Modes page and activate BulletProof Modes. You can then further isolate which custom .htaccess code is the problem by adding only 1 block of additional custom code back to a BPS Custom Code text box at a time.

    Thread Starter rsp7

    (@rsp7)

    11 years, 1 month ago

    Ok thanks for your quick reply!

    BPS System Info page says: PHP Actual Configuration Memory Limit: 256M
    and Peak Memory Usage: 62.88MB so i assume that’s ok

    Logging was turned off so have enabled that. Will follow and go through the other standard bps troubleshooting steps you added.

    Thread Starter rsp7

    (@rsp7)

    11 years, 1 month ago

    Have gone through the above mentioned steps and links but haven’t found any custom code etc that may have caused the problems.

    Eevn the opposite: now both BPS and akismet can be enabled (together) and the user can click on and compile a new message without landing in the ‘white screen of death’. Any idea why this didn’t work yesterday but no problem today?

    The main suspect now is yoast seo: if that plugin is enabled a normal user (editor) can not even get into the wp-admin page. The admin has no problems with this plugin

    Thread Starter rsp7

    (@rsp7)

    11 years, 1 month ago

    correction: Admin also gets ‘white screen of death’ at wp-admin/edit.php with yoast seo enabled

    Plugin Author AITpro

    (@aitpro)

    11 years, 1 month ago

    Eevn the opposite: now both BPS and akismet can be enabled (together) and the user can click on and compile a new message without landing in the ‘white screen of death’. Any idea why this didn’t work yesterday but no problem today?

    That would eliminate the BPS plugin then. BPS is all or nothing, meaning that things will either work consistently or not work consistently – there is no intermittent inbetween. htaccess files are a server configuration file that instructs the server to do something consistently/every time. Typically intermittent problems are things like server problems (connectivity, latency), cache, external services (CDN, Cloudflare).

    Check your php error log and server log for clues to what is causing the problem. I would also check with the host just to see if there are any known server issues going on right now.

    Thread Starter rsp7

    (@rsp7)

    11 years, 1 month ago

    Ok thanks for your time and the tips!

Viewing 7 replies - 1 through 7 (of 7 total)

The topic ‘Warning: Failed to open stream’ is closed to new replies.