[Plugin: WordPress MU Domain Mapping] Do we still need to use the Trunk Version?

  • Resolved beyonddomaining

    (@beyonddomaining)


    13 years, 11 months ago

    So just yesterday I flew through the install of my WP multi-site – many thanks to the great documentation.

    (I’m actually using 3.0.2, but the Version drop down indicator asked for when I’m making this post stops now at 3.0.1)

    Next, I wanted to get Domain Mapping set up, but I’ve run into some problems in that area.

    I’m troubleshooting that right now, and my first question is if we still need to be using the Trunk version mentioned at Ottopress: https://ottopress.com/2010/wordpress-3-0-multisite-domain-mapping-tutorial/

    I skipped that and just used the plugin version found at www.ads-software.com for Domain Mapping because I noticed the Ottopress Domain Mapping Tutorial was made in June 2010, and then Domain Mapping Plugin at www.ads-software.com had just been updated on 10/28/2010 and so I thought, well, maybe we no longer need to use the Trunk version since they make no mention of it on the official Domain Mapping Plugin info page at www.ads-software.com. And because the Ottopress post is now semi-outdated.

    So my first question is – do we still need to use the Trunk version of the Domain Mapping plugin? (And if so, to relieve further confusion, I would recommend making some kind of mention of that on the official Domain Mapping plugin page on www.ads-software.com.)

    My second question is – if we DO indeed still need to be using the Trunk version, and given I have already used the ‘official’ / ‘regular’ version that is posted on www.ads-software.com (makes no sense to my why a specifically un-functioning plugin would be posted to www.ads-software.com in the first place(?)), what should I do now to back out of what I’ve done, and head down the correct path? Do I need to re-install my WordPress and start from scratch? Or just overwrite the Domain Mapping plugin files and go back through the whole Plugin Install process anew and just re-start that process?

    I should note that everything seems to be fine with the Domain Mapping plugin in many other respects. I am able to add sites and map them within WordPress. My issue right now is that when I go to one of my ‘network sites’ using the ‘network site’ domain name, I end up at a URL that looks like this:

    https://domainname.com/cgi-sys/defaultwebpage.cgi

    with a message that says this: Default Website Page: If you feel you have reached this page in error, please contact the web site owner:

    I’m using a VPS on HostGator. I have the Multi-Site working great using subdomains and my only problem right now is mapping the ‘network’ domain names. The network domain names are at Moniker right now and I’ve added A records to my VPS IP address AND a CNAME to:

    Host: subdomain
    Address: primaryDomain

    I decided to add BOTH the A records AND the CNAME because there seemed to be some confusion about which one to use in a lot of the comments. I’m not sure if that’s causing a problem.

    I know that my original question was around the trunk files, but if trunk files are not the issue, and anyone has any other ideas on what I’ve missed, please feel free to fire away.

    thanks!

Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter beyonddomaining

    (@beyonddomaining)

    I was just told by Otto that:

    No, the regular version has been updated to work. The steps for installation are the same.

    So, this topic is resolved.

    My issue right now is that when I go to one of my ‘network sites’ using the ‘network site’ domain name, I end up at a URL that looks like this:

    https://domainname.com/cgi-sys/defaultwebpage.cgi

    with a message that says this: Default Website Page: If you feel you have reached this page in error, please contact the web site owner:

    Did you fix this part?

    Thread Starter beyonddomaining

    (@beyonddomaining)

    I have not fixed that part. That’s what I’m wrangling over right now.

    I sincerely appreciate your concern though.

    I’m about to call my web host (HostGator) and ask them a few questions about what’s going on, and then I’m going to start a new thread to pose this issue as the question.

    Thanks!

    Thread Starter beyonddomaining

    (@beyonddomaining)

    I got it figured out (sort of) after calling HostGator.

    Here’s the aftermath – hopefully it helps anyone else out there struggling like I was.

    I use a VPS at HostGator and everything was working perfecting using wildcard subdomains, but then when I switched over to “Primary Domain” using domain names I would get these Default Web Site Pages like this:

    https://domainname.com/cgi-sys/defaultwebpage.cgi

    The Domain Mapping plugin was working just fine.

    I figured it had something to do with the settings at my Registrar (Moniker) for the A Name vs. C Name vs. Parked Domain mapping options.

    So set up three different ‘sites’ on subdomains in WordPress MU and configured each three differently as tests at my registar like so: (1) to use A Name pointing to my primary IP and (2) to use C Name pointing to the main domain name for my hosting account (which is also the main domain name for the WP MU install and (3) pointing to the Private Name Servers I set up for my VPS (ns1.myname.com, ns2.myname.com), which I would then like to add as Parked Domains in my CPanel.

    None of them worked. They all brought me to this error page:

    https://domainname.com/cgi-sys/defaultwebpage.cgi

    So I called hostgator and what they suggested was to change the primary IP address in my account to the next one in line in WHM from Account Functions -> Change Site’s IP Address

    So say, they gave me my primary IP address was 189.83.31.32 (this is a bogus IP), if I went into the Account Functions -> Change Site’s IP Address, it allowed me to select the next IP address in line which was 189.83.31.33

    Then I had to go back to Moniker (my registrar) and update the A Records to point to the new IP address.

    That worked!

    I have combed through all sorts of help pages and forums, etc and never saw this mentioned, so hopefully it helps someone out there.

    The final question I have, if anyone would like to chime in, is that I would prefer to use a C NAME record to point to my site. This is because say I ever need to move to a new server or change IP address or something like that, i don’t want to have to go back and update the A Records for hundreds of sites.

    So I have left the domain name that is set to use the C Name mapping at Moniker as is. I’m keeping my fingers crossed that after a few hours, the C Name mapping will start to point to the new IP address on its own and begin working and then I can just go back and start using C Name records for everything.

    In the mean time though, the A Records seem to have worked for now.

    ok, regarding the https://domainname.com/cgi-sys/defaultwebpage.cgi

    I had the same issue. Dashboards would show, blog would not. I ended up clearing out the .htaccess file, uploading it and clearing browser cache and cookies. All sites are up.

    Found the solution via this forum post.
    https://forums.cpanel.net/f5/domain-redirecting-cgi-sys-defaultwebpage-cgi-139597-p5.html#post796062

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘[Plugin: WordPress MU Domain Mapping] Do we still need to use the Trunk Version?’ is closed to new replies.