Hi Adam, Thank you for your response. We took that SSL healthynycvending.com off for testing purposes; however, the owner of the site saw that it was getting the not secured warning and we had to put it back. We are maxed out with SSLs now until we can figure out how to redirect a non-www to www. We have taken the option off for our clients until we get this resolved. Any help on this would be much appreciated.

Thank you for your response. Will you please explain or give us an example of the last sentence in your response?: add another server config pointing to the same web root, then you can use up another 100 domains in a second certificate...

We are using subdomain directories for our users, unless they want to map their own domain over. We give them they option to purchase a SSL. The problem we are faced with is we would map the domain.com & www.domain.com to the SSL; however, we have used up all of our 100 SSLs with Let's Encrypt. With that said, we made a decision to eliminate one of the domain.com SSLs to cut the SSLs in half. We took out the domain.com; however, if the end user that types in the domain types: domain.com; Firefox and Safari precent that warning that you are on a un-secure page. I have tried using .htaccess to force a redirect, but was unsuccessful. I was wonder if you guys know of a work-around to force the www.domain.com redirect? I hope all that makes sense. Oh, here is one of the sites on the multisite: healthynycvending.com