Use cloudflare for a non-ssl site

[Costinr]

Hi,

I have an internal server that does not “know” SSL/https and I would like to access it from internet via Cloudflare https.

I have the domain pointing to my external IP, I have mapped 2087 external port (accepted by Cloudflare) to my local 35500 port and local server IP in router, and I’ve set SSL on “Flexible”

But I think I’m still missing something as I receive an error - SSL handshake failed.

Please help.

Thank you,

[Costinr]

To be more specific, I need this:

INTERNET-–(SSL)–-> Cloudflare —(NON-SSL)—> INTERNAL SERVER (xteve)

xteve does not “know” https/ssl

Thank you,

[Cyb3r-Jak3]

Checkout why you shouldn’t use flexible

Why you should choose Full Strict, and only Full Strict

Unencrypted & unverified connections Imagine you open Paypal and suddenly get that warning [image] Would you continue? Probably not. For decades leaders in IT security have advocated that people upgrade their sites from unencrypted HTTP to secure HTTPS. And for a reason, everything you send via an HTTP connection is sent in plain text and can be intercepted at any point between you and the server. Equally, you’d probably not proceed if you got such a warning, right? [image] That’s when th…

Your best bet is to have a reverse proxy on your server that can do SSL.

[Costinr]

Thank you Cyb3r-Jak3, but this is exactly what I hoped an I wanted to do: to use Cloudflare as a reverse proxy for my non-SSL server.

Is this possible?

[sdayman]

@Costinr

I have mapped 2087

Cloudflare expects to see HTTPS on 2087:

Network ports · Cloudflare Fundamentals docs

@Costinr

INTERNAL SERVER (xteve)

This sure sounds like a media server, which would be a violation of ToS 2.8:

Self-Serve Subscription Agreement

[Costinr]

Thank you sdayman, I didn’t know.

xteve in my scenario serves only picons via reverse proxy, but probably is safer not to use Cloudflare even for picons, in order to be compliant.