Here is the scenario.
At this point, all subdomains should be covered by SSLby Let’s Encrypt Wildcard certificates.
After they finish building their website they have the option to map their domain to their subdomain via a configuration form in Wordpress (See screenshot) . After setting that, their website is then available at clientsite.com. Internally, Wordpress Multisite handles this - no need to configure Apache vhost files.
Ideally as soon as they make the change, their website should be immediately covered by SSL.
Is this possible to configure it this way? Would the wildcard certificate actually cover the mapped exampleclientsite.com as well?
If this is possible, how can I set this up?
If this is not possible, and I will have to go into the server to create a certificate for each mapped client domain, what’s the best way to do that?
Not long ago, I wrote this post, before I knew really what was going on, and it used the Apache approach. Now that I’ve learned a bit more, I’m wondering if the webroot approach would be best. If that’s the case, after I setup wildcard support, when a client is ready to map their domain to their sub domain and I have to manually go in and do it, can I use the webroot method even if all domains point back to the same root?
(The LE Documentation for webroot states " … potentially in a different domain." Sounds like webroot would be ideal for this?)
Typical in a wordpress multisite setup, all websites share the same base file structure. The site is installed at /var/www/html. Assets for each network site are stored at /var/www/html/wp-content/uploads/sites/site[1,2,3,etc] but these are only image files, mostly.
Our company consults on installing mutisite networks for clients. I’m endeavoring to put together a guide and share it with the community. I think a lot of people are going to want to have this same setup, so any help is understand the steps is greatly appreciated.