You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Issue: Unable to make the blog accessible at the apex domain and www due to the SSL certificate. A CNAME record at the DNS level doesn't cut it.
Suggestion: Make it possible to add both the apex domain and www in the custom domain settings and supporting SSL certificates with SAN. I believe it can be done with Let's encrypt
Standard Notes is really onto something with the Listed blogging platform, would be great to add this feature so users can use their apex domain with www or other subdomain.
I currently made it accessible at blog.os3.xyz and it frees up having something else at the apex, but in the future, especially as the platform improves even further, ill move it up.
Thanks for considering it
The text was updated successfully, but these errors were encountered:
neonwhisper
changed the title
Support for Subject Alternative Names for the SSL certificate
Support SSL certificate with Subject Alternative Names
Dec 9, 2021
What I've done in the meantime is run a webserver at www (with a valid cert) that just redirects everything to the apex. It would be very nice not having to do that, though.
Issue: Unable to make the blog accessible at the apex domain and www due to the SSL certificate. A CNAME record at the DNS level doesn't cut it.
Suggestion: Make it possible to add both the apex domain and www in the custom domain settings and supporting SSL certificates with SAN. I believe it can be done with Let's encrypt
Standard Notes is really onto something with the Listed blogging platform, would be great to add this feature so users can use their apex domain with www or other subdomain.
I currently made it accessible at blog.os3.xyz and it frees up having something else at the apex, but in the future, especially as the platform improves even further, ill move it up.
Thanks for considering it
The text was updated successfully, but these errors were encountered: