socket error

[William Jacquier]

Hi, i have problem today (SOCKET ERROR)

SOMEONE CAN HELP ME ?

thx by advance

[Toine Rademacher]

SLSK is down, so that's why

Op woensdag 29 mei 2024 om 20:04:06 UTC+2 schreef William Jacquier:

[OLeev Toots]

Have the same problem one hour ago and it's resolved ;) 

Not Down @ Toine Rademacher

[Hannes Pi]

I can't seem to download anything atm

Op woensdag 29 mei 2024 om 21:28:15 UTC+2 schreef OLeev Toots:

[Hannes Pi]

Up, restarted and killed another process in taskmanager called SOulseekQT now it seems to work again

Op woensdag 29 mei 2024 om 21:28:15 UTC+2 schreef OLeev Toots:

Have the same problem one hour ago and it's resolved ;) 

[Blair Ketelaar]

hi soulseek is down

[BlastoiseVeteran]

glad its not just me, i was about to pull my hair out trying to fix it.

[Blair Ketelaar]

hi anyone else find soulseek is down

[Electronic Music Lover]

hello , slk is down in Spain. Greetings

[Nir Arbel]

The service isn't offline but there are a lot less users on than usual. Is www.slsknet.org visible to you?

[Blair Ketelaar]

yes i can see it

[Nir Arbel]

The website is visible but the client doesn't reconnect if you exit and restart it completely?

[Blair Ketelaar]

no it does not

[Nicholas Stevens]

Nope, it's not working

[Nir Arbel]

Sorry do you mean both the website and the client aren't working or just the client?

[Blair Ketelaar]

just the client

[Nir Arbel]

I restarted the server. Any difference?

[Hardcore Uproar]

Good morning Nir, it's the same here in the UK and the Netherlands. Client not connecting but showing some users and the website is still accessible.

[Nir Arbel]

Is this with SoulseekQt? Are you able to connect with Nicotine Plus?

https://nicotine-plus.org/

[Hardcore Uproar]

No difference after you restarted

[DJAetius]

lol another week, another socket error

[Nicholas Stevens]

I haven't noticed a difference even with restarting the app

[Hardcore Uproar]

Nicotine appears to be working

[Blair Ketelaar]

how do i install nicotine

[Blair Ketelaar]

any ideas what could be wrong

[Nir Arbel]

I'm very worried someone is exploiting a software problem in SoulseekQt that doesn't exist in Nicotine+ or slskd... I have no problem connecting with SoulseekQt myself though, so I can't reproduce whatever is happening. I also don't understand why someone using SoulseekQt wouldn't be able to reconnect either. I'm hoping something will shed some light on this soon.

[Alex Morris]

Nicotine+ and the old school slsk seem to be connecting

[heddy.b...@gmail.com]

from my side i can confirm it works with nicotine-1-2-16 and not soulseekQt 219-7-22

with same user, and so on

[Nir Arbel]

Which operating system are you people using?

[heddy.b...@gmail.com]

w10

[Nir Arbel]

Hang on, I figured something out. I'll report more soon.

[Illorca]

same problem here in italy. Anyway, many thanks to all of you for your work.

[Stan Iconic]

Eindhoven The Netherlands represent!!! same problem thooo greetings and thanks so much for the awesome app "Soulseek" its a killer!!!!

[Punta]

same here its been saying socket error since about last night around 1130pm here in Windsor,on,Canada. I tried to do it about 10 mins ago deleted it then re downloaded it same shit

[Nir Arbel]

Looks like our main server port was either temporarily blocked by our host or under attack, but it's working for the time being. Nicotine+ and SoulseekNS use a different port so they weren't affected. If you still can't connect, please let us know which server port you have configured. It's listed under Options->Login in SoulseekQt.

[Electronic Music Lover]

port 60246

[heddy.b...@gmail.com]

it's ok now thanks a lot Nir

[Blair Ketelaar]

so is the latest version of soulseek working again

[heddy.b...@gmail.com]

spoke too quickly, down again :(

[Electronic Music Lover]

hope not much troubles to find a solution, thanks.

[ferday the unicorn]

62793

[Noonien Soong]

Port 2242 does not work

Port 2271 does work!

Latest SoulseekQT

Windows 11 Enterprise

sproutletMOSS schrieb am Montag, 3. Juni 2024 um 11:08:43 UTC+2:

64403

[Mo]

server port 2416

[AK' WAK]

thanx working back with your settings

On Monday, June 3, 2024 at 11:27:27 AM UTC+2 Mo wrote:

server port 2416

[Gerd Maes]

not working here

Op maandag 3 juni 2024 om 11:35:42 UTC+2 schreef AK' WAK:

[Nir Arbel]

You just need to pick a port other than 2416 or 2242. See the instructions here: https://www.slsknet.org/news/node/3722

[ferday the unicorn]

thanks Nir

confirm it works fine

[Антон Дикобраз (HystriX)]

Tried this and connected successfully. Had problems all last week and today. It seems that the problem with ports persists somehow.

[Freek Claessen]

Thanks for the update. Had the same issue, costed me 2 hours until I read this thread. Working with other server port (not 2416) now.

Op maandag 3 juni 2024 om 13:08:58 UTC+2 schreef Антон Дикобраз (HystriX):

[Ben Ashdown (Manctalo)]

2271 working, 2242 no

[Gia Gia]

I can't connect when I'm using AirVPN (https://airvpn.org/).

I contacted their support and they replied:

We're also sorry to hear that our infrastructure was used for such a purpose. If they contact us during such a problem we perhaps could help preventing that similar incidents re-occur.
Kind regards
AirVPN Support Team

[Blair Ketelaar]

soulseek is working for me

[tn5421]

It doesn't actually say what ports to pick, just that those two don't work.

[Mo]

well yeah, because most of the ports that aren't those two still work

[Sebastian Alvarez]

Tried changing port to 2271 but it prompted upon reopening: Login failed due to a wrong username/password combination. If you haven't logged in in a while, it's possible your username was recycled and taken by another user. Please try logging in with a different username and password using the button below, or via the 'Login As' button above the Options->Login tab.

On Monday, June 3, 2024 at 1:30:32 PM UTC+2 Ben Ashdown (Manctalo) wrote:

[Toine Rademacher]

So 4 days ago I finally was able to connect again from The Netherlands as. I'm using Nicotine 3.3.4 in a Docker Container behind Windscribe VPN with Gluetun and port 2242. This always worked perfectly, but unfortunately the connection problems got back and got the following Error inside Nicotine+: server.slsknet.org:2242: [Errno -3] Temporary failure in name resolution

I will try it out with the other port people recommended here '2271' but I'll report back if this will work.

@Nir Arbel: can you give us an update on the blocked ports? Will this be restored, you think? Also, which ports do you recommend to use alternatively for SoulseekQT and Nicotine=? Thanks!

Op dinsdag 4 juni 2024 om 10:38:44 UTC+2 schreef Sebastian Alvarez:

[Nir Arbel]

That looks like a DNS resolution problem, but it seems to resolve properly everywhere.. try looking into your DNS settings, there are free DNS resolvers you can google that might work better for you.

[Toine Rademacher]

Hi Nir, I just fixed it! Current settings:

Listening port: 2234 (Port forwarded Router to nas)

Server: server.slsknet.org:2416

I use Cloudflare 1.1.1.1 / 1.0.0.1 DNS

Hope this helps, Thanks!

Op woensdag 5 juni 2024 om 02:04:10 UTC+2 schreef Nir Arbel:

[Nir Arbel]

Glad it worked out!

[Lucien23s]

hey, it seems to be down again? just 1 hour ago here

[Nir Arbel]

Everything seems to be up. What port are you using? What error message are you getting?

[Lucien23s]

port 2271 & socket error

[Nir Arbel]

2271 seems to be working for me. You can try 2242 or 2416 but it sounds like there's something else going on.

[Lucien23s]

Neither 2242 or 2416 doesn't work for me. I've got this problem for several days. Today I tried it again and it suddenly worked (not sure if it was because I changed the port). I used it normally for about 3 hours but then it returned to the previous state again. By the way I tried the "Check Ports" button and the result was always "CLOSED" even if during the time it worked normally, which is confusing for me.

[Nir Arbel]

The check ports button checks the ports you use to accept connections from other users, it has no bearing on your ability to connect to the server. I'm sorry... I don't know what's causing your connection problem.

[Lucien23s]

that's a frustrating news for me. I almost can't live without slsk... when you know what causes the problem please let me know. thanks in advance!

[dirk elst]

austria here, same issue as Lucien23s

[Nir Arbel]

There's a good chance a VPN will get around any connection problem you're having. If you want to help me diagnose your specific connection problem, you can try installing Wireshark, starting a capture on your network connection using the filter:

tcp port [soulseek port]

Where [soulseek port] is what's listed as the server port under Options->Login. Wireshark should show a bunch of packets coming in. Once it stops, stop the capture and save it as a file. Send it to me privately or if you can't see my email address let me know when you have it and I'll contact you directly.

Thanks, Nir

[Lucien23s]

Hi, I use VPN quite a lot before my slsk stopped working. I could't connect to slsk when I was using VPN though,  if I wanna do so had to turn it off. So I don't think VPN will work for me, at least not the one I'm using.

And I don't know where to see your email address, yeah. Please let me know how can I contact to you.

Speak of Wireshark, I've downloaded it and I've seen those data packets of slsk successfully. However, the saved output file looks quite big (about 100MB), I guess I only used the filter of observing properly, but the output filter not. Please tell me how to set the filter for saving files.

[Toine Rademacher]

Unfortunately SLSK just stopped working again for me :( (Netherlands). Tried port 2242 (default), 2416 and 2271 but still getting the same error "[Errno -3] Temporary failure in name resolution"
I'll see if I can try installing and check with Wireshark, but as i'm running Nicotine+ inside a docker container, I dont think it will be that easy.

I'll also try changing the location of my integrated VPN, but when this was the cause of a problem I had before, it didn't show me this same error message.

Op vrijdag 7 juni 2024 om 16:29:04 UTC+2 schreef Lucien23s:

[Nir Arbel]

That's a DNS resolution failure. Try changing your DNS settings, maybe use a free resolver like 8.8.8.8/8.8.4.4

[Lucien23s]

Hi Nir, did you see my reply?

[Lucien23s]

Hi, I tried using other VPN and my slsk started working again. Thank you so much for the help!