Support » Plugin: Wordfence Security - Firewall & Malware Scan » open_basedir restriction in effect

  • Resolved ashokmhrj

    (@ashokmhrj)


    Hello There,

    Recently, one of my clients’ site was attacked my malicious scripts. And obliviously, I installed WordFence plugin. During the scan period, I encounter with this issues. It says:

    tempnam() [function.tempnam]: open_basedir restriction in effect. File(/tmp) is not within the allowed path(s): (/home:/usr/local/apache/php_tmp:/usr/bin/convert) (2) File: /home/user/…/public_html/…./wp-content/plugins/wordfence/lib/wfConfig.php Line: 692

    .
    .
    .

    unlink() [function.unlink]: open_basedir restriction in effect. File() is not within the allowed path(s): (/home:/usr/local/apache/php_tmp:/usr/bin/convert) (2) File: /home/user/…/public_html/…/wp-content/plugins/wordfence/lib/wfConfig.php Line: 710

    Scan can’t continue – stored data not found after a fork. Got type: boolean

    I did follow some links: https://wordpress.org/support/topic/fix-for-open_basedir-not-in-allowed-paths-message?replies=5 but I still got same issue.

    I did talk to the host support and they said that my account do not have access to path.
    Now, I am here to get help.
    Thanks.

    https://wordpress.org/plugins/wordfence/

Viewing 4 replies - 1 through 4 (of 4 total)
  • Hello ashokmhrj,
    Can you look on the Wordfence “Diagnostics” page and let me know which PHP version you have? Thanks in advance.

    Here it says:

    PHP version >= PHP 5.2.4 (Minimum version required by WordPress) 5.2.17

    Checking for OpenSSL support OK

    Checking for cURL support 7.19.7

    Hello ashokmhrj,
    as you can see your PHP version is too old to even run WordPress. Your PHP version is 5.2.17 but WordPress recommends 5.6 and requires at least 5.2.4.

    If you can update PHP via your web hosts administration panel, please do so. Otherwise you need to contact your web host and ask them to update to a newer version of PHP.

    Hello,

    try to define :
    sys_temp_dir = ""
    in your php.ini file.

    This solved the problem for me.

    Have a nice day

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘open_basedir restriction in effect’ is closed to new replies.