On 27.10.2013 02:00, Andrew Bartlett wrote: > It's actually the opposite problem, the hostname is correct (this is a > XSS protection as I understand it), but the SSL cert is for the wrong > name. I've BCC'ed our admins, who I have already discussed the recent > cert change with. oops, overlooked this. I'm already about to fix this. Björn