The naming is causing confusion. So I'm going to 301 redirect fstat.gluster.org -> failurestat.gluster.org. And eventually phase out fstat.gluster.org.
So I went ahead and added the alias in DNS and on the proxy. I am not sure it is gonna work fine with our letsencrypt automation, I think that's a untested configuration.
Yeah, it throws up an error. I'm contemplating if it's worth changing it to be the default domain.
Yeah, we would have to force LE to renew the certificate. I did verify that it should work, but on first deployment only. I am gonna fix it manually.