Not connected, Your IP: 216.73.216.195
Online: 48659 users - 679490 Mbit/s total BWSearch the Community
Showing results for tags 'soulseek'.
Found 4 results
-
Hello! I've been able to use port forwarding both in qbittorrent and nicotine+ (soulseek client) thanks to the possibility to choose the Network Interface in those apps. But when I try to run slskd (different soulseek client) as a container in Windows Docker Desktop, I can't get the listening port to work (own shares are not browsable by other users, other functions ok). I have (ie 12345) soulseek: listen_ip_ address: 0.0.0.0 listen_port: 12345 in my config yaml and ports: - 5030:5030/tcp - 5031:5031/tcp - 12345:12345/tcp in my compose. In Docker I have host networking enabled and the port binding behavior is Open (Default). If someone has a similar setup working and can let me know what I'm missing / doing wrong, thanks in advance! -
Soulseek requires two consecutive ports to be opened which I can do in the client area. I'll be using gluetun in a docker container alongside Soulseek. Since these ports are statically assigned, the ports setup in Soulseek needs to match. The problem is that assigning matching ports in Soulseek doesn't take effect until it is restarted (or so it says) and then it assigns two new ports which then no longer match the port forwarding. Has anyone found a way round this?
-
Hello good people, hope can you help me think why I'm not getting port forwarding to work on the slskd soulseek client (https://github.com/slskd/slskd/) I am running it in docker alongside gluetun. I am using the same setup for a working port forwarding with qbt, so I know it is possible FWIW I am using wireguard. I have: Configured forwarded port 60798 in airvpn dashboard (also forwarded 60799, as some clients needs this, but probably not slskd) Set up the correct listering port in slskd application Opened the gluetun firewall (FIREWALL_VPN_INPUT_PORTS) for 60798 and 607999 Verified that the port 60798 is open using "test open" - TCP on ipv4 is open on 82.102.27.195 (Camelopardalis) Alas: The slskd logs says it is failing to communicate with my user on 82.102.27.195:60798. I have checked the other posts on the forum, and slskd does not have a NAT/PMP option to toggle. Is there anything else I am not thinking about? Or does this narrow it down to slskd? Thanks!
-
ANSWERED Help with SoulSeek and forward porting
nubdubnub posted a topic in Troubleshooting and Problems
Hi everyone, I purchased AirVPN recently to use it with a p2p file sharing application SoulSeek. I'm very new to this stuff and really in need of some guidance. I was able to add my 2 ports in the "client area" section of the AirVPN website. Then I ran a TCP test check and recieved the message, "Not reachable on server IP over the external port #####, tcp protocol. Error 110 - connection timed out". I'm not into torrenting, I just want to use this VPN for Soulseek. I haven't done anything to my router since I'm not comfortable messing with the settings on it. Also when I check the ports on SoulSeek it also says the ports are closed. Any guidance is most welcomed! -Nub
