Scan can’t continue

My basedir is – https://prntscr.com/f1kefz

Hi @slavaman,

In order to make sure which directory PHP will actually see as /tmp, could you please check with your hosting provider which directory PHP’s open_basedir is set to.

Wordfence uses sys_get_temp_dir() to get the location of a temporary directory that PHP should be able to write to, which here is giving us /tmp, but the site’s open_basedir in your case prevents us from using that directory.

Also, could you check with your hosting provider if they can set the site to use a newer version of PHP (version 5.6 or newer); php.ini has a sys_temp_dir option that would let them set a different temp directory, if needed.

• This reply was modified 7 years, 11 months ago by wfyann. Reason: Spelling

ISP’s answear was such: The open_basedir restriction does not allow access to files that do not reside outside your home directory. CloudLinux rules also apply this limitation.

PHP version changed – https://prntscr.com/f25eud

Scan stopped after lines:
[Apr 29 10:56:41:1493452601.305342:2:info] Analyzed 800 files containing 31.39 MB of data so far
Apr 29 10:56:47:1493452607.420245:1:error] tempnam(): open_basedir restriction in effect. File(/tmp) is not within the allowed path(s): (/var/www/XXXXX/data:.) (2) File: /var/www/XXXXX/data/www/XXXXX/wp-content/plugins/wordfence/lib/wfConfig.php Line: 414

Hi @slavaman,

Sorry about the delayed response.

I suggest you ask your hosting provider to either modify the PHP sys_temp_dir parameter so it is compatible with the open_basedir restriction or to add /tmp to PHP’s open_basedir directive.

Thanks) But I can’t understand why other two websites may scan correctly without any limitation of PHP…

Hi @slavaman,

Could it be that the 2 other Wordfence instances are running on environments which have different PHP configurations?

Maybe there aren’t any open_basedir restrictions there? Or maybe the open_basedir directive has a different value?

If you check the Wordfence System Info page for each of the 3 Wordfence installations:

• Go to the Wordfence Tools page
• Click the Diagnostics tab
• In the Other Tests section, click the link that reads “Click to view your system’s configuration in a new window”

…and compare the values associated with the following parameters:

• Loaded Configuration File
• PHP Version
• open_basedir

Do you see any differences?

there aren’t any differences

Hi @slavaman,

For each of your 3 Wordfence instances (the 2 working fine and the problematic one), could you please:

• Go to the Wordfence Tools page
• Click the Diagnostics tab
• Scroll down to the Send Report by Email section
• Send the report to yann[at]wordfence[dot]com

Dear wfyann,

thanks for help. Wordfence is working properly now. And I don’t know why because nothing was changed))

Hi @slavaman,

Thanks for letting us know. I’m glad the issue is now fixed!

Maybe your hosting provider made some configuration changes. It would be interesting (and enlightening) to check with them.