Well... You might want to use different certificates for different names.
Also, you don't need different virtualhosts, just one with a lot of aliases. I would use Caddy.
Well... You might want to use different certificates for different names.
Also, you don't need different virtualhosts, just one with a lot of aliases. I would use Caddy.
Got it. Now I understand Create the vhost in sites/available/ and then activate it. That's what I did. I think I just misunderstood originally.
I'll have to check out this Caddy you speak of. it look interesting at first glance for my type of setup
The OP can use a single virtualhost with many aliases if apache doesn't terminate SSL.
Because they were manually editing the certificate domains and onboarding/offloading domains on a regular basis, we suggested multiple virtualhosts - each for a single domain - so Certbot could automatically manage domain-specific SSL certificates.
Using Caddy or terminating SSL before Apache was the initial suggestion. The OP is familiar with Apache though.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.