December 2, 2025Dec 2 Author On 11/28/2025 at 3:25 PM, Friarsgate_Customs said:Having the same issue here as well. Minus trying to uninstall and reinstall. I have this container on auto update every night, and maybe 5 days ago I saw that it wasn't auto starting anymore, and then yesterday I tried to start the container 3-4 times and it wouldn't stay running at all.On 11/27/2025 at 3:28 PM, Keek Uras said:After this latest update, Nicotine will not stay in running state. After it is rebooted at night, it stops. I can start it but when I refresh the page, it's stopped again. The only way I can find to fix is uninstall and reinstall the docker each day. The logs provide nothing useful. Any suggestions? Thanks!fixed, please pull down the latest image at your convienience.
December 2, 2025Dec 2 4 hours ago, binhex said:fixed, please pull down the latest image at your convienience.Working great again, thank you much! I wasn't super worried because I have Slskd set up as a backup container, but I like the nicotine+ experience a lot better. Thanks again
December 3, 2025Dec 3 21 hours ago, binhex said:fixed, please pull down the latest image at your convienience.My issue is resolved as well. Thank you so much!
December 15, 2025Dec 15 Greetings all. I'm trying to get Nicotine running through unraid's wieguard VPN using the "vpn tunneled access for docker". I am not able to get port forwarding working. I added the port I wanted to forward to the docker template asI am otherwise connected through the VPN just fine.I was misreading my error logs. I kept seeing " UPnP: Failed to forward external port 2234: No UPnP devices found" and assumed my port forwarding wasn't working, completely ignoring the UPnP issue like a dummy. Edited December 16, 2025Dec 16 by naturalcarr
December 16, 2025Dec 16 Author 12 hours ago, naturalcarr said:Greetings all. I'm trying to get Nicotine running through unraid's wieguard VPN using the "vpn tunneled access for docker". I am not able to get port forwarding working. I added the port I wanted to forward to the docker template asI am otherwise connected through the VPN just fine.The UNRAID implementation of wireguard has no support for port forwarding at all, so you are out of luck. If you do want a working port forward then you will have to use the solution i came up with which involves gluetun and using that to get a working port forward established.12 hours ago, naturalcarr said:I was misreading my error logs. I kept seeing " UPnP: Failed to forward external port 2234: No UPnP devices found" and assumed my port forwarding wasn't working, completely ignoring the UPnP issue like a dummy.You should ignore uPnP, that would only work in a traditional port forward defined on your router, but as you are using a vpn this does not work, you need to get the port forward established at the vpn end, for soluton see above.
January 20Jan 20 On 12/16/2025 at 3:46 AM, binhex said:The UNRAID implementation of wireguard has no support for port forwarding at all, so you are out of luck. If you do want a working port forward then you will have to use the solution i came up with which involves gluetun and using that to get a working port forward established.You should ignore uPnP, that would only work in a traditional port forward defined on your router, but as you are using a vpn this does not work, you need to get the port forward established at the vpn end, for soluton see above.Aloha, thank you for your response earlier, I started to look up that exact method and thats how I have it setup currently with SLSKD. I wanted to know if there's a way to get Nicotine+ to work with/produce a SLSKD apikey. I ended up going primarily to SLSKD so I can use it with soularr, but I prefer Nicotine+ in every way.
January 28Jan 28 Author On 1/20/2026 at 9:06 PM, ThermodynamicEntropy said:I wanted to know if there's a way to get Nicotine+ to work with/produce a SLSKD apikeynope, nicotine+ has no api, so you are out of luck.
February 4Feb 4 On 1/28/2026 at 7:37 AM, binhex said:nope, nicotine+ has no api, so you are out of luck.Thank you, this has actually pushed me to Nicotine after some though on whether I really want my music collection to be automated. That being said, is there a way to connect to the tigerVNC server using my own VNCViewer client? I tried RealVNC, TightVNC and TigerVNC and they all say the connection is being actively refused by the computer.
February 5Feb 5 Author 13 hours ago, ThermodynamicEntropy said:Thank you, this has actually pushed me to Nicotine after some though on whether I really want my music collection to be automated. That being said, is there a way to connect to the tigerVNC server using my own VNCViewer client? I tried RealVNC, TightVNC and TigerVNC and they all say the connection is being actively refused by the computerhttps://github.com/binhex/arch-nicotineplus#access-via-vnc-client
February 5Feb 5 3 hours ago, binhex said:https://github.com/binhex/arch-nicotineplus#access-via-vnc-clientThank you, I did check that earlier, but I now I realize my issue was trying to connect via VNC while the container was routed through Gluetun. I am able to connect normally while on a bridge network, but nothing (connection refused) when I run it through Gluetun. Would you have any insight on getting these working together? (Nicotine_ through Gluetun accessed on a VNC client) Edited February 5Feb 5 by ThermodynamicEntropy
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.