Refresh GitHub Pages HTTPS certificate for react.luau.page
Nobody has claimed this yet.
- Dominant language
- Luau
- Stars
- 569
- Forks
- 25
- PR merge metrics
- No merged PRs in 30d
Description
Hi! We recently moved luau.page DNS from Cloudflare to Porkbun.
Cloudflare used to terminate TLS at the edge. Porkbun is DNS-only, so GitHub Pages now needs to serve a certificate that includes this custom domain directly:
react.luau.page
Some GitHub Pages sites may temporarily serve the default *.github.io certificate until GitHub refreshes the custom-domain HTTPS certificate.
Could you open Settings -> Pages for this repository? That was enough to refresh the cert for luau.page. If it stays stuck, GitHub troubleshooting docs recommend removing and re-adding the custom domain to restart HTTPS provisioning.
You can also trigger/check the GitHub Pages DNS health check with:
gh api repos/jsdotlua/react-lua/pages/health
No code change should be needed; this is just a GitHub Pages settings/certificate refresh after the DNS provider change.
Thanks, and sorry for the migration noise.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Open this repository's Settings → Pages and inspect the custom-domain HTTPS status for react.luau.page. Run gh api repos/jsdotlua/react-lua/pages/health to check DNS and Pages health, using GitHub's Pages troubleshooting guidance if provisioning remains stuck. Done means the custom domain serves its refreshed HTTPS certificate.
Written by the indexing model from the issue text.
Assessment
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 72/100