jamesfredley opened a new issue, #14731: URL: https://github.com/apache/grails-core/issues/14731
### Issue description This will simplify the Grails.org domain and DNS move to ASF. Most of the ~43TB/month in bandwidth comes from documentation. async.grails.org. 1 IN CNAME grails.github.io. ; cf_tags=cf-proxied:true docs.grails.org. 1 IN CNAME grails.github.io. ; cf_tags=cf-proxied:true gorm.grails.org. 1 IN CNAME grails.github.io. ; cf_tags=cf-proxied:true grails.org. 1 IN CNAME grails.github.io. ; cf_tags=cf-proxied:true gsp.grails.org. 1 IN CNAME grails.github.io. ; cf_tags=cf-proxied:true guides.grails.org. 1 IN CNAME grails.github.io. ; cf_tags=cf-proxied:true start.grails.org. 1 IN CNAME grails.github.io. ; cf_tags=cf-proxied:true slack-signup.grails.org. 1 IN CNAME grails.github.io. ; cf_tags=cf-proxied:true testing.grails.org. 1 IN CNAME grails.github.io. ; cf_tags=cf-proxied:true views.grails.org. 1 IN CNAME grails.github.io. ; cf_tags=cf-proxied:true Example: https://github.com/grails-guides/grails-guides-template/settings/pages Remove proxy in cloudflare, then enable Enforce HTTPS in GitHub  GitHub Pages requires direct DNS resolution to its servers to issue and renew SSL certificates via Let's Encrypt. When Cloudflare's proxy is enabled, DNS queries resolve to Cloudflare's IPs instead of GitHub's, causing GitHub to fail the DNS check and display the error: "Enforce HTTPS — Unavailable for your site because your domain is not properly configured to support HTTPS." Cloudflare's proxy also complicates certificate renewal, as GitHub cannot access the necessary Let's Encrypt challenge endpoints (e.g., /.well-known/acme-challenge/). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@grails.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
