webcoast

Great news for us in agencies! Thanks @mmaunder

Hi one3rdnerd, yes this is a new feature in 7.8.0 and changes the registration process for the free version. The free version is staying, but its not automatic registration any more. You can read about it on their blog https://www.wordfence.com/blog/2022/11/wordfence-7-8-0-announcement/?utm_medium=email&_hsmi=235770461&_hsenc=p2ANqtz-82isoCQh6rb-MdMmkONI0od1QdPbSWnNhs4KiPMvAQFxk5VJ1inEfDtYbxIGn92pDXOq1TD54uMRmvI7WMjXt-rdmlcw&utm_content=235770461&utm_source=hs_email

I agree, it’s going to be a pain for us in agencies, depending on what they come back with as their answer to my question.

I got same errors using PHP8, I will create a new ticket to see if we get a reponse.

Thanks for your reply @wfphil
Nope, the site was not developed in a staging environment, and there is no copy of the site running elsewhere.

I added the site to Wordfence Central, in the Global Configuration for the site on Wordfence Central “Where to send email alerts” field, there is only my own email address. Is this the field you meant?

Regards
Nicola

Thanks for your reply. Yes, the issue has been fixed in the last few hours, it was a javascript problem with the theme and the developers have resolved it.

I had the same problem. I developed a site on a temporary URL (eg using IP address) because the client had an existing website. When I swapped across and made the new site live I used Velvet Blue plugin to update all the references to the old temporary domain. But the canonical URL didn’t swap across to the domain name, it stayed as the old temporary URL.
I installed Yoast Test Helper and clicked on ‘Reset Indexables’ and it worked! Canonicals updated, including pages that use WooCommerce.

Thanks for the plugin!

Hi zachchs, did you ever figure out what was going on? The same thing is happening on my client’s site. I see you didn’t get a response from the developer, did you find another plugin which is working better, or did you figure out what the problem was yourself?
Regards
Nicola

Hi, I have just started having the exact same issue. I noticed that when I logged out yesterday instead of returning to login screen the logout went to the Wordfence notification page that says user is blocked. I had been using the site fine for hours.

I haven’t done invalid login attempts, however a user was blocked overnight for attempting to login too many times with [login] username.

I disconnected from my broadband internet connection, and used mobile hotspot to connect to the site and was able to login. I checked the Wordfence block and there were NO entries for my IP address, my IP showed in the list for successful login. I ran a scan and it was all fine. Then I logged out and straight away received the blocked user message again, so now I am blocked from logging in both from my broadband IP, and my mobile hotspot IP.

Not sure what is going on here, any help would be appreciated.

Hi Jules, the website isn’t live yet, so I can’t send you a public URL.

Hi, I have the same question. I have a client that I need to upgrade to WordPress 5.0.x and their site uses this plugin. But I see that this plugin hasn’t been tested yet in WordPress 5. It sounds like it isn’t working for your site. Is it broken on the front end or in the backend?

Did you resolve the issue? Replace the plugin with a different one? Your webpage link looks ok but I’m not sure if something is missing?

Thanks
Nicola

Hi elnath78, yes the issue was resolved. I ended up sharing the doc page that wfalaa suggested, with the website host support technicians and they made some adjustments to the .htaccess file which resolved the issue.

Here is a section from the .htaccess file, I see they commented out the original noabort and added a different version.
## BEGIN litespeed noabort
#SetEnv noabort 1
## END litespeed noabort

# BEGIN litespeed noabort

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

# END litespeed noabort

Hope this helps.
Regards, Nicola

Hi,
So I have made some progress, and a few things have changed as a result, but the Wordfence version still isn’t being auto-updated.

I sent an email to the hosting provider for this client, and this is what they replied with “As you are on shared hosting we do not have litespeed caching enabled on the server enabled by default however reviewing your wordpress plugins I can see you have ‘litespeed-cache’ enabled, Looking into your hosting account I can also see there was ‘opcache’ enabled, This is a PHP Caching module. I have gone and disabled opcache but havn’t touched litespeed-cache”

So it sounds like even though the server has the litespeed capability, it isn’t enabled for this client (maybe they have to pay extra for it?). So, I have deactivated and deleted the Litespeed plugin which was previously installed. The .htaccess file still contains the following at the very top of the file
# BEGIN litespeed noabort
SetEnv noabort 1
# END litespeed noabort

Even with litespeed cache plugin deleted the site did not auto-update to the latest version of Wordfence, so after a couple of days I updated it manually. As soon as I did that, I received this email :
This email was sent from your website “Queensland Motorcycle School” by the Wordfence plugin at Tuesday 7th of August 2018 at 05:00:30 AM The Wordfence administrative URL for this site is: https://www.queenslandmotorcycleschool.com.au/wp-admin/admin.php?page=Wordfence
To preserve the integrity of your website we are not running Wordfence auto-update.
You are running the LiteSpeed web server which has been known to cause a problem with Wordfence auto-update.
Please go to your website now and make a minor change to your .htaccess to fix this.
You can find out how to make this change at:
https://www.wordfence.com/help/?query=dashboard-litespeed-warning

Alternatively you can disable auto-update on your website to stop receiving this message and upgrade Wordfence manually.

User IP: 127.0.0.1
User hostname: localhost

So it seems that Wordfence is detecting that Litespeed is installed on the server, but since the host says that it is not ACTIVE/ENABLED for this client, Wordfence should be ignoring it. I have no idea whether what the hosting provider is saying is true – is it possible to have a Lite Speed Server, but to not use the litespeed functionality for a site on that shared server?

Let’s assume that it IS possible to have a litespeed server, but to not have the litespeed active. Should there be the no abort or Set ENV in the .htaccess? Should I tick the ‘skip noabort check’ box? What should I do?

Thanks
Nicola

Thanks for your reply. As a suggestion, maybe you should update this page https://www.ads-software.com/plugins/agentpress-listings/ on the right hand side where it says “Tested up to: 4.8.7” to be 4.9.7.

Regards
Nicola

• This reply was modified 6 years, 8 months ago by webcoast.

For me it was a template issue which occured only when I deactivated WooCommerce. The template providers gave me a fix.

Just to clarify, I don’t have ‘User Role Editor’ installed.

These are the plugins that I have installed:
– Akeeba Backup Professional for WordPress
– Coming Soon Page & Maintenance Mode by SeedProd
– Duplicate Post
– Essentials Grid
– MailChimp for WordPress
– Simple Google reCAPTCHA
– Slider Revolution
– ThemeREX Addons
– Visual Composer Extensions All In One
– Watchful
– WooCommerce (DEACTIVATED)
– Wordfence Security
– WP Media Folder
– WPBakery Visual Composer

Maybe if everyone else compares this list to the plugins that they have installed we might be able to narrow it down to a shorter list of common plugins?