August 28, 20241 yr On 8/26/2024 at 7:06 PM, binhex said: Please see Q24 from the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md Question about routing other containers related to VPN ports: So i am running the qbittorrenvpn docker which automatically assigns a VPN port to qbittorrent. So i can not use this port anymore for nicotine. The same should apply for PrivoxyVPN. If i already use that port for one application, i can not use it for a second one, right? So in this case, i would need to spin up another VPN container? Or would it be possible to run 2 different VPN connections inside a VPN container? Edited August 28, 20241 yr by MrSliff
August 28, 20241 yr Author 1 hour ago, MrSliff said: The same should apply for PrivoxyVPN. If i already use that port for one application, i can not use it for a second one, right? So in this case, i would need to spin up another VPN container? Or would it be possible to run 2 different VPN connections inside a VPN container? spin up another container is the only option in that scenario.
August 28, 20241 yr 1 hour ago, binhex said: spin up another container is the only option in that scenario. Ok, fine. Looking forward to your work on the dynamic port forwarding.
August 28, 20241 yr Hello. Since the last update, I can rarely access the web interface anymore. I've tried Chrome, Edge & Opera GX. They all open the same (see pic). I have restart the docker several times to get it to load correctly. Today, I can't get it to do it anymore. I've removed the docker, deleted the folder and reinstalled with no luck. Any suggestions? repository-diagnostics-20240828-1833.zip Edited August 28, 20241 yr by Keek Uras strange red line on original image
August 31, 20241 yr Author On 8/29/2024 at 12:34 AM, Keek Uras said: Hello. Since the last update, I can rarely access the web interface anymore. I've tried Chrome, Edge & Opera GX. They all open the same (see pic). I have restart the docker several times to get it to load correctly. Today, I can't get it to do it anymore. I've removed the docker, deleted the folder and reinstalled with no luck. Any suggestions? repository-diagnostics-20240828-1833.zip 306.04 kB · 0 downloads This is a bug in tigervnc, for now I've rolled it back to the previous version and rebuilt the image, so please do a pull to pick up the fixed image
August 31, 20241 yr 4 hours ago, binhex said: This is a bug in tigervnc, for now I've rolled it back to the previous version and rebuilt the image, so please do a pull to pick up the fixed image Thank you so much. That fixed the issue!
November 5, 20241 yr Do I understand correctly that I can assigne the VPN network of binhexQbittorentVPN to binhexNicotine+? I've setup binhexQbittorentVPN and it's working flawlessly, but when I put --network=container:binhex-qbittorrentvpn in Nicotine+ and network NONE, I can't access VNC. The container is running correctly I think as the log shows normal behavior. Is there anything special that I should do to get this working? I've also tried setting this up with a new docker network and Wireguard Docker VPN on the same network, but I have the same problem. In my mind I should maybe route something somewhere, but I'm too much of a newb to figure it out I guess
November 5, 20241 yr Author 48 minutes ago, kjettern said: Do I understand correctly that I can assigne the VPN network of binhexQbittorentVPN to binhexNicotine+? I've setup binhexQbittorentVPN and it's working flawlessly, but when I put --network=container:binhex-qbittorrentvpn in Nicotine+ and network NONE, I can't access VNC. The container is running correctly I think as the log shows normal behavior. Is there anything special that I should do to get this working? I've also tried setting this up with a new docker network and Wireguard Docker VPN on the same network, but I have the same problem. In my mind I should maybe route something somewhere, but I'm too much of a newb to figure it out I guess Please see Q24 from the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md
November 12, 20241 yr Hey Binhex, having some issues routing nicotine+ through qbit. It seems to connect to soulseek just fine; however i cant connect to my vnc server. I'm not entirely sure where i went wrong, i followed the guide through the FAQ. I've attached my supervisord.log file for nicotine+. Any help would be appreciated! Thank you in advance for all you do! supervisord.log
February 24, 20251 yr Hey, I've been running SoulSeek in a Windows 10 VM with the ports manually forwarded in my router. It's been working great, but this container was pretty easy to get running, and probably a hell of a lot more friendly on resources, so I'm trying to make the switch to it. Also would be nice to be able to queue downloads from my domain rather than the VNC window for my VM on my phone screen. I tried using the container with my actual publicIP and going into my router NAT settings to forward a free port to my unraid machine for Nicotine+, but even after doing so, it still says it's closed? Am I missing something stupid here? Soulseek/Nicotine+ makes you hard to find in search if you don't have open ports. I have your qbittorrent container setup with my ProtonVPN. I tried following your Q24 documentation to network share with qbit, but was too dumb to get it to work. I'm on Unraid7, so I just changed the network type on Nicotine+ to container, and binhex-qbit as the network container, and added the ports like you normally would on the documentation. This let me access the webgui from the nicotine+ port, but it takes me to "directory listing for /" and I have to click vnc.html or vnc_lite.html to actually get to the nicotine+ webgui (also it's a quarter size for some reason?). This is fine, and under network, my public IP address is the VPN address. However, the listening port is closed. If I look at the qbit logs to manually enter the ProtonVPN open port that your automatic matching does and use that in Nicotine+, it says it's already in use. Is that the problem MrSliff above was asking about where you said that spinning up another VPN container is the way to solve it? ProtonVPN only allows you a certain amount of logged-in devices, so I'm not sure it multiple containers would count each time. Sorry for rambling, let me know if I'm missing something obvious.
February 25, 20251 yr Author 16 hours ago, Friarsgate_Customs said: I tried using the container with my actual publicIP and going into my router NAT settings to forward a free port to my unraid machine for Nicotine+, but even after doing so, it still says it's closed? Am I missing something stupid here? did you add the port you forwarded on your router to the nicotine container? if not then that will be the issue, you need to edit the container, click add and add the port with your assigned port number.
March 8, 20251 yr Hi and first and foremost, thanks for your work. It would be very nice if that could be done a la binhex-qbitorrentvpn, I only really need a vpn for that and nicotine on my server. (In reference to one of your posts that I could not quote for some reason) Edited March 8, 20251 yr by MonadProxy
April 2, 20251 yr Not sure if this is an issue with the application or the container, but one thing I noticed is that non-roman characters are not rendered for me. I tried selecting a few different font options but all the Japanese characters I have for files show up as blocks. Some issue with font encoding but not sure where exactly the issue is coming from. I suspect it's something with the container as when I run nicotine locally everything works as expected. Maybe I need to download a language into the container?
June 17, 20251 yr Good morning. After the last update, my Nicotine web gui is blank.text error warn system array loginCreated by...___. .__ .__\_ |__ |__| ____ | |__ ____ ___ ___| __ \| |/ \| | \_/ __ \\ \/ /| \_\ \ | | \ Y \ ___/ > <|___ /__|___| /___| /\___ >__/\_ \\/ \/ \/ \/ \/https://hub.docker.com/u/binhex/2025-06-17 06:56:57.539461 [info] Host is running unRAID2025-06-17 06:56:57.551951 [info] System information: Linux b29e2e5d3409 6.6.68-Unraid #1 SMP PREEMPT_DYNAMIC Tue Dec 31 13:42:37 PST 2024 x86_64 GNU/Linux2025-06-17 06:56:57.564573 [info] Image tags: BASE_RELEASE_TAG=2025061403,INT_RELEASE_TAG=2025061403,IMAGE_RELEASE_TAG=test2025-06-17 06:56:57.606006 [info] PUID defined as '99'2025-06-17 06:57:00.193162 [info] PGID defined as '100'2025-06-17 06:57:03.515244 [info] UMASK defined as '000'2025-06-17 06:57:03.532906 [info] Permissions already set for '/config'2025-06-17 06:57:03.649172 [info] Deleting files in /tmp (non recursive)...2025-06-17 06:57:03.683852 [info] WEBPAGE_TITLE defined as 'Nicotine+'2025-06-17 06:57:03.704411 [info] ENABLE_STARTUP_SCRIPTS defined as 'no'[WARN] 2025-06-17 06:57:03 :: '/home/nobody' path already exists, renaming...[WARN] 2025-06-17 06:57:03 :: '/config/home' path already exists, skipping copy[WARN] 2025-06-17 06:57:03 :: Creating '-s' from '/config/home' to '/home/nobody'...2025-06-17 06:57:05.372993 [info] Starting Supervisor.../usr/lib/python3.13/site-packages/supervisor/options.py:13: UserWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html. The pkg_resources package is slated for removal as early as 2025-11-30. Refrain from using this package or pin to Setuptools<81.import pkg_resources2025-06-17 06:57:10,112 INFO Included extra file "/etc/supervisor/conf.d/novnc.conf" during parsing2025-06-17 06:57:10,112 INFO Set uid to user 0 succeeded2025-06-17 06:57:10,195 INFO RPC interface 'supervisor' initialized2025-06-17 06:57:10,195 CRIT Server 'unix_http_server' running without any HTTP authentication checking2025-06-17 06:57:10,195 INFO supervisord started with pid 72025-06-17 06:57:11,197 INFO spawned: 'start' with pid 902025-06-17 06:57:11,197 INFO reaped unknown pid 8 (exit status 0)2025-06-17 06:57:11,353 DEBG 'start' stdout output:[info] Self-signed certificate already exists, skipping generation...[info] Using self-signed certificate for websockify...2025-06-17 06:57:11,353 INFO success: start entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)2025-06-17 06:57:12,237 DEBG 'start' stderr output:_XSERVTransmkdir: ERROR: euid != 0,directory /tmp/.X11-unix will not be created.2025-06-17 06:57:12,237 DEBG 'start' stderr output:Xvnc TigerVNC 1.13.1 - built May 25 2024 17:13:24Copyright (C) 1999-2022 TigerVNC Team and many others (see README.rst)See https://www.tigervnc.org for information on TigerVNC.Underlying X server release 121010132025-06-17 06:57:12,237 DEBG 'start' stderr output:Tue Jun 17 06:57:12 2025vncext: VNC extension running!2025-06-17 06:57:12,237 DEBG 'start' stderr output:vncext: Listening for VNC connections on all interface(s), port 59002025-06-17 06:57:12,237 DEBG 'start' stderr output:vncext: created VNC server for screen 02025-06-17 06:57:12,472 DEBG 'start' stderr output:The XKEYBOARD keymap compiler (xkbcomp) reports:> Warning: Could not resolve keysym XF86RefreshRateToggle> Warning: Could not resolve keysym XF86Accessibility> Warning: Could not resolve keysym XF86DoNotDisturb2025-06-17 06:57:12,473 DEBG 'start' stderr output:Errors from xkbcomp are not fatal to the X server2025-06-17 06:57:12,474 DEBG 'start' stderr output:[mi] mieq: warning: overriding existing handler (nil) with 0x55a7d6dd36e0 for event 2[mi] mieq: warning: overriding existing handler (nil) with 0x55a7d6dd36e0 for event 32025-06-17 06:57:12,621 DEBG 'start' stderr output:ERROR: openbox-xdg-autostart requires PyXDG to be installed2025-06-17 06:57:12,623 DEBG 'start' stderr output:WebSocket server settings:2025-06-17 06:57:12,623 DEBG 'start' stderr output:- Listen on :6080- Web server. Web root: /usr/share/webapps/novnc2025-06-17 06:57:12,623 DEBG 'start' stderr output:- SSL/TLS support2025-06-17 06:57:12,623 DEBG 'start' stderr output:- proxying from :6080 to localhost:59002025-06-17 06:57:15,388 DEBG 'start' stdout output:[INFO] Downloading portset.sh from Github to '/usr/local/bin/portset.sh'...2025-06-17 06:57:15,436 DEBG 'start' stdout output:[INFO] Download attempt 1/10...2025-06-17 06:57:15,643 DEBG 'start' stdout output:[info] tint2 not running2025-06-17 06:57:16,142 DEBG 'start' stderr output:tint2: Using glib slice allocator (default). Run tint2 with environment variable G_SLICE=always-malloc in case of strange behavior or crashes2025-06-17 06:57:16,143 DEBG 'start' stderr output:tint2: xRandr: Found crtc's: 1tint2: xRandr: Linking output VNC-0 with crtc 0, resolution 1024x768, DPI 962025-06-17 06:57:16,143 DEBG 'start' stderr output:tint2: No XSETTINGS manager, tint2 uses config option 'launcher_icon_theme'.tint2: Loading config file: /home/nobody/.config/tint2/theme/tint2rc2025-06-17 06:57:16,144 DEBG 'start' stderr output:tint2: real transparency on... depth: 322025-06-17 06:57:16,160 DEBG 'start' stderr output:tint2: panel items: TSCtint2: Systray composited rendering ontint2: nb monitors 1, nb monitors used 1, nb desktops 4tint2: panel 1 uses scale 12025-06-17 06:57:16,193 DEBG 'start' stderr output:tint2: Kernel uevent interface initialized...2025-06-17 06:57:16,214 DEBG 'start' stderr output:tint2: systray window 8388621tint2: systray started2025-06-17 06:57:16,584 DEBG 'start' stdout output:[INFO] Download complete. Executing portset.sh with arguments provided...2025-06-17 06:57:16,596 DEBG 'start' stdout output:[INFO] No application name specified via argument '-an|--application-name' or environment variable 'APPLICATION_NAME', showing help...2025-06-17 06:57:16,603 DEBG 'start' stdout output:Description:A simple bash script to monitor the VPN incoming port from gluetun and configure a predefined list of applications.portset.sh 1.0.0 - Created by binhex.Syntax:./portset.sh [options] [command and arguments]Where:-an or --application-name <name>Define the name of the application to configure for incoming port.No default.-qcf or --qbittorrent-config-filepath <path>Define the file path to the qBittorrent configuration file.Defaults to '/config/qBittorrent/config/qBittorrent.conf'.-qwp or --qbittorrent-webui-port <port>Define the web UI port for qBittorrent.Defaults to '8080'.-qba or --qbittorrent-bind-adapter <yes|no>Define whether to bind qBittorrent to the gluetun network interface.Defaults to 'yes'.-gcsp or --gluetun-control-server-port <port>Define the Gluetun Control Server port.Defaults to '8000'.-cip or --configure-incoming-port <yes|no>Define whether to enable VPN port monitoring and application configuration.Defaults to 'yes'.-pd or --poll-delay <seconds>Define the polling delay in seconds between incoming port checks.Defaults to '10'.--debugDefine whether debug mode is enabled.Defautlts to not set.-h or --helpDisplays this text.Notes:- Any additional arguments provided after the options will be passed to the specified application.Environment Variables:APPLICATION_NAMESet the name of the application to configure with the VPN incoming port.QBITTORRENT_CONFIG_FILEPATHSet the file path to the qBittorrent configuration file.QBITTORRENT_WEBUI_PORTSet the web UI port for qBittorrent.QBITTORRENT_BIND_ADAPTERSet to the name of the application to configure with the VPN incoming port.GLUETUN_CONTROL_SERVER_PORTSet the port for the Gluetun Control Server.CONFIGURE_INCOMING_PORTSet to 'yes' to enable VPN port monitoring and application configuration.POLL_DELAYSet the polling delay in seconds between incoming port checks.DEBUGSet to 'yes' to enable debug mode.Notes:- Command line arguments take precedence over environment variables.Examples:Monitor VPN port and configure Nicotine+:./portset.sh /usr/bin/nicotineMonitor VPN port with custom settings:./portset.sh --gluetun-control-server-port 9000 --poll-delay 5 /usr/bin/qbittorrentSimply execute a command without VPN monitoring:./portset.sh /usr/bin/some-application --some-flagManually executing the script for debug:CONFIGURE_INCOMING_PORT=yes APPLICATION_NAME=nicotineplus ./portset.sh --debug /usr/bin/nicotine2025-06-17 06:57:16,603 DEBG 'start' stdout output:[INFO] Configuration of VPN incoming port is enabled, starting incoming port watchdog...2025-06-17 06:57:16,606 DEBG 'start' stdout output:[ERROR] Unable to connect to gluetun Control Server at 'http://127.0.0.1:8000/v1', are you running this container in the gluetun containers network?, exiting...2025-06-17 06:58:48,816 DEBG 'start' stderr output:172.16.0.134 - - [17/Jun/2025 06:58:48] code 404, message File not found2025-06-17 06:58:48,850 DEBG 'start' stderr output:172.16.0.134 - - [17/Jun/2025 06:58:48] code 404, message File not found2025-06-17 06:58:48,885 DEBG 'start' stderr output:172.16.0.134 - - [17/Jun/2025 06:58:48] 172.16.0.134: Plain non-SSL (ws://) WebSocket connection172.16.0.134 - - [17/Jun/2025 06:58:48] 172.16.0.134: Path: '/websockify'2025-06-17 06:58:48,885 DEBG 'start' stderr output:172.16.0.134 - - [17/Jun/2025 06:58:48] connecting to: localhost:59002025-06-17 06:58:48,947 DEBG 'start' stderr output:Tue Jun 17 06:58:48 2025Connections: accepted: 127.0.0.1::555642025-06-17 06:58:48,974 DEBG 'start' stderr output:SConnection: Client needs protocol version 3.82025-06-17 06:58:48,975 DEBG 'start' stderr output:SConnection: Client requests security type None(1)2025-06-17 06:58:48,977 DEBG 'start' stderr output:VNCSConnST: Server default pixel format depth 24 (32bpp) little-endian rgb8882025-06-17 06:58:48,986 DEBG 'start' stderr output:VNCSConnST: Client pixel format depth 24 (32bpp) little-endian bgr8882025-06-17 06:58:48,998 DEBG 'start' stderr output:/usr/src/debug/tint2/tint2/src/util/signals.c 160: triggering tint2 restart, reason: configuration change in the root windowComparingUpdateTracker: 0 pixels in / 0 pixels outComparingUpdateTracker: (1:-nan ratio)2025-06-17 06:58:49,011 DEBG 'start' stderr output:tint2: /usr/src/debug/tint2/tint2/src/main.c 786: restarting tint2...2025-06-17 06:58:49,012 DEBG 'start' stderr output:tint2: xRandr: Found crtc's: 1tint2: xRandr: Linking output VNC-0 with crtc 0, resolution 2539x1244, DPI 96tint2: No XSETTINGS manager, tint2 uses config option 'launcher_icon_theme'.tint2: Loading config file: /home/nobody/.config/tint2/theme/tint2rc2025-06-17 06:58:49,012 DEBG 'start' stderr output:tint2: real transparency on... depth: 322025-06-17 06:58:49,012 DEBG 'start' stderr output:tint2: panel items: TSCtint2: Systray composited rendering ontint2: nb monitors 1, nb monitors used 1, nb desktops 4tint2: panel 1 uses scale 12025-06-17 06:58:49,013 DEBG 'start' stderr output:tint2: Kernel uevent interface initialized...tint2: systray window 8388621I've removed and reinstalled the docker with the same result. Any help would be appreciated. Thanks! Edited June 17, 20251 yr by Keek Uras
June 17, 20251 yr I'm having the same "Unable to connect to gluetun Control Server" issue as Keek Uras. Been running fine for months now after I configured everything properly per binhex's instructions. My instance is really basic, just the container on my custom docker network, not ran through a VPN or anything, with a port opened on my router. I had it hosted through cloudflare, but at the moment neither cloudflare or the LAN address are working.
June 18, 20251 yr Author 17 hours ago, Friarsgate_Customs said:I'm having the same "Unable to connect to gluetun Control Server" issue as Keek Uras. Been running fine for months now after I configured everything properly per binhex's instructions. My instance is really basic, just the container on my custom docker network, not ran through a VPN or anything, with a port opened on my router. I had it hosted through cloudflare, but at the moment neither cloudflare or the LAN address are working.if you restart your container it should now allow it to run, this was an accidental inclusion of code which is not quite ready for prime time yet.
June 18, 20251 yr 1 hour ago, binhex said:if you restart your container it should now allow it to run, this was an accidental inclusion of code which is not quite ready for prime time yet.Thank you for the response. Unfortunately, restarting the container has the same result.
June 18, 20251 yr Just now, Keek Uras said:Thank you for the response. Unfortunately, restarting the container has the same result.nvm, it took a moment but finally loaded. Thanks!
July 21, 2025Jul 21 Author Please note this container now has built in gluetun support, please see Q9:- https://github.com/binhex/documentation/blob/master/docker/faq/unraid.md
September 12, 2025Sep 12 Using RealVNC to connect, resolution is stuck at 1024x768. Looks horrible. I have tried changing the scale from automatic to 100%. No change. How can I increase to 1920x1080? Thank you Edited September 12, 2025Sep 12 by spacebender
November 27, 2025Nov 27 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!
November 28, 2025Nov 28 23 hours ago, 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!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.
November 30, 2025Nov 30 On 11/27/2025 at 9:28 AM, 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!Checking in. Still having the same issue.
November 30, 2025Nov 30 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.4 hours ago, Keek Uras said:Checking in. Still having the same issue.looking into it guys
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.