sjebelli

@wfasa

Yes I’m sure. please read highlighted data:
———————–
Warning: file_exists(): open_basedir restriction in effect. File(/home/HOST-A/domains/domain-a.com/public_html/wp-content/plugins/wordfence/vendor/composer/../geoip2/geoip2/src/Database/Reader.php) is not within the allowed path(s): (/home/HOST-B/:/tmp:/var/tmp:/usr/local/lib/php/:/usr/local/php56/lib/php/) in /home/HOST-B/domains/domain-b.com/public_html/wp-content/plugins/wordfence/vendor/composer/ClassLoader.php on line 384

Fatal error: Class ‘GeoIp2\Database\Reader’ not found in /home/HOST-B/domains/domain-b.com/public_html/wp-content/plugins/wordfence/models/common/wfGeoIP2.php on line 28
———————-

Even the same class:GeoIp2\Database\Reader has the problem. in other thread, several people had this error.

• This reply was modified 6 years, 2 months ago by sjebelli.

Hi @iragination

Could you please provide more information about how you fixed this issue? How can I do the same for my website.
I know a bit about composer. but don’t know how to “recreated the autoloader” for wordfence plugin.

I have the same error and it’s driving me CRAZY!

thanks!

Hi,
i discovered that this error occurred for lots of websites. here is an example in your forum.

I think what @iragination said in link above is important. one other thing is that after I deleted the plugin files and reinstall wordfence, my site works fine. but later, exactly on next Thursday, the site will crash! my website crashed again today… for 3rd Thursday in a row! What task is scheduled on Thursdays? any update? any use of Class ‘GeoIp2\Database\Reader’?

I think you guys should update the plugin with a patch to fix this bug. this is not a minor host issue…

hello,

you can install the plugin “Wordfence Assistant” plugin in order to delete all wordfence files and configs.

if you can’t login to your website and facing a white dead page, you can go to plugin folders in you host admin panel (like cpanel, direcadmin,…) and rename the wordfence folder/directory to something like wordfence2. this will disable the plugin, when you reopen the website.

keep in mind that you can also debug the problem and fix it instead. for debugging, go to your wp-confing.php file and set debug mode true:
define(‘WP_DEBUG’, true);
then, relode website and see what’s wrong.

hope this help,
Sadegh

Thanks Oliver.Ibanez, this worked for me now.
how can i see the attacker ip address?