SlskQT client often does not appear in search results
Just some facts.
1. Big filelist, big userlist, share is userlist only. No one I ask seems to see it in search results. People I asked were with slskNS, slskQT, Nicotine+. Everyone can download filelist and files, but no search results from this share. Firewall, antivirus, etc, everything was checked, nothing changes.
2. Very small test public share, all default settings. slskQT client does get search results from it. slskNS does not.
In first case I do see occasional lines like "Sending search results to user *** for search string ***" in diagnostics log. I'm not sure if those people do get results or not.
Anyone else noticed anything like that?
Ideas? (Please no "recreate config from scratch". I'm not readding several hundreds users manually second time :-D )
- Log in to post comments
So you're saying people in
So you're saying people in your userlist aren't receiving results from your private share? Are these files shared with them by user group or just by generally being in your user list? I'll run some tests later tonight.
Yes, they are not receiving
Yes, they are not receiving results. Files are shared generally for userlist. No groups are used.
I'm not sure what's going on
I'm not sure what's going on here, I tested from two different Internet locations and I appear to be receiving search results from SoulseekQt for both public and private shares. And if you're getting 'sending search results' messages in the diagnostics log that means you're properly receiving search requests from the distributed network. We can try a remote control session via TeamViewer if you'd like.
Did you test it in pair with
Did you test it in pair with SlskNS too? Two slskQT work here in some cases (see 2). But with slskNS doing search there is no results from slskQT.
Also, on messages in log: I do see them occasionally, but not when I ask people to search for something. So it looks like it works only once in a while or only with some clients or some searches.
Sorry for the late response,
Sorry for the late response, I've been so busy with the last build I've lost track of this conversation. Yes, I tried both. I had no problems receiving results from SoulseekQt on either SoulseekNS or another instance of SoulseekQt. There might be something else going on, but it's very hard for me to say what that might be.