Cannot download and save from search results

03 Oct 23: One server was relocated, the server currently doesn't have a public IP address since in the meantime it is running on starlink. I wrote some additional tunnel code running separately to handle this. When the server is engaged the connection is 5600+ days uniform (since around 24 July 2008). In the unlikely case I disengaged the server because of some problem the retention is 1200-3800 days depending on newsgroup. If you experience any issue please let me know.

29 Nov 23: Because of encrypted and obfuscated posts flood mass posted by a few nzb indexing websites using usenet servers as private storage for their members to download the posts - the situation with the content is pretty chaotic since their purpose is to post in such a way, so users must use their website exclusively, when the website disappears - the encrypted posts just eat usenet providers' hard disk space uselessly. If you can't find something specific please let me know at alexbirj at gmail dot com what exactly you can't find for me to check how it is possible to retain the posts. Non-obfuscated posts shouldn't be affected at all, let me know if you notice anything missing.

29 Nov 23: The search protocol had to be upgraded to extend 3 byte (16M+) limit on the server side for number of sets per instance, so at least the version 5.8.3 is needed to access it, otherwise should be no any difference.
Post Reply
ticatc3
Posts: 23
Joined: Wed Jun 18, 2008 7:47 pm

Cannot download and save from search results

Post by ticatc3 »

Hi,

When i select 1 article from search results and click download and save it's ok. When i select multiple articles using select related headers and click download and save attachements, i wait and wait and nothing happens.
alex
Posts: 4514
Joined: Thu Feb 27, 2003 5:57 pm

Post by alex »

in the search bar, when it happens, what is the status of the leftmost button, is it "search" or "cancel"?

if it is "cancel" (i guess it is) it means the request is in progress, might be temporary connectivity problem from your location or some issue with router. check the connection status how fast the data is coming in.

from server statistics cancelled or failed requests for messge-ids are around 0.2% of total - it shows overall total and number of errors, including when cancelled in the middle of the request, it cannot know really the cause, just socket write returns error.
Post Reply