{"action":"created","issue":{"url":"https://api.github.com/repos/webprofusion/Certify/issues/3","repository_url":"https://api.github.com/repos/webprofusion/Certify","labels_url":"https://api.github.com/repos/webprofusion/Certify/issues/3/labels{/name}","comments_url":"https://api.github.com/repos/webprofusion/Certify/issues/3/comments","events_url":"https://api.github.com/repos/webprofusion/Certify/issues/3/events","html_url":"https://github.com/webprofusion/Certify/issues/3","id":147041268,"number":3,"title":"Support for www and non-www domain?","user":{"login":"RickStrahl","id":1374013,"avatar_url":"https://avatars.githubusercontent.com/u/1374013?v=3","gravatar_id":"","url":"https://api.github.com/users/RickStrahl","html_url":"https://github.com/RickStrahl","followers_url":"https://api.github.com/users/RickStrahl/followers","following_url":"https://api.github.com/users/RickStrahl/following{/other_user}","gists_url":"https://api.github.com/users/RickStrahl/gists{/gist_id}","starred_url":"https://api.github.com/users/RickStrahl/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/RickStrahl/subscriptions","organizations_url":"https://api.github.com/users/RickStrahl/orgs","repos_url":"https://api.github.com/users/RickStrahl/repos","events_url":"https://api.github.com/users/RickStrahl/events{/privacy}","received_events_url":"https://api.github.com/users/RickStrahl/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2016-04-08T21:15:18Z","updated_at":"2016-04-10T21:35:37Z","closed_at":null,"body":"When creating a certificate for www.site.com the certificate created automatically adds the same certificate to the base domain (site.com), but the certificate doesn't validate in the browser. The only way to get this to work currently is to create a second certificate for the base domain.\r\n\r\nLooks like Certify does support this functionality via whitelisting the base domain:\r\n\r\nhttps://community.letsencrypt.org/t/certificate-valid-for-non-www-and-www-as-well/3725\r\n\r\nNote sure if the Windows ACME library supports this at this point.\r\n\r\nAny chance this can be implemented since this is a pretty common use case and if not at least change the code so the invalid certificate isn't auto-applied to the base domain."},"comment":{"url":"https://api.github.com/repos/webprofusion/Certify/issues/comments/208077530","html_url":"https://github.com/webprofusion/Certify/issues/3#issuecomment-208077530","issue_url":"https://api.github.com/repos/webprofusion/Certify/issues/3","id":208077530,"user":{"login":"RickStrahl","id":1374013,"avatar_url":"https://avatars.githubusercontent.com/u/1374013?v=3","gravatar_id":"","url":"https://api.github.com/users/RickStrahl","html_url":"https://github.com/RickStrahl","followers_url":"https://api.github.com/users/RickStrahl/followers","following_url":"https://api.github.com/users/RickStrahl/following{/other_user}","gists_url":"https://api.github.com/users/RickStrahl/gists{/gist_id}","starred_url":"https://api.github.com/users/RickStrahl/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/RickStrahl/subscriptions","organizations_url":"https://api.github.com/users/RickStrahl/orgs","repos_url":"https://api.github.com/users/RickStrahl/repos","events_url":"https://api.github.com/users/RickStrahl/events{/privacy}","received_events_url":"https://api.github.com/users/RickStrahl/received_events","type":"User","site_admin":false},"created_at":"2016-04-10T21:35:37Z","updated_at":"2016-04-10T21:35:37Z","body":"FWIW, I can create two separate certs one for www. and one for the non-www binding and that works. But that adds a bit of overhead in managing the connection.\r\n\r\nSo are you saying that it's possible to do this with ACME but not with Certify (currently)? \r\n\r\nNormally when you register a domain and you register for www. you automatically get the non-www version of the cert as well. I think the UI for that would be simple enough - a checkbox for base domain would do the trick (enabled only if you're specifically targeting a subdomain).\r\n\r\nI'd help but frankly I don't know enough about the details of the cert process - I'm more like an end user who's excited about being able to more easily automate the certificate management and run all of my sites under SSL."}}