starker3

Members
  • Posts

    2
  • Joined

  • Last visited

Posts posted by starker3

  1. 8 hours ago, wgstarks said:

    If you change the webui port to a custom port you need to create a new port mapping for that port. For mine I used port 8088 so i created another port mapping shown below-

    2137482099_ScreenShot2022-07-06at8_58_19PM.thumb.png.6954cd65c57c3eebdbf61c38e5c5e0d2.png

     

    The name is up to you. Just change 8088 to whatever port you're using.

     

    Edit: Actually, its been a while since I set this up but IIRC you need to delete the existing 8080:8080 port configuration (you can't edit it) and then create the new port configuration.

    Thanks for the tip. I hadn't read your reply earlier when I changed some things around, so I ended up changing the other docker that was using port 8080 to a different port to use the default port for qbittorrent.

     

    I was looking at a different template which uses a similar method that mentioned you can't bind a different host port to container port with the VPN setup as it causes a DNS rebinding issue. Using the default ports for the containers works though (And is probably why the others worked as is because none of those have different ports between container and host)

    • Like 1
  2. Hi everyone, I'm having an issue getting qbitorrent to connect from devices on the local network.

    I've setup the container with several other containers using it for its network connection (Using extra parameters).

     

    All of these other containers are working fine and I can connect to them without any issues, however the qbitorrent service itself seems to just time out.

     

    Here is the docker run command for the container:
     

    root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='binhex-qbittorrentvpn' --net='bridge' --privileged=true -e TZ="Pacific/Auckland" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Zeus" -e HOST_CONTAINERNAME="binhex-qbittorrentvpn" -e 'VPN_ENABLED'='yes' -e 'VPN_USER'='$USER' -e 'VPN_PASS'='$PASS' -e 'VPN_PROV'='custom' -e 'VPN_CLIENT'='openvpn' -e 'VPN_OPTIONS'='' -e 'STRICT_PORT_FORWARD'='yes' -e 'ENABLE_PRIVOXY'='no' -e 'WEBUI_PORT'='9514' -e 'LAN_NETWORK'='192.168.50.0/24,10.242.0.0/16,172.0.0.0/8,10.8.0.0/16' -e 'NAME_SERVERS'='84.200.69.80,37.235.1.174,1.1.1.1,37.235.1.177,84.200.70.40,1.0.0.1' -e 'VPN_INPUT_PORTS'='8989,9696,6789,7878,9514' -e 'VPN_OUTPUT_PORTS'='32400,8096' -e 'DEBUG'='true' -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:8080]/' -l net.unraid.docker.icon='https://raw.githubusercontent.com/binhex/docker-templates/master/binhex/images/qbittorrent-icon.png' -p '6881:6881/tcp' -p '6881:6881/udp' -p '9514:8080/tcp' -p '8118:8118/tcp' -p '8989:8989/tcp' -p '9696:9696/tcp' -p '6789:6789/tcp' -p '7878:7878/tcp' -v '/mnt/user/appdata/data':'/data':'rw' -v '/mnt/user/appdata/binhex-qbittorrentvpn':'/config':'rw' --sysctl="net.ipv4.conf.all.src_valid_mark=1" 'binhex/arch-qbittorrentvpn'
    
    512a9e1237796a72dff020a8c145c86d6a55a215a608edf9608b14864c11d372

     

    As you can see I've set the port to a different port since 8080 is in use on the unraid host.
     

    The debug logs when starting (Showing that qbittorrent starts and listens on the correct port):

    2022-07-07 12:20:31,186 DEBG 'watchdog-script' stdout output:
    [info] Attempting to start qBittorrent...
    
    2022-07-07 12:20:31,195 DEBG 'watchdog-script' stdout output:
    [info] qBittorrent process started
    [info] Waiting for qBittorrent process to start listening on port 9514...
    
    2022-07-07 12:20:31,300 DEBG 'watchdog-script' stdout output:
    [info] qBittorrent process listening on port 9514
    [debug] VPN IP is 172.21.56.65
    [debug] qBittorrent IP is 172.21.56.65

     

    Anyone know what I can do to be able to connect to the qbitorrent web UI?