DNS timing out

[forest narwhal]

I have entered the IP of my server to Cloudflare, but it is not working. I am just getting a timed out error.

I am able to connect directly to the IP.

[knotty pawn]

DNS is timing out? What's the exact error? (the exact url you get the error on, if you can share it, would be helpful as well)

[forest narwhal]

The code is 522, and the URL is https://fts-new.pixellicio.us/. Going to just make it fts.... later but that'll be swapped out when I figure this all out

Just disabled the Cloudflare proxy and http:// traffic is working, but https is giving the timed out error

[knotty pawn]

What's your ssl/tls encryption mode? In the Cloudflare dashboard, in your website, SSL/TLS -> Overview

[forest narwhal]

It's set to Flexible right now

[knotty pawn]

Flexible is insecure, you really want that to be Full (Strict), and then to configure your origin server to also work with https://. You can use Cloudflare Origin Certs ( https://developers.cloudflare.com/ssl/origin-configuration/origin-ca/) if need a certificate & you plan on always having the website proxied, up to 15 years expiry and trusted by CF Proxy

[forest narwhal]

going to install that right now, hold on

added it to my site and i'm getting a not secure warning

wait

hold on sorry i was going directly to the ip

yeah same issue

[knotty pawn]

it has to be proxied

[forest narwhal]

do i want to set it to strict rn too

[knotty pawn]

you should yea, only Full (Strict) is secure

[forest narwhal]

thanks so much, it's fully working

took me two days to figure this out

[quaint verge]

May I ask why flexible is insecure? It only means traffic from the cloudflare proxy to your server (and vice versa) wont be encrypted right?

[knotty pawn]

Insecure for the same reason why http:// is insecure and why browsers warn you about it. Even for static pages, someone in the middle could MITM the connection and inject ads/phising stuff/etc. Worse, you're lying to your visitors by making the site look secure even though it's not

[quaint verge]

But that could only happen in the connection from the cloudflare proxy to your server right?

[knotty pawn]

Yes, which is still half of the request (except for cached assets)

[quaint verge]

Mhm, that’s true

[tame birch]

Hello!

[quaint verge]

I can def see it being better

[quaint verge]

Hi

[tame birch]

I see you have gotten a error 522 on cloudflare! The most common reason why is because of slow internet / incorrect dns settings

[quaint verge]

@tame birch he made it work

[tame birch]

oh

[quaint verge]

Also you got a cool profile effect

[tame birch]

oh wait this is the wrong server

[quaint verge]

Lmao

[tame birch]

LOL MY MIND WENT TO THE WRONG SERVER AND STARTED HANDING HELP THREADS

I THOUGHT THIS WAS ANOTHER SERVER

[knotty pawn]

In a perfect world, flexible wouldn't exist, it's more of a relic of the past. Browsers enforce and default to https for a reason, if the browser sees the connection is secure the implication is end to end. Espec when it's really not that hard to get https set up, CF gives you origin certs that last for up to 15 years for free

[quaint verge]

Yeah that’s true