Since the additional domains don’t have their own vhost config on the server, you won’t be able to use Certbot to issue certificates for them the usual way. You have two options:
1) Include all your domains in one Subject Alternate Name or SAN (aka multi-domain) certificate. The exact Certbot command will depend on your platform, but adding the separate domains will be something like this:
certbot -d domain1.com -d domain2.com -d domain3.com
2) If, for whatever reason, you’re unable to use the SAN certificate option, you can use DNS authentication to request individual certificates for your additional multi-site domains.
Please invest a little time to go through the Certbot documentation. And if you still have a problem with this, the LetsEncrypt forum might be the ideal place to get the best support, as this problem is not really specific to WordPress.
Good luck!
I really like the answer given by @gappiah I learn something everytime I read his posts but sometimes you just need a good quick fix until you get to the bottom of the problem…
I like using Cloudflare… I then make use of their certs to cover everything from the origin server forward under SSL. Do remember that anyone reaching your origin server or anything being sent back to your origin server is ‘in the clear’ and isn’t protected by SSL.
Another thing is… are you using your ‘www’ as a separate website?
Most people just Cname the ‘www’ to the root domain and assign the site to answer as the root domain. If your ‘www’ is a separate site though that sometimes confuses others and makes things break when someone erroneously refers a user to your root domain when they are ‘thinking’ about something they saw on your ‘www’ domain. For that reason alone I don’t recommend having ‘www’ as a subsite.
Traditionally, ‘www’ was considered a ‘well-known service’ much like a mail server or other type of server found on the Internet.
Hi,
Thanks for your reply.
I tried this certbot -d website1.com -d website2.com
and got this: https://i.imgur.com/pswXFia.png
@jnashhawkins
For that reason alone I don’t recommend having ‘www’ as a subsite.
so you’re saying for website2.com I should delete the A record www host on Namecheap and only leave the A record @ host?
@worldwade
I’m not saying your records are wrong without having answers to my question about your intentions of using the ‘www’ or looking at your sites and DNS records to see your usage. I only have one domain to work with from you so I’m limited in what I see here.
When I request your site I see the broken front page…
When I add ‘www’ to your site I see what appears to be the same broken front page but I can’t be sure that is your intention.
Sorry I don’t understand what you mean by intention.
I just want website2.com to point to website1.com/test
.
