Stories
Slash Boxes
Comments

SoylentNews is people

SoylentNews is powered by your submissions, so send in your scoop. Only 17 submissions in the queue.
Meta

Log In

Log In

Create Account  |  Retrieve Password


Site News

Join our Folding@Home team:
Main F@H site
Our team page


Funding Goal
For 6-month period:
2022-07-01 to 2022-12-31
(All amounts are estimated)
Base Goal:
$3500.00

Currently:
$438.92

12.5%

Covers transactions:
2022-07-02 10:17:28 ..
2022-10-05 12:33:58 UTC
(SPIDs: [1838..1866])
Last Update:
2022-10-05 14:04:11 UTC --fnord666

Support us: Subscribe Here
and buy SoylentNews Swag


We always have a place for talented people, visit the Get Involved section on the wiki to see how you can make SoylentNews better.

posted by janrinok on Sunday October 05, @04:03PM   Printer-friendly

We are aware of the significant number of 50x responses that users are experiencing from the site. The problem was recognised about 1 week ago and there is much investigative work going on behind the scenes.

The actual cause is difficult to identify. As of Saturday there is new software in place which is trying to find how often the 50x responses occur, while trying to correlate the occurrences with other functions in Rehash. This is a time consuming process. Some users have been assisting by reporting on IRC #soylent when they receive such a response. If you would like to help please report when the 50x response was received with a precise time so that we can find the corresponding query in the server logs, exactly what function were you doing that appeared to trigger it, and how long the problem lasted? If you also know your own IP address it would be very helpful but we understand that many of you will be reluctant to give this information.

In most cases the problem clears itself in less than 10 seconds but there have been periods of unresponsiveness that have lasted several minutes in some rare cases.

FIXED - at least until we find out that it isn't.... [Added at 2025-1005 19:00Z--JR] See also here.

posted by janrinok on Thursday July 24, @10:15AM   Printer-friendly

Over recent weeks we have been experiencing connections from a large number of bots, spiders and scrapers. Some are the expected ones (Microsoft, Google, Amazon etc) and these tend to rate limit their requests and cause us little problem.

Others appear to be AI driven scrapers and they can result in tying up a large percentage of the site's resources. For the most part they ignore robots.txt or when we return code 429. While they are individually only an annoyance their activity can affect the speed at which the site can respond to members attempts to view a page or leave a comment. They have contributed to some of the 404 or 503 (Backend Fetch Failed) that you might have experienced recently. A small number of bots isn't a problem, but if many bots are querying the site at the same time then they can affect the speed at which the site can respond to your comment or request.

Software has been developed to block such abusive sites for a short period. In the majority of cases this will be invisible to you as users other than to hopefully improve the responsiveness of the site.

However, it is possible that sometimes there might be a false positive and you may encounter difficulties in connecting to the site. If you do experience connection problems please inform us immediately either by email or on IRC. Neither of those apply filters to connections; the short temporary blocks only apply to the site itself. We will have to contact you by email to ascertain your IP address so that we can lift any block that may have been incorrectly applied. Please do not publish an IP address in either a comment or on IRC.

If you are using a VPN or Tor it might be advisable to try another routing to circumvent any temporary block that might be affecting your connection.