[wp-trac] [WordPress Trac] #47630: Multisite: Admin dashboard links are malfunctioning on mapped domain
WordPress Trac
noreply at wordpress.org
Wed Jul 10 03:49:37 UTC 2019
#47630: Multisite: Admin dashboard links are malfunctioning on mapped domain
--------------------------------+----------------------------------------
Reporter: kalico | Owner: (none)
Type: defect (bug) | Status: new
Priority: normal | Milestone: Awaiting Review
Component: Networks and Sites | Version: 5.2.2
Severity: blocker | Resolution:
Keywords: | Focuses: administration, multisite
--------------------------------+----------------------------------------
Comment (by kalico):
For what it's worth, I have started over completely from scratch: empty
database, fresh install of WP, upgraded it to MU, and mapped a domain.
Still having difficulties. The mapped domain doesn't do the weird admin
redirect described above, but I can't get past the login screen.
http://dev2.nroc.org/wp-admin
redirects me to
https://dev2.nroc.org/wp-login.php?redirect_to=https%3A%2F%2Fdev2.nroc.org
%2Fwp-admin%2F&reauth=1
and my superadmin login does not work there.
https://wordpress.org/support/article/wordpress-multisite-domain-mapping/
>> Map Domains in DNS
gives this cryptic and technically inaccurate description of how to point
mapped domains to the server.
''Make sure all the domains you want to use are already mapped to your DNS
server. The additional domains should be parked upon the master domain.''
We do have two domains resolving to our AWS server, and both of them DO
bring up the proper website when mapped:
dev2.nrocnetwork.org >> primary site
dev2.nroc.org >> secondary site located at dev2.nrocnetwork.org/nroc
But in admin it's a different story.
dev2.nrocnetwork.org/wp-admin >> primary site dashboard (GOOD)
dev2.nroc.org/wp-admin >> login screen (redirect described above).
We decided to try a different DNS configuration. We changed from A record
to CNAME as follows:
was:
dev2.nroc.org - A - 54.xxx.xxx.xxx
and now:
dev2.nroc.org - CNAME - dev2.nrocnetwork.org
But that didn't fix the problem.
Any help at all would be greatly appreciated. Perhaps something is missing
from the instructions? or our server is configured wrong? I really don't
want to go back to a domain mapping plugin if wp core has this capabilty
built in.
Thanks.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/47630#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list