• Hello. Just installed and configured this great plugin alongside Wordfence (hopefully they will work nicely together), the main reason I got it, was to change my username and login page (to hide it). After configuring everything else I noticed that plugin attempted to change only admin username, but my username was Administrator, so it didn’t change that. Maybe you could add administrator also to be changed? As this is also commonly used username.
    As I mentioned, the main reason to get this plugin was the login page. I just don’t want anyone to see it and attempt to log in. I thought it would do the job, but after configuration I realised that /wp-login is not included together with other slugs like /wp-login.php. I’m not sure about others, but for me /wp-login is always where I log in, so I would assume that hackers know that slug too 🙂 Could you please add that to disabled list as well?

    Also, is this plugin compatible with wordpress 4.4? Is an udpate coming?

    Thank You very much!

    https://wordpress.org/plugins/better-wp-security/

Viewing 8 replies - 1 through 8 (of 8 total)
  • @mamaslt

    Duplicate of this topic.

    Website hosted at 1&1 UK ?

    dwinden

    Thread Starter MamasLT

    (@mamaslt)

    Hello. No it’s not 1&1. And don’t really see the connection between hosting provider and website slugs.

    @mamaslt

    Ok so let’s try and get a better understanding of this.

    In a vanilla WP env the WP Dashboard login screen can only be accessed using the following default slugs:

    • wp-admin
    • wp-login.php
    • login
    • admin
    • dashboard

    Notice wp-login is not included in the list.

    So where does that slug come from ? Perhaps you can ask your hosting provider … Unfortunately there was no definitive answer to this question in the other topic …
    But it seems it is related to the Apache env as configured at your hosting provider … I’m not saying it is but it would fit the picture …

    dwinden

    Thread Starter MamasLT

    (@mamaslt)

    Maybe we should ask the wordpress authors if /wp-login is included somewhere in a code or not?

    @mamaslt

    It’s not. Check in the wp-includes/canonical.php file:

    /**
     *
     * @global WP_Rewrite $wp_rewrite
     */
    function wp_redirect_admin_locations() {
    	global $wp_rewrite;
    	if ( ! ( is_404() && $wp_rewrite->using_permalinks() ) )
    		return;
    
    	$admins = array(
    		home_url( 'wp-admin', 'relative' ),
    		home_url( 'dashboard', 'relative' ),
    		home_url( 'admin', 'relative' ),
    		site_url( 'dashboard', 'relative' ),
    		site_url( 'admin', 'relative' ),
    	);
    	if ( in_array( untrailingslashit( $_SERVER['REQUEST_URI'] ), $admins ) ) {
    		wp_redirect( admin_url() );
    		exit;
    	}
    
    	$logins = array(
    		home_url( 'wp-login.php', 'relative' ),
    		home_url( 'login', 'relative' ),
    		site_url( 'login', 'relative' ),
    	);
    	if ( in_array( untrailingslashit( $_SERVER['REQUEST_URI'] ), $logins ) ) {
    		wp_redirect( wp_login_url() );
    		exit;
    	}
    }

    As you can see ‘wp-login’ is not recognized as a default WP Dashboard URI.

    dwinden

    Thread Starter MamasLT

    (@mamaslt)

    So… What do we do? 🙂
    I think I will try this: WPS Hide Login. Do you have any comments on that one?
    Also I noticed that “Add New” plugin does not show plugins available online anymore. It gives me this:
    An unexpected error occurred. Something may be wrong with WordPress.org or this server’s configuration. If you continue to have problems, please try the support forums.

    Any ideas?

    Thread Starter MamasLT

    (@mamaslt)

    yes. WPS Hide Login works as expected. So if they can do it so should iThemes…

    @mamaslt

    What you should do is contact your hosting provider and ask them for an explanation of the wp-login slug …

    I guess the “unexpected error occurred” issue was either a temporary WP WordPress.org or internet connection issue …

    I think adding a single RewriteRule line (as described in the other topic) to the .htaccess file is the simplest solution.
    Mimimum impact, maximum result.

    So I guess this topic can be marked as ‘resolved’…

    dwinden

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

The topic ‘Hide Login Area Does Not Hide /WP-LOGIN’ is closed to new replies.