Soulseek Port Closed? Here’s How to Fix It
“Soulseek port closed” means incoming TCP connections cannot reach your client at the tested IP and port.
Start with the connection you use
Downloads can work even when your port is closed: Soulseek can connect out to a reachable peer. Opening your own port lets more peers connect to you, as the Soulseek FAQ explains.
Find your Soulseek listening port
In SoulseekQt, open Options → Login → Listening port and write down the number. The original client uses Options → General options; Nicotine+ puts it under Preferences → Network.
Keep the app running. A port test needs a listening app at the other end, so closing Soulseek before testing can produce a closed result even with a correct router rule.
How to change the listening port in Soulseek
Keep the current port unless another app uses it or your VPN assigns a different one. A closed result alone is not a reason to pick a new number.
- Use an available local port for a home router, or the port assigned by your VPN.
- Enter it in the listening-port field, apply the change and restart SoulseekQt.
- Update the router or VPN mapping and any port-specific firewall rule to match.
Use the listening port, not the server port. The server port is used for your outgoing login connection. Nicotine+ defaults to 2234, but there is no universal best port for every setup.
Does Soulseek’s obfuscated port need a second rule?
SoulseekQt also displays an obfuscated port, normally the listening port plus one. Read both numbers in your version. If you control both mappings, forward both TCP ports to the same computer and test each separately.
Nicotine+ uses one ordinary TCP listener and does not implement obfuscated connections, according to its protocol reference. If your VPN supplies only one port, see the single-port setup before trying to open the adjacent port.
Allow the client through your firewall
This applies to both home and VPN connections. Open the instructions for your operating system.
Soulseek port closed on Mac
Open System Settings → Network → Firewall → Options. Add SoulseekQt or Nicotine+ and allow incoming connections. Check whether “Block all incoming connections” overrides the exception, and review any third-party network filter. See Apple’s firewall instructions.
Keep the firewall enabled and use an app exception.
Allow Soulseek through Windows Firewall
Go to Windows Security → Firewall & network protection → Allow an app through firewall. Check the actual Soulseek executable and the active network profile. A VPN adapter can use a different profile from home Wi-Fi.
For advanced rules, allow inbound TCP for the app and required port. Microsoft’s rule guide covers these conditions. You do not need to disable the firewall or put the computer in the router’s DMZ.
Next, configure the home router or your VPN’s forwarded port, depending on how this client connects.
Match the router rule to the app
For Soulseek port forwarding, the router must send incoming TCP traffic to your computer’s LAN IP—its address inside your home network. If Soulseek uses a device VPN, use the VPN setup instead.
If you already have manual rules, review them below. Otherwise, enable UPnP in the client and router if supported; this lets the app request its own port rule. Run the port test. If it opens, skip manual forwarding. If it stays closed, sign in to the router’s app or admin page and follow the steps below. Use the access instructions on its label or in its manual.
- Reserve the computer’s address. Find it in the router’s connected-device list and reserve its current IPv4 under DHCP / Address Reservation. This keeps the destination the same after a restart.
- Find Port Forwarding or Virtual Server. Add a TCP rule with the listening port as both external and internal port, and your computer’s reserved LAN IP as destination. Edit an existing rule for that port instead of creating a duplicate.
- For SoulseekQt, add its displayed obfuscated port too. Use a separate TCP rule to the same computer. Nicotine+ needs only its single port.
- Save and test. Keep the client running and use the port test below. If needed, the firewall instructions cover the separate computer-side check.
Example: your computer is 192.168.1.50 and its listening port is 50000
TCP 50000 → 192.168.1.50 → TCP 50000Substitute your own address and port. Use the same pattern for a second port if your client shows one.
Need the router screens? Follow our TP-Link port forwarding guide. If automatic and manual entries conflict, use the UPnP vs. port forwarding guide to choose one method.
Run a Soulseek port test
- Leave the client running. In SoulseekQt, use Check Ports under Options → Login. In Nicotine+, use Check Port Status under Preferences → Network.
- Check the IP and port on the test page. For a VPN test, these must match the VPN’s exit IP and assigned port. If split tunneling sends the browser outside the VPN, include it in the VPN route first.
- Read the result for each port. Nicotine+ has one; SoulseekQt shows a main and an obfuscated port. An unassigned adjacent port on a single-port VPN will stay closed—use the single-port guidance rather than repeatedly changing the router.
- If the forwarded port is open, confirm sharing. Ask a trusted peer on another connection to browse your shared folder and transfer a file you are permitted to distribute.
- Once it works, retest after reconnecting. Restart the client and reconnect the VPN if used. Update any changed port before testing again.
Once Soulseek has open ports for your chosen setup and a peer can reach your shares, save the working settings and stop. If a port is open but transfers fail, check sharing and queues.
Ports still closed after setting up port forwarding? On a home connection, try the manual rules if automatic mapping was your only attempt; if manual rules also fail, check upstream NAT. On a VPN, check its forwarding assignment. If you have completed the relevant branch, send your recorded results for help.
Save the port-check worksheetCheck for CGNAT or a second router
CGNAT means your provider shares a public internet address among customers. Your home-router rule cannot open the provider’s incoming mapping. If you use a hotspot or shared network and cannot access its main router, go straight to what to ask the operator.
Otherwise, find WAN IPv4 on the router’s internet-status page. This is its provider-facing address, not your computer’s LAN IP. Compare it with the public IPv4 seen by websites, using our CGNAT check instructions. For this home-route check, close the file-sharing client before disconnecting a VPN. Reconnect the VPN before reopening the client.
- WAN starts with 100.64 through 100.127
- This is shared address space used for CGNAT. Ask your ISP for a public IPv4 that allows incoming connections.
- WAN is 10.x, 172.16–31.x or 192.168.x
- There is a private NAT layer upstream. If it is another router you own, forward on both routers or use a supported bridge setup. Otherwise, ask the network operator.
- WAN matches your public IPv4
- If the client, firewall and router-rule checks are complete, ask your ISP whether it filters incoming TCP. If it does not, use the support instructions with your test results.
- The addresses differ, but neither range fits
- Ask the ISP to explain the mismatch before changing more settings. It may need to confirm how your connection reaches the public internet.
If you control a second router, follow the double NAT guide. After changing the network layout or receiving a public IPv4, check the forwarding destination on the router now handling your connection.
What to ask your ISP or network operator
“Can this connection receive incoming TCP on the ports my Soulseek client uses? If it is behind CGNAT, can you provide a public IPv4 so I can forward them on my router?” A dynamic public IPv4 can work; a static address is not required.
If the operator cannot provide inbound access, a VPN with port forwarding can offer another route. If you cannot use either option, home-router changes alone will not remove the upstream restriction; some transfers may still work through outgoing connections.
Set up Soulseek VPN port forwarding
Your VPN must support incoming port forwarding; P2P support alone is not enough. First find your client’s listening-port field and allow the app through the computer’s firewall. Then use your provider’s mapping, not a home-router rule.
If your current plan supports forwarding, configure it before considering another subscription. If it does not, you need a supported plan or a home connection that accepts incoming traffic.
Soulseek port closed with Proton VPN
Proton assigns one active port. This fits Nicotine+’s single listener. It can cover SoulseekQt’s main port, but not automatically its adjacent obfuscated port; if you want every displayed port to be reachable, use Nicotine+ or a service that forwards both Qt ports.
- Use a paid Proton VPN plan, connect to a P2P server and enable Port forwarding.
- Copy the displayed active port into your client’s listening-port field. Apply the setting and restart the client when needed.
- Disable router UPnP/NAT-PMP mapping in the file-sharing app. Proton’s Moderate NAT setting must also be off for port forwarding.
- Use the test below with the VPN connected. After reconnecting, read the active port again and update the client if it changed.
Follow Proton’s instructions for your operating system to find the forwarding control. On macOS, check the early-access requirements if the option is missing.
PureVPN: forward the ports shown in SoulseekQt
Before buying PureVPN’s port-forwarding add-on, confirm that it supports your client’s TCP port or ports on the chosen location, operating system and protocol. With support confirmed, enter those numbers in the forwarding settings, reconnect as instructed and test each port.
Soulseek not downloading files even with an open port?
Stop changing the port and check the transfer itself. A file that stays queued forever may belong to a busy or offline peer, or may no longer be shared. Try another reachable user and check sharing permissions.
If others cannot browse your own shares, confirm that your intended folder is in the client’s shared-folder list and accessible to that user. In SoulseekQt, manage folders under Options → File Sharing.
A Soulseek socket error during login concerns the server connection, not this incoming-port test. Record its exact text and use the client support links below if you cannot log in.
Still closed after the relevant checks?
Send your completed worksheet to the team that controls the failing connection: the VPN provider for a VPN-only failure, or your ISP / router support for a home-route failure. Include the client and version, operating system, tested port, forwarding settings and exact result.
If the network provider confirms the mapping is working, use the Soulseek technical forum or Nicotine+ issue tracker for client troubleshooting. Redact public IPs and account details from public posts.