ANSWERED Soulseek random ports assignment

[kinsham 1]

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?

[Staff 10494]

1 hour ago, kinsham said:

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.

Hello!

This a wrong assumption. Soulseek clients (like Nicotine+) do not randomly change ports on their own if properly configured. Of course you need to re-start the software if you change listening ports. After the re-start, no new ports are assigned. If this happens something wrong is going on, for example the configuration was not saved, or you forgot to disable some random port selection option (from picking random ports to negotiating via UPnP etc.).  

As a side note, please remember to configure GlueTun environment variables properly, in particular
environment:
- FIREWALL_VPN_INPUT_PORTS=PORT1,PORT2

That's the environment variable telling the containers firewall to allow incoming packets on listed ports of the VPN adapter.

Kind regards
 

[kinsham 1]

Thank you for that. I realised eventually that my Soulseek ports config wasn't being saved. There is no save button, changes are saved every 60 mins by default. Since I didn't wait that long before restarting so the changes were lost. I temporarily changed the default save period to 1 min in options/UI and waited 1min. Now the changes are saved and persist over a restart.
I also made sure that UPNP was disabled and the selected ports opened in Gluetun. All seems good now.