jpb_adx

so can somebody summarize the correct procedure to update the plugin, I’m a bit lost here

Same issue here, had to restore application from backup. The sequence of events as I recall was: updated plugin; logoff; modify wpconfig.php; login; got to admin screen with message regarding something about redis, went to redis settings in plugin; message went away; site broke admin not working; logged off; login screen quit working; attempts to refresh browser could not find login page; restored from backup

Regarding the AM360 license check, it works when the admin is logged in. But to a logged off user or at the alternate login/logoff screen it is apparently blocked, thus the maintenance mode message from AM360 (which prevents subscribers from logging in).

From AM360 Support:
If they could explain what changes they had made we could perhaps assist further.

Regarding version 8.4 from your blog:
The custom login page feature has been updated to eliminate possible conflicts with themes and other plugins.

Can you shed any light on this please?

Regarding the maintenance mode message in screenshot of alternate login above, per AM360 support:

ActiveMember360 only shows the maintenance mode message if the license is not active.

This would indicate that communication to our license server is not working or more likely blocked by WP Cerber at the time of that screenshot.

This is the response I got from AM360:

We use the standard WordPress authenticate filter to perform our validation/authentication based upon ActiveCampaign data any time a user logs in to WordPress.

See: https://codex.www.ads-software.com/Plugin_API/Filter_Reference/authenticate

We call the filter as follows: add_filter( ‘authenticate’, [ $this, ‘authenticate’ ], 999, 3 );

The messages you are seeing are from ActiveMember360 from our own function hooked into authenticate.

Whatever changes WP Cerber have made recently this is obviously interfering with that process. If we understand you correctly this worked before their last update.

This is a process we have used in our plugins for ten years. There is nothing wrong in that respect with our process.

Given the above perhaps WP Cerber can determine what change they as made that would interfere with the authentication process.

I have reactivated your plugin and am trying to see what I can learn via the diagnostics. Although I do not know if this is related, do you have a recommended frequency with which to run the cron.

I may still have an issue with my cron scheduler:

Maintenance Tasks
Hourly task #1 has never been executed
Hourly task #2 has never been executed

Daily task has been executed 2 days ago and it took 0 seconds.

Hourly task #1 scheduled for July 15, 2019, 3:00 pm (in 9 mins)
Hourly task #2 scheduled for July 15, 2019, 3:10 pm (in 19 mins)
Daily task scheduled for July 15, 2019, 3:20 pm (in 29 mins)

Background tasks: 0

Note: the internal WordPress cron launcher is disabled on this site.

An external cron launcher has not been configured or does not work properly.

Do you have any insights regarding the scheduled task cerber_bg_launcher, which according to site health check failed to run. Would this message result if I was using an external cron schedule on the server side?

Thank you for that feedback. My plugin stack has not changed in over a year, and in regards to membership plugin, it has not changed in several years and since I started also using WP-cerber. So this is a fairly recent development. When I deactivate WP-cerber, the problems are no longer present. It does seem rather obvious it is probably a conflict, but it came about apparently with recent changes to your plugin. I am in the process of setting up some PHP WP error logs and see what that says about the issue. I have not inquired yet with the membership plugin support.

I had no luck resolving the maintenance mode message on my alternative signon page but it might be a clue. As before, deactivating WP-cerber resolves these issues, and my subscribers can login.

Regarding this issue of logging in subscribers, I have an additional message showing up and it may be easy to address (I am looking into it). It says I am in maintenance mode and only admins can login.

Login Error Screenshot

Perhaps a separate issue, WP site health check has informed me: The scheduled event, cerber_bg_launcher, failed to run. I have WP-cron disabled in wpconfig and it instead is set to run every 45 minutes by the server.

• This reply was modified 5 years, 8 months ago by jpb_adx.

Here is the link

I don’t know if that error message is coming from WP Cerber or AM360. But the AM360 login process worked before and now it does not, unless I deactivate WP Cerber. Or is there a setting somewhere?

I’ve solved my own problem, another security plugin was blocking the webhook due to a flagged user agent, and generating the HTTP 403. Traffic inspector was just logging this event. Sorry for the confusion!

I whitelisted the IPs too but still, those webhooks always get blocked HTTP 403 Forbidden
I also set traffic inspector to use whitelist

I have verified the regex is correct at https://regexr.com/
{\/.plugin.+}

The whitelisting is not working, webhooks always blocked. Also set the regex in bot detection antispam…

I thought those log entries might be related to the scanner, but apparently not, as I re-installed and attempted to run the scanner without generating any errors in the PHP log. However, the scanner still hung as before.