Viewing 15 replies - 1 through 15 (of 19 total)
  • Plugin Author Ron Rennick

    (@wpmuguru)

    Is it remote login that’s not working or login in general?

    I came online searching for this because it is happening to a new site I set up on my multisite. If the domain is set to be primary domain I can not login. No error message given.
    I have to go into the multisite, remove it as the default and then I can log into that blog.

    it only seems to be happening on a new site I set up. This is what shows up in the browser

    ‘humblebumble.com/wp-login.php?redirect_to=http%3A%2F%2Fhumblebumble.influencer.biz%2Fwp-admin%2F&reauth=1’

    I don’t know if that makes sense or not. It is telling the main domain to redirect to the multisite domain and nothing happens.

    Thread Starter Prometheus Fire

    (@prometheus-fire)

    @ron, we are able to login from the main site, but when subsite owners attempt to login to their site at mappeddomain.com/wp-login.php it fails. It just reloads the page. Even as superadmin, I wasn’t able to login to subsite’s with my account via the subsite login page.

    I’ve tested this on 3 different multisite networks and the result is the same on all 3. I’ve had to downgrade to 0.5.4.3 to keep things running smoothly.

    We were also having this issue with our site. After updating to the 0.5.5 and checking “Redirect administration pages to site’s original domain (remote login disabled if this redirect is disabled)” I am noticing that when trying to access the wp-login.php on subsites it doesn’t redirect to the subdomain url for logging in. It stays on a page similar to what “helpology” mentioned.

    We fixed the issue but using 0.5.4.3 in which we have “Redirect administration pages to site’s original domain (remote login disabled if this redirect is disabled)” checked and also “Remote Login” checked. If we do not check “Remote Login” then when trying to go to the login screen for a subsite it doesn’t redirect to the subdomain login. If I try to login on the mapped domain then I am sent to a 404 which is my ip followed by a $ so something like “123.123.123.123/$”.

    Biggest thing that I noticed with 0.5.5 was that I was unable to login to subsites at all (including using super admin). I had to login to the root site and then go to the backend to access it.

    How can I get to download the 0.5.4.3 version? At least it would help resolve the problem in the meantime. No one on the network has noticed or sent in a support request with any problems yet and I would like to avoid that if I could.
    Thanks
    Diane

    Thanks @art Armstrong – appreciate that ??

    Yeah same for me, sub sites just refresh on login page with no error when trying to log in after latest update.

    If it helps @go3asy going back to 0.5.4.3 sorted out the problem for me.

    OK, so its not just me! My site login for a mapped domain subsite stopped working as well, the page would just refresh with no error message.

    The fix for me was to manually go into “Edit Site” from wp-admin as Network admin and edit the home and site URL to match the mapped domain rather than the subdomain URL. But, I didn’t need to do that before until this recent update.

    Had to do this same thing for another issue a few weeks back, where featured images on front end were referencing subdomain instead of mapped domain. Hopefully, there is no downsides to changing my home and site URL to the mapped domain as I have done. It fixed the issue at least.

    We were having a similar problem here, and I was able to pinpoint the source. When the URL of the login page matches the original siteurl value, something like:

    https://rootsite.com/subsite/wp-login.php

    the login form action is still set to:

    https://mappeddomain.com/wp-login.php

    The mismatch is causing the problems, though I’m not sure whether the sudden spate of problems people are having is due to a change in the plugin itself or to recent browser security updates.

    I manually changed wp-login.php’s form action on a test installation of multisite so that the form action matched https://rootdomain.com/site/wp-login.php, and the login was working correctly again.

    WP uses the site_url() function to build the form action. This plugin is doing things to change the value of site_url() to the mapped domain, and on the login page this is creating the mismatch.

    I haven’t come up with a fix yet, but I’m exploring the possibility of using a filter to fix the form action value. Really this needs to be adjusted in the plugin itself so that on the login page the form action matches the current URL.

    We created a must-use plugin and added two functions that have fixed nearly all of the problems we were having. Here’s the code if you want to try it out:

    // Takes care of form action issues to prevent mismatch between the URL of wp-login.php and site_url(), which causes authentication to fail
    function fix_remote_access()
    {
    if (substr_count($_SERVER[‘PHP_SELF’], ‘wp-login.php’)):
    remove_filter(‘pre_option_siteurl’, ‘domain_mapping_siteurl’);
    endif;
    }
    add_action(‘init’, ‘fix_remote_access’)

    // Used in place of redirect_login_to_orig()
    // Takes care of login page URL issues to prevent mismatch between the URL of wp-login.php and site_url(), which causes authentication to fail
    function new_redirect_login_to_orig()
    {
    if (function_exists(‘get_original_url’)):

    if ( !get_site_option( ‘dm_remote_login’ ) || $_GET[ ‘action’ ] == ‘logout’ || isset( $_GET[ ‘loggedout’ ] ) ):
    return false;
    endif;

    $thisurl = (is_ssl() ? ‘https://’ : ‘http:/’).$_SERVER[‘SERVER_NAME’].$_SERVER[‘REQUEST_URI’].’
    ‘;
    $url = get_original_url( ‘siteurl’ );

    if (!substr_count($thisurl, $url)):
    $url .= “/wp-login.php”;
    echo “<script type=’text/javascript’>\nwindow.location = ‘$url'</script>”;
    endif;

    endif;
    }
    add_action(‘login_head’, ‘new_redirect_login_to_orig’);

    This happened to me regardless of what setting for remote login was. Since I have not noticed anything significant about the update aside from a new setting under remote login, I reverted back to the old plugin and it’s working fine. Just figured I’d respond here so I could be notified of when the new version is fixed so I can update yet again. ??

    I had a problem recently with sites redirecting and taking 20 seconds to load. After updating, the problem went away but so did the plugin. I got an error message saying “The plugin domain_mapping.php has been deactivated due to an error: Plugin file does not exist.” I can’t find it now. I will upload the old plugin or ask my hosting company to do a restore of my site. I’ll leave the old plugin until there is another update.

    I’m sorry, I made a mistake. It was installed, I just didn’t see it at first. However, after updating, it deactivated. I re-network activated and it seems ok.

Viewing 15 replies - 1 through 15 (of 19 total)
  • The topic ‘Remote login is not working with recent update’ is closed to new replies.