• Resolved jhaber31

    (@jhaber31)


    Recently I began to address the results of WordPress’s site health report, which is easily available from the WordPress dashboard. It reports a loopback error, and a WP support forum said to get in touch with my ISP (FatCow). The ISP said that while my plan doesn’t support loopback, and while I’m not seeing any problems on that account with my Web page, I might still wish to identify what’s causing the error. To that end, it asked me to disable plugins one at a time, then see if the health issue remained.

    When I got to disabling All in One WP Security, I could no longer log in to see the health report. The URL for site administration that I had bookmarked was not found. It was my site’s home URL, followed by /wp-art-login. This confused me, but I realize now that in installing the plugin, I must have chosen this, I just don’t remember. That’s what I’m asking you to help me understand.

    While I no longer had access, I used FTP to inspect my site. I have a much older and larger site in static html, and I left those files (to which I add every day or two). I use WP merely for a home page blog in order to permit comments, and I installed WP in a “/bog” subfolder, presumably with a redirect so that it appears as my home page. Within this subfolder, I sas a file wp-login.php. I presume this is the default login in the absence of All in One WP Security. So I used this URL in a blogger, and it took me right to the dashboard. From there, I reactivated the security plug in, existed the browser, and restarted the browser. Sure enough, wp-art-login now worked again.

    Can you help me understand what was going on? Thank you! (The security plugin, it turns out, was NOT causing the loopback error.)

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Contributor mbrsolution

    (@mbrsolution)

    Are you running the latest version for aiowps and WordPress?

    When I got to disabling All in One WP Security, I could no longer log in to see the health report. The URL for site administration that I had bookmarked was not found. It was my site’s home URL, followed by /wp-art-login. This confused me, but I realize now that in installing the plugin, I must have chosen this, I just don’t remember. That’s what I’m asking you to help me understand.

    It looks like you activated one of the Brute Force feature in the plugin.

    Can you help me understand what was going on? Thank you! (The security plugin, it turns out, was NOT causing the loopback error.)

    This issue might have been caused by a cache problem in your browser, however I am not 100% sure without knowing fully everything about your site. The good thing is that the plugin and site are working again.

    Thank you

    Thread Starter jhaber31

    (@jhaber31)

    I update both the plugin and WordPress whenever it becomes available. Could you elaborate on the feature I’m likely to have activated? I must have proceeded in awareness, since I do have a related link my browser bookmarks. (And yes, I’m embarrassed I don’t remember enough to answer my own question. At least I was alert enough to figure out how to restore functionality this afternoon.) So it’s really just that that I’m trying to understand, lest it happen again.

    Plugin Contributor mbrsolution

    (@mbrsolution)

    There are times that a simple deactivation and then reactivating a plugin fixes some issues. I really can’t say what might have caused the issue in your site.

    I recommend the following:

    In the future don’t be quick to update plugins, your theme and WordPress without first understanding what has been included in the update. For example: I have a few testing sites which I use for testing purposes. When ever there is an update for one of my clients or my blog I use these testing site for updating and testing if I think it is needed. Security patching can be done straight away most of the times because it is important to patch any security holes. This method allows me to check and see if the updates work. 9 times out of 10 everything works fine, however there is always that 1 time that something might go wrong, hence the reason for running some tests.

    Also when it comes to WordPress I definitely always wait until a couple of months have passed to make sure any bugs found have been reported and patched.

    I hope the above helps you for future reference.

    Kind regards

    Thread Starter jhaber31

    (@jhaber31)

    Interesting, and I do appreciate the help. Still, something doesn’t quite ring true. First, regarding deactivating and reactivating as a fix, bear in mind that it was precisely deactivating it that caused me the trouble, and then reactivating just restored the condition I’d had before (and consider just fine). It’s just a hard condition to understand as well as I’d like.

    As for hesitating on updates, all the conventional wisdom I’ve seen over the years has been to take care to keep current on the very grounds that most updates are security fixes. Anyhow, I still don’t understand the plugin’s options any better (such as whichever one set the login path), and after all that’s all I’m trying to explain. It’s not that I’m finding it broken.

    Plugin Contributor mbrsolution

    (@mbrsolution)

    Anyhow, I still don’t understand the plugin’s options any better (such as whichever one set the login path)

    The login path is set up by one of the Brute Force features below.

    Enable Rename Login Page Feature:
    Enable Brute Force Attack Prevention:

    Regards

    Thread Starter jhaber31

    (@jhaber31)

    Found it! You had it when you mentioned Brute Force. I found that under settings, and it included enabling the option to set a login URL, which it told me to be memorable (and I guess I did). So I’m all caught up and thanks again.

    Plugin Contributor mbrsolution

    (@mbrsolution)

    You are most welcome 🙂

    Enjoy the plugin.

Viewing 7 replies - 1 through 7 (of 7 total)

The topic ‘How did I set login URL?’ is closed to new replies.