• Each time I click Network Admin, I am automatically logged out from WordPress. If I try logging back in immediately, the page simply refresh, I am not redirected to the admin.

    Please advise…

Viewing 15 replies - 1 through 15 (of 15 total)
  • Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    πŸ³οΈβ€πŸŒˆ Advisor and Activist

    Were you ever able to login?

    Is it redirecting you to the domain without the www?

    I’m having a similar problem. Updated a multi-site today from 3.0.1 to 3.1.2, and now I can’t access my network admin.

    My main site is located at mastersite.domain.com and the other sites as site1.domain.com, site2.domain.com etc.

    Now, when I try to access network admin I’m redirected to domain.com, but this domain doesn’t handle the WP-installation.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    πŸ³οΈβ€πŸŒˆ Advisor and Activist

    My main site is located at mastersite.domain.com and the other sites as site1.domain.com, site2.domain.com etc.

    That never should have worked. How did you get it to run subdomains out of a subdomain itself?

    Well… I have a lot of sites setup like this. πŸ˜›

    Create a site, edit the url. Tada.
    The reason I’m doing it this way is I’m running https on *.domain.com.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    πŸ³οΈβ€πŸŒˆ Advisor and Activist

    Right. You’re not supposed to do that.

    You should have installed it on domain.com and then use *.domain.com as you are, but just let the subdomains sort out normally. If you have a subdomain install, WordPress assumes ‘domain.com’ is the ‘root’ install, because that’s what it SHOULD be.

    Can’t install on just domain.com, running several different setups of WordPress. The public site is tied with domain mapping to other domainnames.

    This is a 3.1.2 issue, and I’m quite sure I’m not the only one with this setup.

    Btw, if “you’re not supposed to do that”, why is the option to do this availiable directly under settings?

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    πŸ³οΈβ€πŸŒˆ Advisor and Activist

    Probably because no one thought you’d rename it like THAT. πŸ™‚

    You have to be able to rename a site cause what if you typo blowfish as blofish? But I’m guessing when you make a site it shows up as blogname.master.domain.com right? And you’re changing that to just blogname.domain.com?

    Anyhow, your saying the correct form would be
    master.domain.com
    site1.master.domain.com
    site2.master.domain.com

    That just proves my point. Network admin should still be availiable on master.domain.com, and never ever redirect to domain.com.

    the network admin address is built off the base url of where your install is.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    πŸ³οΈβ€πŸŒˆ Advisor and Activist

    site1.master.domain.com -> master.domain.com

    site1.domain.com -> domain.com

    master.domain.com -> ?

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    πŸ³οΈβ€πŸŒˆ Advisor and Activist

    If master.domain.com is the … MASTER domain, that is you install WordPress in master.domain.com then there should be nothing further.

    IF
    main site = master.domain.com
    THEN
    network = master.domain.com/wp-admin/network
    subdomain = site.master.domain.com
    subfolder = master.domain.com/site

    IF
    main site = domain.com
    THEN
    network = domain.com/wp-admin/network
    subdomain = site.domain.com
    subfolder = domain.com/site

    You seem to have a combo of both, and I would guess that’s what’s making WP throw a wrench.

    Thanks Andrea_r! Everything works, found the problem in wp-config when i double-checked it again. Base url was the key.

    Ipstenu: Network admin is always the address of site #1. My problem was a hardcoded definition that site #1 was “domain.com”. Bummer. πŸ™‚

    ding ding ding! that’s what I was getting at. πŸ™‚

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

The topic ‘Unable to access the Network Admin area’ is closed to new replies.