Yeah.. if you go to
www.calgarypuck.com it is fine but not calgarypuck.com.
I use
Let's Encrypt for certs, and I can create a cert that would have both, except the DNS provider won't let me create the proper DNS challenge response records to do that.
I tried creating a calgarypuck.com only domain cert and that worked, but there must be some kind of forwarding going on since it gets stuck on
www.calgarypuck.com with a DNS error even if I go to calgarypuck.com.
I could change the website so it always uses
www.calgarypuck.com, but I hate fiddling with the Apache settings as I'm not very good with them and always seem to run into problems.
I will have to see if the DNS provider has an API and maybe I can do the challenge/response updates via that to satisfy Let's Encrypt's requirements.