Latest Announcemnent
New thread
Status
Not open for further replies.
Hi,

We're going to dump sites that attempt to use us solely for storage and bandwidth, unfortunately. It wouldn't be an issue if the sites were serving real traffic.
 
There is an annoying problem with cloudflare.

They set a timed page refresh.

Say im in the ACP of my site and doing something that will run a long mysql query (eg. dumping 5k posts) the page will refresh before its finished.

This stops all the queries being run, update posts, topics, users etc so its a problem.

The site only runs from the domain name as well, so cant be used from a direct A record url.
 
I use it for the caching :))
If they added paypal I would pay for it.

The service isnt to hide your IP You can find any sites ip if you really want from looking at DNS records. And they dont say they migrate DDOS ;)
 
Gavo said:
There is an annoying problem with cloudflare.

They set a timed page refresh.

Say im in the ACP of my site and doing something that will run a long mysql query (eg. dumping 5k posts) the page will refresh before its finished.

This stops all the queries being run, update posts, topics, users etc so its a problem.

The site only runs from the domain name as well, so cant be used from a direct A record url.
Click to expand...

You can use
Code: 
[COLOR=#000000][COLOR=#0000BB]ignore_user_abort[/COLOR][COLOR=#007700]([/COLOR][COLOR=#0000BB]true[/COLOR][COLOR=#007700]);[/COLOR][/COLOR]
so it will keep running while the browser is aborted.
 
I know I could add that but sometimes i have a clean up on the board and run long queries one after the other for an hour or so, I want to make sure the last query finishes before i start another or I will flood/lock mysql (without having to check server status etc.) :P


Other people must have this problem, so cloudflare should increase the time to page refresh.
 
Hi Gavo,

You could actually create subdomains for your admincp and mysql & then mark it as something we don't touch in your DNS settings (create subdomains->CloudFlare->Settings->DNS settings->Add subdomain(s)->make sure cloud is grey.

If it was url based, however, we do have a feature called Page Rules (beta) that could possibly assist with this as well.
 
Gavo said:
I know I could add that but sometimes i have a clean up on the board and run long queries one after the other for an hour or so, I want to make sure the last query finishes before i start another or I will flood/lock mysql (without having to check server status etc.) :P


Other people must have this problem, so cloudflare should increase the time to page refresh.
Click to expand...

well you as site/server admin you don't need to access site through CloudFlare reverse proxy. you can edit your hosts files and point your domain to your server real IP. and do maintenance :)

Highest Regards
Mohammed H
 
sanis said:
jase07, wtf are you talking? Have you ever tried it? I have had about 300 online users and my VPS was slowing down, after starting to use cloudflare I can even handle 500+ users without any problems. And page loading times are much more better.
Click to expand...

Loading times are better when they load because they keep pages in their cache.

I also have been on many sites using cloudfare and continually get can not load cache for that page. Click here to try and load live page....

Maybe your users just don't report it....
 
I use it..
but their routing is ASIA is suck, always route to US DC.
So, in load time still same as my server in US too.

Still waiting improvement for their ASIA routing as they had 3 DC in ASIA but none of them get hit from ASIA users.

Had reported it to CF and said forward it to their network department but I think it's general answer as when I search it in internet about this ASIA routing, it has been since along time ago until today no improvement.

I think their network technician should learn from other CDN company how to make correct routing :P

But I still use it as save b/w but I'm still neutral in here until they fix ASIA routing. =)
 
Hi,

"
Had reported it to CF and said forward it to their network department but I think it's general answer as when I search it in internet about this ASIA routing, it has been since along time ago until today no improvement."

It actually was forwarded to engineering to see if it can be fixed. Routing in Asia is a mess, which isn't entirely within our control, but we'll see if it is something that can be fixed through a provider in Asia (this can take a little time). Generally speaking, a user in your area would likely be hitting either Singapore or possibly even Hong Kong & this does happen with most users in that area.
 
I added some proof at support ticket
all routing from SG go to HK instead SG DC.

Code: 
Tracing the route to cloudflare.com (173.245.61.250)

  1 203.208.155.2 0 msec 4 msec 0 msec
  2 ge-0-1-2-0.sngc3-dr1.ix.singtel.com (203.208.172.117) 4 msec
    ge-4-0-0-0.sngc3-cr1.ix.singtel.com (203.208.172.153) 0 msec
    ge-1-1-4-0.sngc3-dr1.ix.singtel.com (203.208.172.169) 0 msec
  3 203.208.152.225 0 msec
    203.208.152.229 0 msec
    203.208.152.221 0 msec
  4 so-3-0-0-0.hkgcw-cr4.ix.singtel.com (203.208.172.182) [MPLS: Label 384560 Exp 0] 28 msec
    203.208.152.154 [MPLS: Label 387792 Exp 0] 33 msec
    203.208.151.253 [MPLS: Label 307744 Exp 0] 0 msec
  5 203.208.152.177 32 msec
    ge-4-0-9-0.hkgcw-cr4.ix.singtel.com (203.208.152.137) 28 msec
    203.208.152.177 32 msec
  6 203.208.153.193 32 msec 32 msec 32 msec
  7 203.208.186.98 32 msec
    203.208.153.193 32 msec 52 msec
  8 CDF-0005.asianetcom.net (203.192.178.6) 32 msec 32 msec 32 msec
  9 CDF-0005.asianetcom.net (203.192.178.6) 36 msec
    cloudflare.com (173.245.61.250) 33 msec 28 msec
sngc3-sr1
Code: 
Tracing the route to cloudflare.com (173.245.61.248)

  1 203.208.145.29 0 msec 0 msec 4 msec
  2 ge-1-1-8-0.sngtp-dr2.ix.singtel.com (203.208.152.65) 4 msec 4 msec 4 msec
  3 203.208.152.217 4 msec 4 msec 4 msec
  4 so-3-0-1-0.hkgcw-cr3.ix.singtel.com (203.208.151.82) 32 msec 40 msec 32 msec
  5 203.208.152.177 40 msec 52 msec 32 msec
  6 203.208.153.193 36 msec 48 msec 32 msec
  7 203.208.186.98 120 msec 204 msec 196 msec
  8 CDF-0002.gw1.hkg4.asianetcom.net (202.147.17.182) 36 msec 32 msec 36 msec
  9 cloudflare.com (173.245.61.248) 36 msec 36 msec 32 msec
sngtp-sr1
Code: 
  traceroute to cloudflare.com (173.245.61.248), 30 hops max, 40 byte packets
 1  202-150-221-169.rev.ne.com.sg (202.150.221.169)  0.290 ms  0.325 ms  0.372 ms
 2  s4-6-r10.cyberway.com.sg (203.117.6.209)  0.681 ms  0.710 ms  0.771 ms
 3  anutsi11.starhub.net.sg (203.118.3.163)  2.476 ms  2.465 ms  2.452 ms
 4  tenge4-2.br01.hkg15.pccwbtn.net (63.218.211.13)  34.358 ms  34.349 ms  34.402 ms
 5  anc.ge13-34.br01.hkg04.pccwbtn.net (63.218.1.222)  33.736 ms  33.726 ms  33.714 ms
 6  ge-4-0-0-0.cr4.hkg3.asianetcom.net (202.147.16.93)  34.337 ms  34.368 ms  34.322 ms
 7  te3-2.gw1.hkg4.asianetcom.net (202.147.16.198)  240.293 ms  226.074 ms  213.076 ms
 8  CDF-0005.asianetcom.net (203.192.178.6)  34.383 ms  34.400 ms  34.469 ms
 9  cf-173-245-61-248.cloudflare.com (173.245.61.248)  34.915 ms  34.859 ms  34.913 ms
 
Last edited:
Status
Not open for further replies.
Back
Top