Hi,
I'm building a site with multiple subdomains and after changing the model have issues with the redirect.
We have hosting using cpanel on godaddy.
The first installs were made by creating seperate wordpresses, subdomains and ssl certificates for each subdomain.
Now we're switching to wordpress multisite with a wildcard ssl. The wildcard ssl is just one level, it doesn't cover www.subdomain.domain
It's been a struggle to get several parts straight:
- get multisite working with subdomains
- force redirection of domain and all subdomains to https:// without using www. to prevent security alerts because of "missing" certificate
(I take it as a given that some clients will type "www.subdomain..." manually and I want to prevent the security alert for them.)
I've managed to get this working for new subdomains with these steps:
- force redirect to https without www in .httacces
- create alias for new subdomain in cpanel
- create new site in multisite
these way the only way I get a security alert before redirecting to https is if somebody types "https://www.subdomain..." and that doesn't seem very likely to me, so I don't care that much.)
The problem is with the older installs I want to switch to the new model. There are two types:
1. pages that have a own wordpress install, subdomain and ssl certificate and I'll have to move to the multisite.
2. pages that were created in multisite, but trying to figure out the process I created subdomains and ssl certificates for them.
At the moment I'm having a problem with the second group. Everything works fine, but I still get the "missing" certificate security alert for www.subdomain. As it works for new subdomains I figure it's some point of the old install I'll have to clean, but I don't know where.
And this brings me to the first group, where I'll have to clean up even more when I switch them to multisite.
So, where do subdomain installations leave traces I have to clean to make the new subdomain installation on the same subdomain work?
Thanks a lot
I'm building a site with multiple subdomains and after changing the model have issues with the redirect.
We have hosting using cpanel on godaddy.
The first installs were made by creating seperate wordpresses, subdomains and ssl certificates for each subdomain.
Now we're switching to wordpress multisite with a wildcard ssl. The wildcard ssl is just one level, it doesn't cover www.subdomain.domain
It's been a struggle to get several parts straight:
- get multisite working with subdomains
- force redirection of domain and all subdomains to https:// without using www. to prevent security alerts because of "missing" certificate
(I take it as a given that some clients will type "www.subdomain..." manually and I want to prevent the security alert for them.)
I've managed to get this working for new subdomains with these steps:
- force redirect to https without www in .httacces
- create alias for new subdomain in cpanel
- create new site in multisite
these way the only way I get a security alert before redirecting to https is if somebody types "https://www.subdomain..." and that doesn't seem very likely to me, so I don't care that much.)
The problem is with the older installs I want to switch to the new model. There are two types:
1. pages that have a own wordpress install, subdomain and ssl certificate and I'll have to move to the multisite.
2. pages that were created in multisite, but trying to figure out the process I created subdomains and ssl certificates for them.
At the moment I'm having a problem with the second group. Everything works fine, but I still get the "missing" certificate security alert for www.subdomain. As it works for new subdomains I figure it's some point of the old install I'll have to clean, but I don't know where.
And this brings me to the first group, where I'll have to clean up even more when I switch them to multisite.
So, where do subdomain installations leave traces I have to clean to make the new subdomain installation on the same subdomain work?
Thanks a lot