Domain - Enable Full (Strict) SSL with Cloudflare
Posted by elliotjj in websites.
I currently have my custom domain working with my WispByte server through Cloudflare using a proxied DNS record and an Origin Rule to route traffic to my application's port. The setup works, but I currently have to use Cloudflare's Flexible SSL mode. This means the visitor Cloudflare connection uses HTTPS, but the Cloudflare WispByte origin connection is HTTP. Is there any way for me to enable HTTPS/TLS on the WispByte origin so I can switch Cloudflare to Full (Strict)? Everything is already working through the custom domain I'm specifically looking to secure the connection between Cloudflare and the WispByte server.
Replies
tirito
you can't have HTTPS on TCP port alone, try using a free subdomain and then use CNAME/url rewrite rule to use HTTPS with strict mode
elliotjj
I tried setting my proxied terachat.org record as a CNAME to my WispByte subdomain, but Cloudflare returns Error 1014 (CNAME Cross User Banned), presumably because the WispByte subdomain is proxied through a different Cloudflare account. What URL rewrite/rule configuration would you recommend to avoid this?
tirito
after some testing, i don't think you can really do hostname rewrite if you have cloudflare free plan, so you will probably have to stick to HTTP for now or wait for custom domains to be released as a feature