nicholaswyoung

Could you perhaps tell me what configuration settings you changed…

Sure. In the end, my issue was that domain mapping wasn’t truly activated. Once I configured the domains (in Network Admin > Settings > Domains) everything worked.

But, to recap, my method for setting up a multi-site install is as follows:

1. Setup the basic network parameters.
2. Install the multi-site plugin, and create your first site using a subdomain (noting the site_id as you do so.)
3. Setup domain mapping by visiting Network Admin > Settings > Domains and adding the domain there. Make sure to input the site_id from the last step. (Do not map the network’s principal domain.)
4. Go back to your Network Admin > Sites page and make sure the domain mapping is correct. Also check that the super admin has access to each site by looking at the Users column.

After that, point your A records and you should be good to go.

I’m not exactly sure what you mean, as a few items on that list are virtually unknown to me at this point.

The credentials I’ve been using are authorized on every domain. The domain mapping looks correct in the site options, and I haven’t changed any other options beyond the domain. Everything else is stock.

What you’re experiencing is called cross-domain browser protection. You can’t use a cookie on multiple sites, even with integrated logins, with different domains.

Not exactly. Even if I try to login (by inserting my credentials) and hitting the “Log In” button – it still won’t authenticate me. It starts to redirect to /wp-admin as it should, then redirects away.

The only way I can log in on that domain is to modify the DOMAIN_CURRENT_SITE constant, which then disables logging in on any other site in the network. I understand how cross-domain browser protection works, and this isn’t it.

It should authenticate with the same super admin credentials as the main network site, correct?