bjf2000

OK, that explains it. I would never have connected the two.

The reason this used to work but no longer does, is because in late August, when we finally upgraded from the latest WP 4.9x to WP 5.x, our host switched our installation over to being managed by “Softaculous,” which is a “commercial script library that automates the installation of commercial and open source web applications to a website.”

And if I go into that, look what I see:

View post on imgur.com

Before Softaculous we (via other means) were always configured to automatically upgrade only minor WP versions automatically. That’s why Wordfence always used to update but then stopped once Softaculous took over.

And I was kind of wondering why we were still on WP 5.2.4 and not 5.3, but in the back of my mind I was thinking that may be considered a major version jump (as opposed to a hypothetical 5.2.5, which would be minor). Clearly not.

I’ll have to remember this when WF 8.0 comes out, because that will not auto-update when set on “Upgrade to minor versions only.”

Thanks

Thanks

On the theme, it’s possible, though it’s hard to understand how it would relate. I put it here if you want to take a look at it:
https://www.upload.ee/files/10810126/functions.zip.html

There’s nothing in wp-config.php (which hasn’t changed in several months) about updates that I can see:

RewriteCond %{HTTP_USER_AGENT} (BUbiNG) [NC]
RewriteRule .* - [R=403,L]

# Remove any previously set header from the 'onsuccess' table.
Header unset Strict-Transport-Security

# Set the header in the 'always' table for HTTPS requests, replacing any previous header.
Header always set Strict-Transport-Security "max-age=31536000" env=HTTPS

# For HTTP requests, the header should not be sent.
Header always unset Strict-Transport-Security env=!HTTPS

# BEGIN litespeed noabort

RewriteEngine On
RewriteRule .* - [E=noabort:1]

# END litespeed noabort

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>

# END WordPress

deny from 159.8.14.107

# Wordfence WAF
<IfModule LiteSpeed>
php_value auto_prepend_file '/home/oursite/public_html/wordfence-waf.php'
</IfModule>
<IfModule lsapi_module>
php_value auto_prepend_file '/home/oursite/public_html/wordfence-waf.php'
</IfModule>
<Files ".user.ini">
<IfModule mod_authz_core.c>
	Require all denied
</IfModule>
<IfModule !mod_authz_core.c>
	Order deny,allow
	Deny from all
</IfModule>
</Files>

# END Wordfence WAF

Thanks

I checked cron, and there’s a lot there. What should that job be called? I see these mentioning Wordfence:

wordfence_ls_ntp_cron
wordfence_daily_cron
wordfence_hourly_cron
wordfence_start_scheduled_scan
wordfence_email_activity_report

On wfConfig, to make sure “autoUpdate” is DISabled (don’t we still want it ENabled)? This is what we have for all mentions of “update,” but I’m not sure what state it’s in (1=On?). Maybe you can tell:

View post on imgur.com

Thanks

Great, thanks

Wild theory: Because it’s .ca?

OK, I misunderstood then. I did see that example notification of v3.9, and noted that it looked different than what I still see, but I attributed that to just a change in style over the years.

It turns out, however, that there are simply multiple notifications up there.

Thanks

Wanted to report back that it works! Thanks.