Does cloudflare handle non http/https ports properly?

I have an EC2 hosting a blog. It also runs a bunch of other services on some random ports. I want to enable CDN for my blog, because it loads very slowly for people halfway across the globe. I wanted to know if the other services will keep working after enabling cloudflare CDN. I had to change the nameserver entries to those of cloudflare. Now I’m guessing that if someone in another country tries to connect to, the cloudflare nameserver will resolve to a cloudflare cdn, which will reject communication at port 460. Will the network handle this case properly?

One workaround I can think of is to allocate another domain and use that for my blog. Is there another alternative?

Use different hostnames for the http or non http services and only proxy hosts which use the supported proxy ports / protocols.

1 Like

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