Why does refreshing a page after a long wait get me cloudfare and not LQ?
LQ Suggestions & FeedbackDo you have a suggestion for this site or an idea that will make the site better? This forum is for you.
PLEASE READ THIS FORUM - Information and status updates will also be posted here.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Why does refreshing a page after a long wait get me cloudfare and not LQ?
I have noticed this a few times. I know cloudflare is hosting this site somehow but you usually don't see it. However, if I refresh an LQ page after a long wait (a couple of hours, say), my browser hangs on a cloudflare address.
It's getting worse. I've been trying repeatedly to answer a question by a newbie and cloudflare won't let me! My answer doesn't contain any code, just plain text.
I still can't give this poor user his answer! And so far no one else has done so either. He'll just have to do without. I think that's rather sad and defeats the purpose of the site.
I just tried doing it using links, which doesn't use javascript. I thought that might be a way to get around clownflare's idiocy. No luck! The question incidently is about LFS; this user believes that he can't get into chroot and I believe he actually is in chroot and suggested a couple of more reliable ways to test it.
I wonder if this has something to do with the ip address assigned to me today. Could it be on some kind of blacklist? It's 78.32.146.199 if that says anything to anyone.
I recently installed ublock. Could that be it, do you think? Anyone else had problems there?
PS: I tried again this morning and got the same result. This time round, I actually got some capchas to do (I hate those!) but then it again blanked out. Yet I can post to this thread and some in the general forum. I just can't post to that one. Fortunately business kid answered it so the guy hasn't been completely ignored but I would still like to add my .
PPS: I hope this problem doesn't extend to other technical threads. I come here to help people, to pay forward for all the times I was helped. If I'm not allowed to do that, I might as well stop coming.
The solution was not to give that particular questioner the answer I wanted to give. They got one from business_kid, but what I wanted to say (and business_kid didn't say) was that I believed the OP was indeed chrooted into LFS and hadn't tested for it correctly. For example, he'd used uname to identify his kernel but had imho misinterpreted the result. I suggested one or two tests he could do. But I wasn't allowed to post so he is none the wiser.
That saddens me. Just not posting is a solution of sorts but not one that does this site any credit.
Initially yes. But when I had done them, I just got a blank white page rather than being redirected to the post. Frankly I haven't got the energy to chase this up any further.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.