Is something wrong with TOR connection or forum is awefully slow?

[AB de Royse777]

Is this only me or others as well facing this today. I am getting frustrated with the slow response from the server. It's always coming with this:
"The connection has timed out"

It's been few hours I am online but can not make the posts. I am trying to push the IPL 2020 Pool for the final time but it seems this connection thing, the slowness is ruining everything for me.

Forum is awfully slow or it's the TOR connection?

[hd49728]

Maybe it is from your Internet connection or from your node. I am writing with Tor browser.

[ranochigo]

Obvious question but have you tried changing your circuit? I've noticed that my connection can be quite slow at times. Changing the circuit a few times has always solved it.

[jackg]

My VPN was getting issues earlier about 12 hours ago but it seems to be alright now. Yesterday it was stuck loading a majority of the page and got stuck with a loading bar on 75% for a while.

[Pffrt]

I think it's either because of TOR or your internet connection. I am active for the last couple of hours, got not a single issue at all but I'm in chrome browser now because I'm in mobile now.

[Findingnemo]

There is no issue with the bitcointalk since I can surf with no issues for hours already so the issue is on the TOR side for sure.

Did some research on How to resolve the connection time out issues on regular websites then I came across this old reddit post

Because of the huge amount of lag associated with Tor, pipelining, i.e. sending http requests in batches, makes a lot of sense. Go to about:config and make the following changes:

Code:

network.http.keep-alive.timeout:600
network.http.max-persistent-connections-per-proxy:16
network.http.pipelining:true
network.http.pipelining.maxrequests:8
network.http.proxy.keep-alive:true
network.http.proxy.pipelining:true 

You should also disable prefetching. This is when the browser tries to predict what the user will click next. It is a waste of Tor bandwidth, and should be disabled by setting:

Code:

network.prefetch-next:false

[AB de Royse777]

I had no idea why yesterday I was having so much trouble but it seems today I am back of the track. The speed is as it suppose to be. I know TOR is not as good as regular browsers but it was the shittiest yesterday.

Because of the huge amount of lag associated with Tor, pipelining, i.e. sending http requests in batches, makes a lot of sense. Go to about:config and make the following changes:

Code:

network.http.keep-alive.timeout:600
network.http.max-persistent-connections-per-proxy:16
network.http.pipelining:true
network.http.pipelining.maxrequests:8
network.http.proxy.keep-alive:true
network.http.proxy.pipelining:true 

You should also disable prefetching. This is when the browser tries to predict what the user will click next. It is a waste of Tor bandwidth, and should be disabled by setting:

Code:

network.prefetch-next:false

Thanks bud for posting it. Maybe I will try next time when I face such issue again. I am not much expert, how do I find this about:config?

[Lucius]

I am not much expert, how do I find this about:config?

It should be quite simple - just type about:config in your browser address bar and click enter. I've changed some settings in Chrome and Firefox that way before, of course you have to be careful with such things so that you don't do more harm than good.

http://kb.mozillazine.org/About:config

[AB de Royse777]

It should be quite simple - just type about:config in your browser address bar and click enter. I've changed some settings in Chrome and Firefox that way before, of course you have to be careful with such things so that you don't do more harm than good.

http://kb.mozillazine.org/About:config

Ah! Good man, easy-peasy!!! My browser is working very smooth right now, so I am not going to change anything but since now I know something, I will try this next time when I face the same situation. Cheers everyone for helping me out here. I will lock this topic in the next 24 hours.