ANSWERED slskd port forwarding

[p1pb0y 0]

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!

[Staff 10432]

@p1pb0y

Hello!

We can reach your software from the Internet on the IP address you're currently connected to, port 60798, i.e. your slskd receives the packet and replies accordingly. So your port forwarding configuration, firewall configuration and slskd bind/port setting are all fine and working properly. The logged error must have a cause unrelated to AirVPN port forwarding and also unrelated to the container's firewall.

Kind regards
 

[p1pb0y 0]

Thanks for the quick and helpful answer!

After some more testing, it seems everything is actually working fine, other users can reach me and browse my shares, I just can't reach myself. 

Hopefully this can help others in the same situation in the future