smallguy

Vimexx unblocked the managewp ip eventually

Update, Vimexx unblocked ManageWP ip

Nope, they are not willing yet. ManageWP is investigating it and corresponding with them to pursuade them into doing this…

Hi Dennis,
ManageWP can’t do anything about it. You must email VimeXX to whitelist the 54.191.137.17 IP

Just found out that my webhoster VimeXX has blocked you, with the following reason (I’ll translate)

VimeXX support quote:

ManageWP uses Amazon’s network for hosting and this IP range is blocked by us because of abuse coming from those IP addresses. Unfortunately we can’t just unblock that, ManageWP should contact Amazon about this so they check our abuse reports and come up with a solution. We cannot unblock IP addresses if they regularly cause nuisance.
<end quote>

As you can expect, this can take some days, meaning that all VimeXX customers are blocked for this ManageWP service (and yes I’m a paying customer at both of them…. quite some experience this…

Same experience here. Worst plugin around to manage your WP. Never had a flawless update ever, always false negatives. Support is the worst too.

Since 2 days it totally stopped working, no more connections possible, nothing. And I’m a paying customer.

Totally agredd! Plugin and support is the worst ever. Same experience.

Hi @gabelivan Thanks for responding. Yes I had to lower to 1.3.7.7 in order to have things work as expected.

Hi @abwaita
Awesome reply. You found the Asset CleanUp bug here. I rolled it back to Version 1.3.7.7 and will contact their plugin support. Thanks!

Hi @robert681
I sent you email with screenshots etc…, with the text as below:

About the above discussion, some screenshots.

This is a Woocommerce install with ‘customer’ role that currently have the 2fa status “Required but not configured”. This results in a redirection loop when customers are trying to log into their customer account.

What I need is to have WC customers login without 2FA.
Your answer was:
So you want the users whose role is “customer” to log in to your website without 2FA. Is that correct?
If that is the case, you do not need to exclude that role, you just should not enforce 2FA on them via policies.

So I changed my settings, from exclude customer role, to only apply to certain roles, see attachment. Unfortunately this will not change anything to the existing customer roles, only for new customers, since only they will now get the 2fa status
“Not required & not configured” and they can login without 2fa. (attachment)

The initial question remains:
How to change the 2fa status for current ‘customers’ from “Required but not configured” to “Not required & not configured”`

Hi @robert681
The problem is the 2fa user status which means that I can’t change the 2fa user role to exclude the ‘customer’ role, so that Woocommerce customers can login without a 2fa. In this case this website now has “Required but not configured” at the 2fa (customer) role status.

Excluding the customer role in 2fa ui is not changing the current “Required but not configured” status…

Hope this helps..

Hi @robert681 thanks and yes a quick fix would be very helpful, since this website in particular is a webshop where it’s customers can’t login into their account.

@sterndata
Thanks, That was’nt my intention to do so ??
Meaning, never in a public forum…

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

Thanks @giuse
Before I do anything, let me say that after installing Oxygen + Oxygen Woocommerce on this WP I installed your Freesoul and deactivated Oxygen as the only plugin like suggested by Sridhar howto. So I guess that means that no other plugin besides Oxygen (+ lateron also Oxygen Woocommerce) is disabled by Freesoul, right? IMHO that would mean I can’t enable any more plugins that would be needed by the theme, since they all are already enabled ??

Or am I missing something?

Note: Debug only shows below deprecated warnings when Oxygen (wc) + Freesoul is deactivated

Deprecated: Function create_function() is deprecated in /home/tsttngwatch/domains/test.tngwatches.com/public_html/wp-content/plugins/locatoraid-pro/modules/widget.wordpress/widget_searchform.php on line 87

Deprecated: Function create_function() is deprecated in /home/tsttngwatch/domains/test.tngwatches.com/public_html/wp-content/plugins/locatoraid-pro/locatoraid-pro.php on line 67

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

Hi @giuse,

Below what I see displayed on the homepage when debug is true.

Fatal error: Uncaught Error: Call to undefined function new_etheme_get_image() in /home/tsttngwatch/domains/test.tngwatches.com/public_html/wp-content/plugins/legenda-core/inc/shortcodes/banner.php:38 Stack trace: #0 /home/tsttngwatch/domains/test.tngwatches.com/public_html/wp-includes/shortcodes.php(343): etheme_banner_shortcode(Array, '</p>\n<h1 style=...', 'banner') #1 [internal function]: do_shortcode_tag(Array) #2 /home/tsttngwatch/domains/test.tngwatches.com/public_html/wp-includes/shortcodes.php(218): preg_replace_callback('/\\[(\\[?)(banner...', 'do_shortcode_ta...', '[banner font_st...') #3 /home/tsttngwatch/domains/test.tngwatches.com/public_html/wp-content/plugins/js_composer/include/helpers/helpers.php(240): do_shortcode('[banner font_st...') #4 /home/tsttngwatch/domains/test.tngwatches.com/public_html/wp-content/plugins/js_composer/include/templates/shortcodes/vc_column.php(94): wpb_js_remove_wpautop('[banner font_st...') #5 /home/tsttngwatch/domains/test.tngwatches.com/public_html/wp-content/plugins/js_compo in /home/tsttngwatch/domains/test.tngwatches.com/public_html/wp-content/plugins/legenda-core/inc/shortcodes/banner.php on line 38