Search Failed message

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
iduls
Posts: 2
Joined: Sat May 13, 2006 1:54 pm

Search Failed message

Post by iduls »

Hello,

I havent used the search for a while and i cant get it to work properly now. Downloaded latest 1.9.9, and i get this message almost instantly after pressing serch:

Search Failed
Error communicating with the server.

No firewall present atm. No viruskiller either. I dont get it.

Server is ueservice.dyndns.org port 2020 default afaik....

Help appreciated! :idea: :wink:
alex
Posts: 4514
Joined: Thu Feb 27, 2003 5:57 pm

Post by alex »

check help menu->about, what version do you see?

v1.9.9 doesn't list the search service server since it is not static any more, if you see it in properties it is an older version.

the message would be given if you use some old UE version before the previous search protocol update, if it is previous it will tell you to upgrade to the latest version, but if it is one more than previous it will give "communication error".

otherwise you need to look whether something is wrong on your side with the network.

but i guess you are just running an old UE version.
iduls
Posts: 2
Joined: Sat May 13, 2006 1:54 pm

Post by iduls »

:shock: :D You are absolutely right, I didnt properly upgrade to 1.9.9. as I thought. Had 1.9.5 running and just unpacked 1.9.9. instead of extracting it using my serial.

Problem is solved, it auto-configured the search in 1.9.9. and it worked perfectly. Thanks man.
Post Reply