It works now! Thank you so much for the help, everyone. It looks like Glitch / Fly.io caught up with the missing SSL cert on its own – I didn’t have to delete and re-add
molecall.com in the Glitch config.
So I believe my instructions above [now below] are correct and I’m now repeating them for two other domains…
And it worked instantly this time!
I’m now adding some edits and clarifications in the above [now below] instructions. I think it would make sense to incorporate them into the official instructions.
I believe the existing official instructions are great if you have a specific subdomain of your custom domain that you want to use. If not then you’ll surely want both the root domain and the www version to work and of course you’ll want it to work for both http and https. As far as I can tell, only those with a profound understanding of sysadminnery could immediately infer the instructions below from what’s currently in the official instructions. (I mean, I have a PhD in computer science and it was a pretty huge frustration for me to piece it all together!)
[moved again as I’ve learned new things and to keep it all as a single coherent set of step-by-step instructions! see new final response below.]
- Is it fragile to hardcode the IP address? Is there any way to avoid doing so?
- What if I’m morally opposed to non-encrypted websites and want the http version to actively redirect to the https version?
- Which should be the canonical version of the URL? (I hear it’s important for googly/SEO reasons to pick one and have all others redirect to it.)