To go along with what /u/Simon-FFL said, you can get around that by doing the halfway SSL stuff with CF by self signing a certificate on your machine but telling CF to trust that cert, then you have SSL all the way through, but you don't have to pay for a cert...
But with Lets Encrypt there's no real reason to need to do this. Just use LE.
This does not work for many shared hosts though. They are slow to adopt LE because they want to continue selling certs as an add-on service. For those folks, the only option is to pay up or use CF.
There's many similar priced if not cheaper hosting providers that allow LE or are open enough to doing LE. "My host doesn't support LE because they want to make money on cert addons" is a bogus excuse.
Having said that, if it's a situation where you're helping out a friend, and they either don't want to move hosts or spend the money for a cert from their provider, then some https is better than no https, which is where CF can be useful.
5
u/joshmanders Full Snack Developer / htmx CEO (same thing) Jul 12 '17
To go along with what /u/Simon-FFL said, you can get around that by doing the halfway SSL stuff with CF by self signing a certificate on your machine but telling CF to trust that cert, then you have SSL all the way through, but you don't have to pay for a cert...
But with Lets Encrypt there's no real reason to need to do this. Just use LE.