Some of the providers like elasticemail.com rewriting email content links.
Example. elasticemail requires tracking CNAME to be configured while verifying/adding sending domain also don’t allow verifying sub domains
as discourse install didn’t install cert on tracking.domain.com leaving an insecure message on browser when we set force ssl setting.
As Discourse LetsEncrypt module will install certs on configured domain, Is there any way that installing certs on tracking domain
This is not a multisite.
Also LetsEncrypt is going to issue wildcard ssl in a week.(ETA: February 27, 2018 from LetsEncrypt forums) incorporating that to letsencrypt module is good choice to avoid these instances
There is nothing wrong with discourse. This is because of third party email service provider tracking smtp emails. but, is there any way in app.yml or ssl template for installing LetsEncrypt ssls on other sub domains? Please let me know.
I have seen some setup for multi-site with after ssl hooks. not sure if this works with single install.
What? Of course not. You don’t run the tracking domain, therefore you can’t install certs on it. Tell your e-mail provider to get off their chunk and setup HTTPS.