The search service protocol has been changed

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
owpex
Posts: 2
Joined: Sat Jun 12, 2010 11:39 am

The search service protocol has been changed

Post by owpex »

I receive this message when I try search something:

The search service protocol has been changed,please upgrade to the latest version

My version is 2.2.1 could somebody help? thank you
Top
jonib
Posts: 397
Joined: Thu Feb 27, 2003 8:46 pm
Location: Sweden

Re: search failed

Post by jonib »

The current version is 2.9.2 download here. your version seems old; you might also need to reenter your latest serial when extracting it.

I have made a tool to check and automatically update UE here. Only 32bit version for now.

jonib
Top
owpex
Posts: 2
Joined: Sat Jun 12, 2010 11:39 am

Re: search failed

Post by owpex »

Everything is ok now,thank you jonib
Top
MrEman
Posts: 123
Joined: Tue Aug 12, 2003 7:06 pm
Location: USA Connecticut
Contact:
Contact MrEman

Re: search failed

Post by MrEman »

Worked fine for me in ver 2.9.2
Now I have the same message in ver 2.9.3......Protocol changed???

I did a reset from the Search/Import settings tab.....
Still not working.....
Top
MrEman
Posts: 123
Joined: Tue Aug 12, 2003 7:06 pm
Location: USA Connecticut
Contact:
Contact MrEman

Re: search failed

Post by MrEman »

OK!
I see there is now version 2.9.5
Upgrade cleared up my problem

All is well now! :D
Top
alex
Posts: 4514
Joined: Thu Feb 27, 2003 5:57 pm

Re: search failed

Post by alex »

v2.9.5 introduces simple search syntax which is sufficient for many users with no need to type control characters, so the protocol change notice.

Boolean wildmats are now implemented more effectively on the server side as well.

In the next version maybe I'll add forced check for updates when protocol has changed, before v2.9.1 it didn't change for couple of years.
Top
Post Reply

Return to “Search service”