bzerkmultimedia

UPDATE: For those who encounter similar problems, I have figured out what was causing my issue. TL;DR: uninstall and reinstall. That’s right, the oldest fix in the book.

Wordpress Multisite handles domain mapping by routing incoming calls to your ip through the primary domain on your hosting account. I never could find exactly where that code is located, but in my case the issue was that when I added a Subject Alternative Name to my UCC SSL (which had been installed by GoDaddy), the certificate was validated and reissued. At some point during this process the auto installer must have uninstalled the certs on the sites listed on my hosting and reinstalled them. GoDaddy marks the first domain installed as primary and apparently doesn’t check to make sure that the previous primary domain is given preference. A new domain was marked primary, which meant that all incoming calls to my ip were sent there instead of to my multisite installation.

The fix for this was simple: uninstall the sites in your SSL management on your hosting panel and reinstall them in the proper order, primary first. Note that on my GoDaddy cPanel, there was an option to “Make Primary” beside each site besides the primary. This option did nothing. Only reinstalling could change the primary.

• This reply was modified 5 years, 6 months ago by bzerkmultimedia.

And for further context, here’s a subfolder site (one of my older ones) which uses the same UCC SSL Certificate as the other sites. It works, supporting the idea that the problem is somewhere in the network’s https requests.

https://www.ssllabs.com/ssltest/analyze.html?d=ebenezerbeaumont.org

Thanks for your replies.

I’m aware that a network needs to use either subdomains or subdirectories. My network uses subdomains. The subfolders I mentioned are buried elsewhere on the server and have no relation to the network other than being on the same hosting account. It has worked for years in this configuration. Is there any reason it should suddenly stop?

Also, I can see how it might be confusing that cajunheritagefest has a revoked certificate. I can put it back on the cert if necessary so it’s easy to tell that when you go to https://downtownbeaumont.org it redirects to https://cajunheritagefest.com for no immediately discernible reason. Other sites on my network that attempt to use https do the same. Sites on my network that do not use https ( example: https://setxac.org/ ) work fine. It isn’t that the entire network isn’t working, it’s that either the network or some other step in the request is mishandling https requests (as far as I can tell).

Also also, because I’m out of my depth here, if your above replies are directly related to the solution of my problem you’ll have to explain it like I’m 5.

Don’t know if this has already been addressed in the replies, but anyone simply copying and pasting the referenced define function may find that it does not work. That is because this:

define( ‘COOKIE_DOMAIN’, $_SERVER[ ‘HTTP_HOST’ ] );

is not the same as this:

define( 'COOKIE_DOMAIN', $_SERVER[ 'HTTP_HOST' ] );

Check your single quote operators and make sure they’re the right ones. Copy/pasting the second line above may work for you.

• This reply was modified 7 years, 9 months ago by bzerkmultimedia.