Forum Replies Created

Viewing 15 replies - 1 through 15 (of 105 total)
  • I have the same problem:

    PHP Fatal error: Declaration of RCP\lucatume\DI52\Container::has($id) must be compatible with Psr\Container\ContainerInterface::has(string $id): bool in S:\Local Sites\test\app\public\wp-content\plugins\restrict-content\vendor\strauss\lucatume\di52\src\Container.php on line 294


    Using PHP 8.1.9

    Thread Starter Youdaman

    (@youdaman)

    Thanks @wpchefgadget that makes sense, appreciate the insight.

    Apologies again if I came in too hot and strong, it’s just that it seems like every day we receive scam calls and emails and spam from all directions, so it’s sometimes hard to tell the good guys from the baddies.

    Cheers for creating LLAR and good luck with the business 🙂

    Thread Starter Youdaman

    (@youdaman)

    Thanks @wpchefgadget, what you said makes sense re 2FA only sending on correct credentials. My apologies for this misunderstanding.

    The only other odd thing then is that the notifications I receive for failed attempts are for existing usernames and not for more generic/obvious ones like “admin” for example. Could you please clarify why this might be? Is there a way for bots/hackers to retrieve a list of authors/users via a URL?

    Thread Starter Youdaman

    (@youdaman)

    Thanks for the reply @wpchefgadget but I’m not talking about accounts — and the only login attempts I get notified about are for accounts that exist.

    Your plugin is reporting multiple login attempts to account X but the user who owns account X is not receiving any emails from the 2FA plugin, which sends an email with a verification code to the user on legitimate attempts.

    Could you explain why one plugin says there are multiple login attempts but another does not detect any? This is the part that does not make sense.

    I’m suggesting that Limit Login Attempts Reloaded is not being truthful in its reports, but in order to make the reports seem legitimate, there’s a bot (hosted in the cloud at the IP address given in the report, which is likely on AWS given it’s located in Virginia USA) that spams the /wp-login.php route with POST requests so the server logs show alleged “login attempts”.

    I’m happy to be proven wrong, but given the above issue re 2FA not detecting any logins, and the replies I’ve received from what seems to be a puppet account in this thread, I’m leaning towards fraudulent activity.

    Thread Starter Youdaman

    (@youdaman)

    This plugin doesn’t know that I have 2FA installed. But it’s still claiming I have even more login attempts on accounts that are not receiving 2FA verification emails, so these claims are clearly false right?

    I noticed that this plugin was claiming an increase in login attempts, even with XML RPC disabled and 2FA enabled, so I came here to post about it.

    My reply isn’t necessarily unpleasant, it’s just stating facts and asking questions, and your response doesn’t make me feel I was incorrect in my suspicions about this plugin reporting fake login attempts.

    You claim the developers have been helpful to you about this plugin, but all of your posts are in defence of criticism or questions about the legitimacy of the plugin — I don’t see any posts where you’re asking for the help you’re talking about.

    If you are the developer, or even a friend of the developer, and the plugin is indeed giving false positives in order to upsell the premium version, and you’re actively assisting with covering that up, then you’re party to fraud.

    Thread Starter Youdaman

    (@youdaman)

    Another thing that seems dodgy @gregjf908 is that all of your replies are to complaints on this support forum (see https://ww.wp.xz.cn/support/users/gregjf908/replies/) but you don’t seem to claim that you’re affiliated with the plugin.

    You do a great job defending any claims made against it though. Why is that? I don’t believe someone sits on a forum defending a single plugin without some kind of connection to it. Are you a fake account owned by the developer?

    Thread Starter Youdaman

    (@youdaman)

    Thanks for the reply. I understand that bots will keep attempting to hit my site.

    I can see in the logs that the reported IP addresses are there, however they’re doing POST requests to /wp-login.php but I’m not sure that’s a valid attack vector.

    Also, the point I was trying to make above re 2FA is that with every login attempt, the user receives an email with a verification code. There have been no such emails, so the login attempts haven’t actually been real login attempts — it’s just my /wp-login.php page is being spammed with POST requests.

    So I’m saying there’s no legitimate login attempts as claimed by the email I received from the Limit Login Attempts Reloaded plugin. The “attempts” aren’t real. Which also leads to asking why would an actual hacker write a bot that doesn’t try to login.

    The worst it’s doing is filling up my logs with pointless hits to a URL where it can do no damage — and if this is what Limit Login Attempts Reloaded is reporting as potential threats then it’s not being truthful.

    That said I’m happy to be corrected if I’m wrong here, but it seems dodgy.

    Thread Starter Youdaman

    (@youdaman)

    Excellent work! Gracias amigo! 😀

    Plugin Author Youdaman

    (@youdaman)

    I’ve not yet integrated rickykpg’s code into the plugin, and a few people have asked about multiple elements.

    I guess the easiest way for me to implement this would be to create a textarea that lets you specify multiple elements via separate lines, ie one sticky element (and its settings) per line.

    If I have some time soon I’ll have a crack at it 🙂

    Plugin Author Youdaman

    (@youdaman)

    My only guess is Capsule have made a change to their API.

    I’ll have to investigate, thanks for the heads up.

    Plugin Author Youdaman

    (@youdaman)

    My only guess is Capsule have made a change to their API.

    I’ll have to investigate, thanks for the heads up.

    Plugin Author Youdaman

    (@youdaman)

    Usually with troubleshooting plugins it’s best to disable everything (or at least most things) and enable the one you want to get working, i.e. Sticky, and then once that’s working, then enable the others one by one until things stop working, and that way you can figure out which plugin is causing issues.

    Best of luck and let me know how you go.

    Plugin Author Youdaman

    (@youdaman)

    Yes the compression is probably stopping it. I replied on Twitter.

    The best way to troubleshoot is to turn off other plugins and try Sticky by itself. Then once that’s working, turn on each plugin again until you find which is breaking the page.

    The cause (most likely) is the compression that is loading the JavaScript in a compressed way, so that the “jQuery” variable (required by a datepicker by the looks of things) is not there, and this stops the page loading further plugins (like Sticky).

    Plugin Author Youdaman

    (@youdaman)

    Looks like something else is causing a bug on the page when I look at the error console in Chrome: “Uncaught TypeError: jQuery is not a function” — so maybe a plugin is using jQuery instead of $ or jQuery isn’t being loaded?

Viewing 15 replies - 1 through 15 (of 105 total)