This may be an issue due to newly adding my domain, however when using a custom domain I get a certificate error over HTTPS.
When checking the cert it states it has been provided to "33rdnorwich.co.uk" - which seems to be a different voice site.
Is there something in particular I need to do to get HTTPS working with a custom domain? If it helps any, I'm using Google Domains as my registrar.
This looks to have sorted itself overnight. Thank you!
As you've just discovered - when you add a domain name it does take a little while for Voice to be able to validate it and create an SSL certificate. Usually it happens in under an hour but it can depend on how long it takes the DNS settings to update (since we can't validate the domain until you update the DNS to prove it's a Voice site).
Interesting domain you've chosen - I've not seen the .community TLD in use before. Nice!
PS. that's https://killen.community/ for those people wondering what we're talking about!
Thanks for the feedback/update Joe! .community seems pretty new as a TLD, surprisingly haven't encountered any issues with it so far, and it very much reflects our site so it's great to have! (Pricier than a .com sadly, but that's to be expected with the new TLD's).
Awesome integration with SSL, I wasn't sure if I needed to do anything to get it working but the fact it automatically registered and applied overnight was really great. Thank you!
voice.community is available for "only" £4,944 - I think I'll pass on that!
voice.online is available for £1,500 which is still ridiculous but a bit less so.
(I'm not overly keen on the e-voice.org.uk domain - it seems a bit too clunky and old fashioned to me!)