Hey @dreeves sorry you’re site is still having some trouble.
Here’s what I think is happening. www.molecall.com resolves (eventually) to the fly.io / shw.io servers, which are serving up an appropriate SSL certificate for www.molecall.com, so that all works as expected. However molecall.com itself, where the redirect to www.molecall.com takes place, is being served by a Namecheap server (based both on the results of a WHOIS lookup at https://whois.arin.net/rest/net/NET-192-64-112-0-1 and on the
X-Served-By: Namecheap URL Forward header returned in a
curl -IL http://molecall.com/ request) which doesn’t have an SSL cert for molecall.com (or at least isn’t responding on port 443). Therefore requests for https://molecall.com time out.
Swapping the CNAME record at www.molecall.com for an A record wouldn’t help; A records need to point to an IP address, and presumably if you pointed www.molecall.com to 126.96.36.199 (the ip where 1zdn9kj2hmfo4q3v.shw.io resides) then fly.io wouldn’t be able to resolve your custom domain to the right glitch.me project (I expect that they use the host header of the incoming request to determine which application to serve, but that’s largely a guess).
My suspicion is that you need to make some changes in your Namecheap forwarder configuration to have them serve a valid SSL cert for molecall.com if you want SSL to work at that address.
Hope that helps!