I saw there was an option for pointing an external domain name at a blog hosted here, so I tried it and apparently screwed something up and now can't get to my site's dashboard to undo it. my blog url is dlbaker.commons.gc.cuny.edu and I was trying to point the domain damonlorenbaker.com at it. Now I just get an empty blank page when I go to the site, and when I go to the wp-admin page I get an apache error. Is it possible to undo the domain settings on your end? I just got started with the site so if you needed to wipe it out to reset it that would be fine. Thanks!
#3 Updated by Dominic Giglio over 6 years ago
Scott, Matt, Boone,
I've gone in and removed the original domain mapping for this blog. I then re-added it but DID NOT check the default domain box. The custom domain: damonlorenbaker.com still does not work. But the original, primary domain, dlbaker.commons.gc.cuny.edu now does.
This leads me to believe that the admin has not setup his domain forwarding at his registrar correctly. Scott, are you in contact with this user? I'll help to setup the domain as best I can, but we will need to converse with them to make sure the A-record is correct. But as of right now they can get back into the site using their original Commons domain to continue setting it up.
Sorry for the delay on this issue.
#6 Updated by Dominic Giglio over 6 years ago
Damon (site owner) and I have been conversing about this issue mainly over email. I think we're close to getting his A-record correctly setup at his registrar (joker.com), but I'm getting some weird results from our site when his domain (damonlorenbaker.com) is set as the primary in Domain Mapping settings.
If I visit:
The site will not render, But if I visit:
It does work. I'm wondering if this issue will end up being related to our other Domain Mapping issues? Specifically #2245 (ssl errors).
I've added Andre as a watcher incase he's in the middle of some server related tweaks that would prevent http from rendering but allow https to render properly.
#7 Updated by local admin over 6 years ago
- Status changed from Reporter Feedback to Resolved
This domain name (damonlorenbaker.com) has to be entered in the web server's configuration in addition to the WordPress admin interface ("domain mapping") as well.
The reason why it works via HTTPS is because there's only one vhost configured on the HTTPS port so even though this domain record doesn't exist, it defaults to the WordPress installation and everything is cool. We have other vhosts on the HTTP port so the domain record has to be named explicitly.
I added the domain now though and am marking it resolved. Rock on.