I can't open the website when I enable the CF proxied DNS records

Website, Application, Performance DNS & Network
1

What is the name of the domain?

doulaiwan.org

What is the issue you’re encountering

Can’t open the webpage after I enable the CF proxied DNS records

What steps have you taken to resolve the issue?

I have tried change the SSL mode to Flexible and Strict (Full), the issues are same.
After I change the DNS records to DNS only, I can access the webpage, but it warns that the 15 years CF SSL on the server is not valid.

What feature, service or problem is this related to?

DNS records

2

That should never be changed away from Full Strict, as you disable encryption otherwise. Always use Full Strict.

Your site currently runs into a timeout, you need to fix this on your server and Community Tip - Fixing Error 522: Connection timed out has more information.

3

Thanks. I think the problem exists in CF proxy. When I proxy the DNS record, I can’t connect to the website, yes, it seems to be timeout. But I can reach it by IP address.

4

No, this is a server issue. You need to make sure the addresses at IP Ranges are not blocked.

5

This IP address is pointed to my router, and port forward to my NAS. I have not config any IP filter on the router and NAS

6

Then your port forwarding will not be correct or something else prevents Cloudflare from connecting.

You can certainly pause Cloudflare, but should it be an issue with your server, you’ll owe me a coffee :wink:

7

Haha, Coffee is no problem!
That’s exatly my scenario. It works when I disable the CF proxy on DNS record except I need find the other SSL certification to replace that 15 years one.
I doubt that the CF IP is blocked at China

8

Well, you haven’t paused Cloudflare yet.

9

hmmm, you found it…
I just pause the CF as you guided. it is as I imagine. the CF 15y SSL can’t work.

2024-07-05_14-10-43-chrome
2024-07-05_14-10-43-chrome933×492 53.3 KB

10

Yeah, the certificate is not the issue here. As I mentioned, your server is not reachable → sitemeer.com/#b1824c1056ebf484002889a7a48b77fdcd7f042a

I take my coffee black :wink:

11

you have not added the port. 80 is not open yet.
![2024-07-05_14-15-51-msedge|690x188](upload://xPmflkJepuimRv5W6RjlogDNiCd.
I agree that the server connection has some issue.
But now we skipped the CF, that CF origin SSL certification can’t work with clietn directly. It should be used between CF and my server.

12

2024-07-05_14-15-51-msedge
2024-07-05_14-15-51-msedge1389×380 19.3 KB

13

I don’t need to specify a port as 443 is used by default. But are you saying that you are using port 5001? You did not say that.

14

yes, port forwarding. I use the other than 80/443 to connect, is this issue?

15

And you configured the respective rule on Cloudflare? Otherwise that port will never work. That’s a detail you can’t just leave out. I still take my coffee black :wink:

1 Like
16

Never noticed this! I will look into it! Thanks! :hamburger: :coffee:

17

Sorry, It looks like I lost in the docs. can you send me the doc link about that? :smile:

18
1 Like
19

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.