iraqiboy90

If you are running PHP 8.1, downgrade to PHP 8.0 or disable the plugin and wait for version 17.9

https://www.ads-software.com/support/topic/welcome-panel-php-temp-fix/

Thanks for this fix. php 5.6 is dead but I’m currently forced to stay with it, for now…

Admin dashboard should still work. Worked for me. Enter it with url YourDomain.tld/wp-admin
Or
Disable the plugin by changing its folder name to something else with FTP access and then refresh site.
To download old version, on the frontpage of this plugin on this site find the “developer mode” button then scroll to the bottom to find a list of old versions to download

Im running ~v5.6.
Stuck with this php version for now

• This reply was modified 3 years, 5 months ago by iraqiboy90.

I got my email server setup and I got a flood of emails, including the emails sent by the error messages mentioned above

Here is one of them:

An error of type E_ERROR was caused in line 44 of the file /var/sentora/hostdata/productionscape/public_html/productionscape_com/wp-content/plugins/wordfence./models/common/wfGeoIP2.php. Error message: Class 'GeoIp2\Database\Reader' not found

Not when two sites has wordfence at the same time.

I’ve gone ahead and replaced xcache with Zend Opcache + Redis.

This issue is not solved. Wordfence has compatibility issues with xcache.

• This reply was modified 4 years, 8 months ago by iraqiboy90.

Ok. I just got around to test disabling xcache, and it worked.

Now, I would like to start saying that disabling a feature to fix a problem does not mean that the feature was a problem.

Let me suggest my theory of the problem:
Wordpress asks you on installation to choose a prefix for the database tables, in case you are going to install two wordpresses on the same database.
This problem occurring with xcache could be the same reason. One wordfence is reserving or assigns a “prefix” to the xcache for its data and when the second wordfence tries to do the same, it fails. Now, since all sites shares the same xcache engine/space, then there must be a solution that’s similar to the WordPress database prefix thing.

Here is what I tried so far since the beginning.
I disable the same wordfence feature on both sites, flush the cache from the VPS and then re-activate wordfence on both sites. With each step done, if it wasn’t the culprit, I re-enable the feature again and go to the next feature, doing the same methods again.
I tried all of them. Nothing helped.

Though, I found an article that talks about a cookie that wordfence uses for its live traffic feature that messes up the cache which in turn crashes the site. Now, I know this cookie has been removed since 2018 but that’s the closest thing to an answer I got.

I have one step left to try. I will try to disabled caching on the server and all sites I have on it. When I get time to do it, I will reply here with an answer about it.

• This reply was modified 4 years, 8 months ago by iraqiboy90.

I have an unmanaged VPS, so I have full access to it. I did a “tail -f” for all logs at the same time. The only ones that gets new info is the vhost error log that shows me a standard 500 http error code, and the second one shows me that postfix is misconfigured/disabled. This is on porpus because I’m using external mail service. I’m using an SMTP plugin with external mail server for my other wordpress site. I do have it on the new one as well, but the crash message tries to use sendmail (postfix) instead.

yeah, my postfix/sendmail service isnt working. So there is no email

Try to block a “region” or ISP by manually blocking an IP range (with asterisks or CIDR) within htaccess file (For apache servers). You will need FTP access for this. This is the fastest method, but have higher chance of blocking legitimate users with the same IP range

Or

Sign up for Cloudflare and set up your site on their DNS and it will filter trafic through their service. They have a very nice firewall system for manually blocking countries, IPs or sending a captcha challenge to every user to weed out bot attacks. Cloudflare is free, but needs up to 24 hours for setup time (For DNS changes).
But, if the attacker already has the original IP for the website, then they can bypass Cloudflare and go directly to your website.

I’d recommend a combination of both.
Use the “I’m under attack on cloudflare” to serve EVERYBODY with a captcha, even legitimate users, every 5 minutes. This will stop 80% of the attacks, but shouldn’t be enabled all the time, because it will annoy normal users.
and
htaccess to filter what gets through Cloudflare

• This reply was modified 4 years, 8 months ago by iraqiboy90.
• This reply was modified 4 years, 8 months ago by iraqiboy90.
• This reply was modified 4 years, 8 months ago by iraqiboy90.

and here I tried again by reinstalling wordpress without installing any plugin or themes.
https://i.gyazo.com/7b902585cd9ff79faae362a67ea4aa6e.gif

• This reply was modified 4 years, 8 months ago by iraqiboy90.

It’s a 500 error with no error message logged or shown after having wordpress debug enabled

Site A is running. Then activating wordfence on site B and this is what happens:
https://i.gyazo.com/4ff0a38ef68c924d35d066931cb4b682.gif

In order to gain access again, I either disable the plugin by renaming the plugin folder or by restarting httpd or clearing xcache and then refresh Site B, but then site A will crash on refresh

• This reply was modified 4 years, 8 months ago by iraqiboy90.
• This reply was modified 4 years, 8 months ago by iraqiboy90.