Search not working

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
MJones
Posts: 6
Joined: Sat Sep 10, 2005 9:08 pm

Search not working

Post by MJones »

Hi. Search stopped working for me today with "Search failed (8)" message. After a few tries it said something about trying to retrieve configuration, but still didn't work. Tried resetting search configuration in settings, but that didn't help. UE reaches out to the web site IP after the reset then to various ports on 47.197.50.146 then 73.187.26.100 and then errors out again.

Please assist. Thanks.
alex
Posts: 4514
Joined: Thu Feb 27, 2003 5:57 pm

Re: Search not working

Post by alex »

One server was down for several hours and I wasn't monitoring it at the time, it was fixed back then.
Post Reply