i have a trellis / bedrock multisite installation, the 3 sites use letsencrypt on staging but on production they all have their own ssl certificate. in the wordpress sites file for production there seems to be no way of adding a separate setting for each site, any ideas how i get around this? thanks
I assume your multisite is using subdomains or domain mapping, because subdirectories shouldn’t need multiple certs.
I’ve had it on my radar to revamp things in Trellis so a site’s given
site_hosts could each specify different ssl certs/keys, providers, etc., but there is no such built-in functionality at present. I believe you would need to get your certs on the server and perhaps try a child template modifying the
https block, perhaps mapping each
$http_host to its appropriate cert/key. There could be many approaches.
However, it sounds like you have it working with Let’s Encrypt on staging. Is there some reason you don’t want to use Let’s Encrypt on production?
wordpress_sites: example.com: site_hosts: - canonical: aaa.example.com - canonical: bbb.example.com - canonical: mapped-domain.com multisite: enabled: true subdomains: true cron: false ssl: enabled: true provider: letsencrypt
Something like the example above would probably work.
thanks, we can’t use lets encrypt on production, we have premium certificates for 3 production sites on the multisite network. these certs need to be used. im struggling to apply ssl certs for particular sites, templates don’t seem to be site-specific. it would be great to apply ssl to each site individually in the trellis config
i can’t get your solution to work. do you mean overwrite the highlighted block in wordpress-site.conf.j2 replacing the variables? this would affect staging as well as production would it not? the company is close to scrapping trellis because of this limitation. I really don’t want this to happen and I’m desperately trying to find a solution that works and doesn’t add much work when upgrading trellis, any help would be much appreciated, thanks