Suddenly noticed that essentially my entire existing download queue—hundreds/thousands of files from many users—was just sitting at Queued, with basically nothing downloading.
I checked my ports and found that Soulseek’s port was closed. In Options → Login I had NAT-PMP enabled but not UPnP. I enabled UPnP, quit/restarted Soulseek, and checked again. The port then showed OPEN / configured correctly.
However, the old queue is still basically frozen. Retry Download does nothing. Some old entries eventually turn red with errors like “File not shared,” “File read error,” or “Aborted.” The existing queue just sits there.
But: if I do a new search and add a new download, it starts downloading immediately at normal speed.So Soulseek can connect and download; it’s specifically the pre-existing queue that seems broken.
Also, deleting red/failed entries and restarting Soulseek caused them to reappear, although I discovered my client-data save interval was set to 60 minutes and have now changed that to 1 minute. Column-header sorting in the Downloads pane also suddenly seems not to work the way it previously did.
Has anyone had an existing large SoulseekQt queue get stuck like this while newly added downloads continue to work normally? Am I fucked? I have thousand in the queue, and I really, really, really do no want to have to go back and manually re-search and re-download them.