Admin
May 10, 2025, 9:31am
2
The issue you’re having is a consequence of a system change that was made last. It should make SSL for free subdomains better, but it has some unfortunately side effects.
I just wrote the announcement about this, including a workaround for the issue you’re having:
Limitations
The wildcard SSL certificate only protects direct subdomains of our domains, like example.ct.ws. It does not protect subdomains or subdomains, such as www.example.ct.ws or blog.example.ct.ws.
Due to an oversight in the rollout, all certificates for direct subdomains have now been disabled. However, this also results in all www subdomains no longer having any SSL. We are aware of the issue and are looking for a suitable solution.
In the mean time, if your website is on a www subdomain, you can change your website URL to the subdomain without www instead.
Please consult the documentation of your website software to see how you can change the URL of your website. Like these instructions for WordPress: Migrating WordPress – Advanced Administration Handbook | Developer.WordPress.org
4 Likes