Peter

We have tested both Litespeed Cache and quic.cloud after the last update and it works properly on our end.

Also, other customers of ours who encountered this confirmed that the issue is no longer occurring. On top of this, a large part of our userbase uses Litespeed Cache and we didn’t receive any other reports of such issues, so it could be something isolated to your end.

Would you mind checking if you have the latest version of the plugin?

I was just about to write to update the plugin as our developer added a fix over the weekend which takes care of this, but glad to see a confirmation that everything is alright now.

In case anything else comes up, we are one reply away!

We tested with the latest version and it worked with both cloud and caching. If all IPs were added it should work properly.

Would you mind sending us a screenshot of the IPs?

??Hi Radu,

Thank you for bringing this to our attention.

After looking over quic.cloud we found their IP list.
https://www.quic.cloud/ips

Please go to Change Paths > Level of Security > Whitelist IPs and add all their IPs to be whitelisted. This should ensure a smooth functionality.

My apologies for the confusion, it looks like this was a new addition which I wasn’t aware of.

So to confirm, yes it’s indeed possible to set 2FA for individual emails.

As for what you wish to achieve, I’ve talked about it with our developer team and it looks like something like this can be done. In wp_usermeta add meta_key “_hmwp_email_address” for the user ID email.

I’m not quite sure that I understand, as the 2FA is enabled for the whole login page, which is applied to all users, not for a part of them.

Can you give me some more details about “I have activated it manually for several users”?

Hmm, that’s quite strange. Unfortunately, the images are broken, and can’t view them. Would you mind sending them again but using a link? You can use Google Drive, Imgur, or any other tools you prefer.

Thank you!

??Hi,

Thank you for reaching out.

From what you describe it sounds like you are using an older Starbox version.

Please update to the latest version of the plugin as it’s 100% possible to disable Starbox for certain categories. This can be done from Starbox > General Settings > Don’t show your author boxes for.

Let us know if you face any further difficulties.

??Hi,

Thank you for your question!

At the moment the 2FA is added to the login page for all users regardless the role.

However, that’s a great idea and I’ll share it with our product team so they can look into it for future updates.

In the meantime, please feel free to add it to our roadmap at https://squirrly.feedbear.com/roadmap, so other users can also vote on it!

??Hi,

Thanks for reaching out!

You can use do_shortcode to call it in PHP, as required by WordPress. This must be added to the login form just like the [hmwp_bruteforce].

Please give it a go an let us know if you face any difficulties.

??Hi,

Glad to hear that you found the source of the issue.

Quite strange to hear about the redirects, as the only automatically redirects we make is for 404 pages. My educated guess would be that a redirect import was made with some strange redirects.

In any case, should anything come up, we are one message away.

??Hi Aaron,

Thank you for reaching out!

From our tests we are compatible with Nitropack and didn’t receive any reports of issues from our customers. What I could recommend is trying it out with Safe Mode and reach out to us in case you face any difficulties.

Thank you for your understanding, it’s really appreciated! We do understand your situation and see how it can be troublesome, so we’ll keep it in the backlog and think for a better solution for future updates.

We were able to keep the latest update, however, due to the issues it created we will keep it like this.

For the previous keywords that you weren’t able to remove please let us know what are the posts where they are assigned and we’ll try to remove them from the Cloud.

It looks like the update we made it also created some unexpected issues for another feature of ours. We’ll keep investigating the matter to see what else can be done.

Thank you for your understanding and patience!