03 Oct 23: One server has been relocated, the server currently doesn't have a public IP address in the meantime. 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" flood mass posted by few nzb websites and newzbin-like communities using usenet servers as private storage for their members to download the posts - the situation with the content is pretty chaotic, since posts are disguised in such a way, that users must use the satellite ecosystem (whish is not a part of Usenet) exclusively to download them, when the website disappears - the encrypted scattered posts just eat usenet providers' disk space uselessly. If you can't find something specific please let me know what exactly you can't find for me to check how it is possible to retain the posts. Legible posts shouldn't be affected at all, let me know if you notice anything missing.
08 Aug 24: After being unchanged for many years the search service communication protocol had to be updated a few times in part to resolve a server side set feature limitation and properly handle trial searches on the relocated server. The searches themselves are not affected and it looks like the work is now complete.
15 Mar 25: It looks like the search service is currently down as there are no pings. The other server is no more on starlink, but the search requests are still routed and the access to it is through the first server, since it is safer, but the direct access is no problem if this will be a repeated issue. The connection will be restored or server restarted as soon as possible.
16 Mar 25: One server is currently still down, the other server was reconfigured and already connected directly, so the search service is running with minimum possible retention gaps.
25 Apr 25: The search service monitor sound alarm was not always activated to alert me in the case of an unplanned server restart (e.g. tripped breaker) like it happened today. This is now fixed and thus the search service downtime of this nature is less likely.
I'm getting the same error message today.
Search Failed: A connection attempt failed because the connected party did not properly respond after a period of time, or...
Same here
Is it me, or
edit:
forum related; I received an internal server error and persumed this post wasn't posted, went back a page, clicked the post button again and saw two copies of my post, wanted to delete the last one, but couldn't because there was already a reply.
A moderator might want to delete this edited post, or
"A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond"
it just retrieves standard error messages from the system by error code, if it is too long it is cut, you can find the rest through web search.
