Uncaught Error: Class ‘MaxMind\\Db\\Reader’ not found

Hi @flyinghippo!

Sorry to hear that. We’ve had a couple reports about this and it seems to be a possible conflict with another plugin or some other software on the site that uses an autoloader for PHP classes.

Is your site hosted on AWS? Do you know if you are using composer autoloader for any other code on the site?

Yes, our site is hosted on AWS and we’re not using composer. I also tried disabling all plugins/themes and using a fresh install of WordPress.

Hi @flyinghippo!
Thanks for the update. Can you try going here and download Wordfence 7.1.11 and install that instead of the most recent version. If that works, it would be great if you could send me a diagnostics report from Wordfence at that point.

https://www.ads-software.com/plugins/wordfence/advanced/

Let me know how it goes!

No problem! That version works fine. What email do I send it to?

Hi @flyinghippo,
Sorry I forgot to tell you that part. ?? Please send it to [email protected]. It’s important that you mention your forum username in the designated field so I know who the diagnostics are coming from.

Thanks in advance!

Hi @flyinghippo!
I got your diagnostics. Since you have a fair amount of plugins it’s tricky to say if any of them are conflicting with Wordfence.

I’m wondering if you are comfortable editing PHP code, would you consider doing this?

In the file /var/app/current/web/wp-content/plugins/wordfence/vendor/geoip2/geoip2/src/Database/Reader.php on the line before line 53 add this

error_log(var_export(get_included_files(), true));

Then activate Wordfence to let the errors be logged. Then send the error log file to [email protected].

If you send it, please reply here as well so I know to go looking for it in my inbox.

Thanks in advance!

I added the line and sent over the error logs to you from our staging environment (can’t break production). As a side note, I tried disabling all plugins, using twentyseventeen, and using a fresh WordPress install and still received the same result. Pretty sure it’s our environment but not sure what about it is causing the problem.

Thank you!

Hi @flyinghippo,
Sorry for the late reply. Sending you an update via mail just now.

Hi @flyinghippo,
I think we lost touch via email but we’ve made some progress on this case. On a site with similar error we found another plugin was using an out of date composer library which was causing the issue. Is it possible that this could have been the cause for you as well?

Hi there,

Haven’t had a change to disable the apcu PHP extension on our test environments yet but we did catch it happening on some of our other sites hosted on Amazon Beanstalk. Disabling all plugins and using a theme like twentyseventeen did not work for us, either.

Hi again!
Okay, is there any chance there could be an old composer library loading something independent of WordPress plugins? For a custom app? Or something that was part of installation package on these sites?

Not that I’ve seen so far! Some of these sites contain legacy code so I’ll have to dig through them and do a little cross referencing but it seems like it’s related to the environment since disabling plugins and themes doesn’t solve the issue. Most of these environments only get WordPress and plugin updates regularly (no other big changes) and we haven’t had any issues upgrading WF until versions > 7.1.11.