Bakadori 0 Posted ... 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! Quote Share this post Link to post
DeepAnger 1 Posted ... (edited) I don't use slsk (SoulseekQt) anymore but only Nicotine+. I think I remember that SoulseekQt requires more than one port forwarded. Edited ... by DeepAnger Quote Share this post Link to post
Bakadori 0 Posted ... (edited) Ah, I suppose this is VERY BASIC KNOWLEDGE, but I just found out that Docker doesn't direct it's containers through the vpn and that I need an extra tool (ie gluetun) to do that . I was able to set it up and everything works just fine. Edited ... by Bakadori Quote Share this post Link to post