Option to force HTTPS on custom domains

[zyumbik]

According to the topic and response below, you cannot force HTTPS server-side on custom domains on Glitch:

Force HTTPS on project URL

Ah yes, I misinterpreted what you were trying to do; I didn’t read the backscroll carefully enough, sorry! Yes, you are correct, that workaround won’t handle custom domains due to the way X-Forwarded-Proto gets filled in those situations. I don’t know of a way to handle it with custom domains off-hand.

As said in the other threads, it’s not possible to force it globally for all projects because it may result in some problems. Therefore, I suggest to make an option on Glitch to force HTTPS on custom domains.

This is a feature suggestion so don’t forget to vote for it if you think it would be useful.

[advaith]

You can use Cloudflare to force https.

[zyumbik]

Thanks for the suggestion! I just did that. However, I think it would be cool to have it as an option without leaving Glitch. This option is available on fly.io which is used by Glitch to serve custom domains, so I believe it shouldn’t be too hard to implement.

[charliea21]

If your using fly.io them under your “site” go to middlewere and select HTTPS (something like that, I’m on mobile so I can’t check).

[zyumbik]

Thanks @charliea21, your tutorial helped me immensely!

[Tutorial] Get your Glitch project on a domain!

Hey there! Many Glitch users probably wan’t their Glitch project on a custom domain. That’s why I’ve made this tutorial for you to use! Note: this tutorial is long, but it does have pictures! Step 1: Setup your glitch project You obviously need a Glitch project to work with, so first go ahead and create one. But wait… You aren’t going to get away with just making an sort of Glitch project. You need to make a Hello Express project. We’re nearly done with step 1 but next is security…

[charliea21]

No problem. (I had completely forgotten about that tutorial e.e)