Bitcoin Forum

I See 3x this messages today


I just want to opening post/thread and happened, any one know what this mean?

clicky finger go Brrrr  ::)
means you are most likely clicking a load of links too fast

You need to open quite a lot of pages to get this message. Do you have a scraping bot running, or share your IP with other Bitcointalk users?

It literally tells you in your own quote.

You have been quoted the right answer.

"Most likely, you are accessing the forum too quickly. You are only allowed to access at a rate of one pageload per second on average (somewhat higher bursts)."

Or maybe server overload because might be the reason is there are too many users trying to connect this forum at the same time.(Maybe because of the pandemic lockdown and everyone stayed at home). Or might Ddos attack.

Anyway, it's browsing fine at me. Try to refresh the site and press this if your are using PC. "Ctrl+F5".

I see that type of message rather often on Fridays (thrice in a morning would be a sweet deal), since that is when I access the forum whilst retrieving forum profiles from my Alt Account. It makes Fridays pretty difficult to interact with the Forum for me until my data processes complete their task.

Refresh the browser and you’ll be fine in read type operations. If the message appears during a write type operation (post, report to moderator, etc.) you’ll need to be a bit more careful with the effect a refresh may have (sometimes the 503 error message appears despite the update operation concluding, and a refresh may launch the same write operation again, causing a double post or double report).

Why do you need to open so many pages so quickly ? Just use the forum like a forum only  ;)
It will just put the load on bitcointalk and this message /error is to prevent the DDos attack.

How much delay do you use on your scraper? If you make it slightly more than 1 second (say: 1.2 seconds), it's already enough to give you 10 "manual" page loads per minute.
I think you scrape different data than I do, but if it's the same, I can easily share the raw data.

I believe it is set to around just over one second per page per process. The data retrieval is not really an issue currently, and the 503 is produced because I launch a couple of processes simultaneously, thus causing the event to occur rather more often than if I streamlined retrieval in a single process. The processes overcome the 503 with automatic retries, so there is no need for me to do anything manual there (the manual part is only whilst, at the same time, I additionally browse/write on the forum).

The reason why I use a couple of simultaneous processes, knowing that it will create greater collision and 503 errors is down to using free software, with limited 10K batches: It’s better for them to collide but get 20K done overnight and/or morning, than having to launch one after another (unless I automate the sequence, using an external additional tool). I did create a python (unlimited) solution, but never quite finished it for both profiles and posts. With the volumr of data I'm retrieving, it's fine for now (cheers for the offer).

In that case: why don't you increase the delay per process? On AWS, I use delays varying from a few to more than 10 seconds, because I have a different number of scripts running simultaneously.

Yes, I should probably take a look at what I can tweak on that front. It’s not much of an issue really though, except for trying to post simultaneously, and I’ve become accustomed to trying to post less on Fridays. Kind of got used it, until the day it becomes an issue, and then one needs to get on to dealing with it…

Today, I received 503 error

https://i.postimg.cc/FKNPtsRC/503.png

I had opening bitcointalk as usual not too quickly.

Using Tor or VPN?

Tor

You might be sharing an exit node with someone who's making a lot of requests... maybe it's my scraper LOL.

Is it even possible to get more than one page per second through Tor?

You're kidding about scraping through Tor, right? :o

---

---

Since yesterday, I get a Cloudflare captcha (without Tor) when I click "All" on a topic. I don't think it's related though.

This my first time to see this, I believe it should be some kind of system errors. And over 2 years of being on bitcointalk.org have not gotten this error before.

I also experienced this error today. If you see it once or twice, there is nothing to worry about. Also i think this is due to server being overloaded or responding slow at times. This does not mean that we are refreshing the page again n again and loading it too fast.

Yes.


No.

https://i.postimg.cc/kM2VqzNW/qqq.png

have you received too?,

---

maybe suchmoon scraper?

Probably not :)

I'm getting the 403 error now too. Requesting a new Tor circuit usually fixes it. So it seems to be related to certain Tor exit nodes although it's been happening quite a lot in the last few hours. Maybe some sort of DDOS attempt over Tor is happening.

I don't think that's the case, I tried clicking the first link I see every time the page loads and nothing happens as well as opening the links to the new tab and still I don't see any kind of error. It looks like it has something to do with multiple accounts or an IP address being shared by other Bitcointalk users which is the consensus answer for the ones experiencing it.

can member login the same time with 2-3 different address? maybe someone out there has accessed my account while I am logged in.

I don't understand what has shared IP and etc. In the beginning, I never use real address while accessing the Internet because I ever read the news the hacker can easy hijacking computer activity using real IP.

Yes, but I don't think that causes the overload-error.

See https://bitcointalk.org/myips.php, and change your password if someone else has had acccess. There have been cases where accounts were compromised, but the attacker only used it to send PMs. None of that has anything to do with error 503 though.