2 Comments
  1. Sure, presumably for a website the public don’t need to log in, so take the site “offline” and publish a static copy. Then there’s no longer anything to log in to, you won’t need to pay hosting fees (static hosting is free), it’ll be much quicker and it won’t fail after a plugin update. 😉

  2. Blocking IPs is usually ineffective. Use strong unique passwords, use 2fa on all admin level accounts, keep software stack updated, don’t keep unnecessary plugins around, replace plugins that haven’t been updated in a year, add Cloudflare to the mix if possible, etc. If you’re the only one logging into the admin area, you can also put wp-login.php behind http authentication. If it’s a VPS or dedicated server, you can use crowdsec to prevent bruteforce protection at firewall and web server levels (much faster and more efficient than any WordPress plugin).

    Login attempts are not a cause for concern on their own, unless they’re happening in the thousands or more every day, which can put unnecessary strain on the server. If you implement some of the above measure your site will be safe and brute force attempts will also be blocked.

 

This site will teach you how to build a WordPress website for beginners. We will cover everything from installing WordPress to adding pages, posts, and images to your site. You will learn how to customize your site with themes and plugins, as well as how to market your site online.

Buy WordPress Transfer