When you have a custom domain associated with Cloudflare there are settings to consider to make sure that both Cloudflare and Frame are working in partnership.
Below is a breakdown of the Cloudflare SSL modes and how it affects Frame.
Flexible. Traffic to Cloudflare is secured but traffic to Frame's servers are sent over port 80 (unsecured). Frame servers are designed to auto redirect to SSL (port 443) so a redirect loop will occur. See Cloudflare's documents regarding this issue.
Full. Cloudflare will respect the original request so if if the original request is unsecured (port 80) it will send an unsecured request to Frame servers and if the original request is secured (port 443) it will send a secured request to Frame. This flexibility of port 80 and port 443 allows Let's Encrypt to work on Frame's servers.
Full (strict). Cloudflare only allows secure requests over port 443. This is great once Let's Encrypt has generated an SSL Certificate on Frame's servers. However, if this is set prior to that then SSL generation will fail on Frame's servers.
Steps to Set Correct Information
Add A record pointing to 160.238.31.236
CNAME record for www pointing to *@sdachurch.org
Remove any AAAA records from your domain's DNS settings.
Set Cloudflare's SSL Certificate to Full. Once the SSL has been configured on Frame and you confirm the website loads, you can update Cloudflare's SSL Certificate to Full (strict).
Please make sure that the information is added and the SSL is working in Frame before adding the Full (strict) option in CloudFlare. If this is done before than the SSL Certificate may fail.