D4. HTTPS and SSL
What this page helps you do
Understand the final step that gets your site onto https://.
Why it matters
Without HTTPS, browsers warn users and some app features break.
You should already have
- a domain that points to the app
Skip this page if
- the domain already loads over HTTPS without warnings
What to do
- confirm the hosting provider or server has a valid certificate path
- test the root domain and any subdomain variants
- fix redirect loops or certificate mismatch errors
Recommended default
Use the hosting provider or Cloudflare’s normal HTTPS flow unless you already know you need something custom.
Common mistakes
- testing only one subdomain
- enabling HTTPS in one layer but not the other
- ignoring redirect loops until launch day
Next step
Go to R8. Launch checklist.
Related pages
Advanced notes
TODO for contributors: add a plain-English explanation of full versus flexible SSL modes for builders using Cloudflare in front of a VPS.