Cannot browse my own files

Submitted by Insiteful on Wed, 05/16/2012 - 10:00
Forums: 
Soulseek General Discussion

Not sure whether this is a bug, a feature request. I am still able to add myself as a user, and I appear in my own "user list". However, I cannot browse my own files. This is a handy feature of the older versions, which is useful for diagnostics and other purposes. If it is easy, could it be re-implemented in SoulseekQT? Thanks.

Submitted by Nir on Wed, 05/16/2012 - 22:54.

If your listening port is forwarded (you should get a link in the share browse failure message that allows you to check for this) you should almost definitely be able to browse your own files. The upcoming upload files feature will also let you see your own share without trying to read it over TCP, as it's essentially a browse your own share feature that lets you pick files to send to another user.

Submitted by Insiteful on Thu, 05/17/2012 - 22:08.

Thank you for your reply. Yes, I have confirmed that my port is operating properly, and I can browse other users' files with no problem. When I try to browse my own files (by adding myself as a user in the "user list"), SoulseekQT give me an error: "A connection could not be successfully formed to the user. If this is happening to you a lot, Check here to make sure that your port is open." I test the port, and it passes. I am running Snow Leopard on a macbook pro. I am also able to run Windows XP on the same machine (using Fusion), and I have confirmed that SoulseekQT will not allow me to browse my own files on that OS, either. I can, however browse my own files with ver.157 in Fusion (XP).

Submitted by Nir on Fri, 05/18/2012 - 17:43.

Let me build you a version that does user logging. This should give us a better look at what's going on when you try to browse yourself.

Submitted by Nir on Sun, 05/20/2012 - 00:10.

Sorry it took so long. My Hackintosh crapped itself once again after upgrading my motherboard BIOS. This build: SoulseekQt-5-20-2012.dmg will let you see logging specific to a particular user. Try browsing yourself, wait for it to fail, then right-click your username either in your userlist or a room you're in and select 'User Log' at the bottom. Copy everything from the All tab and paste it here. Let's see if it'll show us anything unusual.

Submitted by Insiteful on Tue, 05/29/2012 - 09:02.

Thanks, Nir. Log is below. Please note that I am not the only one having this problem. See below in the Forum entry labeled "Browse user's files", where "decimal-" seems to have the same problem: he says "But I can't browse some users, including myself. I get this port error as reported before..."
---------------------------
[Log Data]

Submitted by Nir on Mon, 05/21/2012 - 16:17.

Hmm. It does look as if the TCP connection simply fails in both directions here, which I can only theorize has something to do with the operating system blocking it for some reason. One last thing that occurs to me is that it might have something to do with the obfuscation not working, which may be a result of something not translating well into 64-bit, the OSX client being the one version of SoulseekQt that's compiled as 64-bit. Let me compile you a version that does away with obfuscation altogether. Let's see what kind of log we get with that one.

Submitted by Nir on Tue, 05/22/2012 - 01:13.

Here we are: SoulseekQt-no-obfuscation-test.dmg

Submitted by Insiteful on Tue, 05/29/2012 - 09:02.

Sorry for the delayed response. Yes, I tried the new "no-obfuscation.dmg" client, and I was able to browse my own files. I will be switching back to the latest public release, until you are able to implement a fix. Thanks! Log is below:
----------------------
[Log Data]

Submitted by Nir on Sun, 05/27/2012 - 13:58.

Can you verify in the same session both that the no obfuscation client succeeds and the public client fails?

Submitted by Nir on Sun, 05/27/2012 - 21:21.

Oh crap, you know what, I think I know why this is happening. SoulseekQt maintains a separate port for obfuscated connections. The reason for this is so that it can assume from the get go that traffic on the alternate port will be obfuscated, without any kind of coordination that might betray its nature to would be traffic analyzers. The obfuscated port is typically your assigned listening port+1, you can make sure by looking at the Diagnostics->Logs->Port Forwarding tab. I bet once you forward that one as well you should be able to browse your files with the unmodified client. I definitely need to add a way to indicate that to the user in case they're manually forwarding their ports.

Submitted by Insiteful on Tue, 05/29/2012 - 08:18.

I changed my modem port-forwarding configuration, and added my assigned listening port+1. I can now browse my own files, no problem. Thanks, Nir.

Submitted by hannibalforez on Sun, 11/18/2012 - 02:59.

Hi,

Sorry but I am not experienced enough and I would like to know concretely (simply) how to modify my settings to solve this problem which I also have?

Thanks

Submitted by decimal- on Sun, 05/20/2012 - 04:45.

same problem for me !
using soulseekqt build 5/10/2012 on mac osx lion

Submitted by decimal- on Sun, 06/24/2012 - 04:23.

the "upload to user" option works as workaround for the problem of browsing your own files. Thank you nir :)

thescarletfire's picture

Submitted by thescarletfire on Fri, 01/25/2013 - 07:24.

I can also confirm that even with all ports completely open in the options, SoulseekQT is still unable to browse my own files - I am forced to use the "upload to user" option to see my shares.

Also, I can confirm that on Soulseek NS I can see 3 folders of another user's shares but in QT, Soulseek only shows ONE of those folders - so, why would that difference occur? Why would NS show more shares than QT when searching someone's shares? Thoughts? I am forced to keep using NS for certain Soulseek sharing, and I want to use QT but it's just having it.

Submitted by Nir on Sat, 01/26/2013 - 10:52.

If you're logging in with different usernames on each client, it's possible you have access to privately shared folders on one that you don't on the other. If you give me the name of the user you're having this issue with I can try and verify whether this is the case or if there's a bug in SoulseekQt that's causing it.

Thanks, Nir

thescarletfire's picture

Submitted by thescarletfire on Thu, 01/31/2013 - 18:35.

I'm not sure if the Mac client was fixed but the Windows QT client still will not let me browse my own files - and the ports are all most certainly opened here. The NS client works fine, but QT still requires the "upload to user" workaround just to be able to see my files.

Just an FYI.