nekromantik
-
Posts
258 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by nekromantik
-
-
@binhex The issue for me seems to be if I use my custom bridge it only listens on IPV6 and not IPV4. If I use normal bridged mode it listens on both. Only seem s to happen with this 1 application. Your deluge container works fine on my setup as do all other containers. Its just Qbitorrent that seems to only want IPV6 if I use my custom bridge network.
-
hi i am trying the qbittorrent image and? I am getting following error as its using IPv6 for some reason which I dont use:
Tue Feb 26 19:13:01 2019 TUN/TAP device tun0 opened Tue Feb 26 19:13:01 2019 TUN/TAP TX queue length set to 100 Tue Feb 26 19:13:01 2019 do_ifconfig, tt->did_ifconfig_ipv6_setup=1 Tue Feb 26 19:13:01 2019 /sbin/ip link set dev tun0 up mtu 1500 Tue Feb 26 19:13:01 2019 /sbin/ip addr add dev tun0 10.x.x.x/16 broadcast xx.xx.255.255 Tue Feb 26 19:13:01 2019 /sbin/ip -6 addr add fdda:d0d0:cafe:1301::1006/64 dev tun0 RTNETLINK answers: Permission denied Tue Feb 26 19:13:01 2019 Linux ip -6 addr add failed: external program exited with error status: 2 Tue Feb 26 19:13:01 2019 Exiting due to fatal errorHow do I stop the container using IPv6?
-
Nope I followed that exact page for mine.thought i would have a play and see if i can replicate the issue, in short i cant. i followed the procedure as layed out in this thread to create a custom bridge and then allocated the qbittorrent a static ip from that new bridge network and selected it from the dropdown for the container, applied it and it still worked just fine, perhaps you are creating the custom bridge differently?.
this is the thread i followed, a little old but still fairly up to date:-
https://forums.unraid.net/topic/70906-added-in-651-docker-user-defined-bridge-networks/
This is very odd.
Sent from my Pixel 2 XL using Tapatalk
-
9 minutes ago, binhex said:
Ok it's got me beat then all I can do is confirm that it does work and I have plenty of users using this sorry dude
Sent from my EML-L29 using Tapatalk
I found the issue
It only works if you use bridge mode.
If you choose custom bridge it wont accept username and password.
can you look into this?
-
Just now, binhex said:
try toggling privileged mode off then back on again and see if that fixes it as your symptom is normally related to privileged mode being off
Sent from my EML-L29 using Tapatalk
tried that did not help
also tried deleting the container and image and fresh start
-
anyone else have default user and password not working?
this is very frustrating as much prefer qbittorrent over deluge but deluge only one that works for me
-
2 minutes ago, binhex said:
ok can you attach that file here.
[AutoRun] enabled=false program= [Preferences] Connection\PortRangeMin=6881 Connection\UPnP=false General\Locale=en General\UseRandomPort=false WebUI\Address=* WebUI\CSRFProtection=false WebUI\LocalHostAuth=false WebUI\Port=8080 WebUI\ServerDomains=* WebUI\UseUPnP=false -
6 minutes ago, binhex said:
i dont think debug will show us anything new, if you can access the web ui then the vpn is running corrctly. ok can you stop the container and then delete the file /config/qBittorrent/config/qBittorrent.conf then start the container again, then try logging in again.
tried and same issue
-
39 minutes ago, binhex said:
@nekromantik actully i dont believe this is the issue, if you dont have debug on then this will be the last visible message you will recieve so im firly confident its running as expected.
so onto the issue then, so you say you cant login to the web ui, but you can see the initial login screen correct?, just when you enter in username admin (all lower case) and password adminadmin (all lower case) then it doesnt let you login right?
Correct username and password does not work.
I can enable debug and post log if you want to see it.
-
@binhex any clue?
-
-
@binhexdid you get chance to look at log output I posted?
-
7 hours ago, binhex said:
guessing here (no log so i cant tell for sure), but i would think you dont have --privileged=true set
here is log, privledge mode is on
QuoteCreated by...
___. .__ .__
\_ |__ |__| ____ | |__ ____ ___ ___
| __ \| |/ \| | \_/ __ \\ \/ /
| \_\ \ | | \ Y \ ___/ > <
|___ /__|___| /___| /\___ >__/\_ \
\/ \/ \/ \/ \/
https://hub.docker.com/u/binhex/
2019-02-11 17:58:14.258073 [info] System information Linux f0d202f63a06 4.19.20-Unraid #1 SMP Sat Feb 9 12:34:16 PST 2019 x86_64 GNU/Linux
2019-02-11 17:58:14.280604 [info] PUID defined as '99'
2019-02-11 17:58:14.380543 [info] PGID defined as '100'
2019-02-11 17:58:14.527336 [info] UMASK defined as '000'
2019-02-11 17:58:14.548747 [info] Permissions already set for volume mappings
2019-02-11 17:58:14.573978 [info] VPN_ENABLED defined as 'yes'
2019-02-11 17:58:14.600536 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/mullvad_cz.ovpn
dos2unix: converting file /config/openvpn/mullvad_cz.ovpn to Unix format...
2019-02-11 17:58:14.633699 [info] VPN remote line defined as 'remote cz.mullvad.net 1301'
2019-02-11 17:58:14.656239 [info] VPN_REMOTE defined as 'cz.mullvad.net'
2019-02-11 17:58:14.678235 [info] VPN_PORT defined as '1301'
2019-02-11 17:58:14.703664 [info] VPN_PROTOCOL defined as 'udp'
2019-02-11 17:58:14.725581 [info] VPN_DEVICE_TYPE defined as 'tun0'
2019-02-11 17:58:14.747224 [info] VPN_PROV defined as 'custom'
2019-02-11 17:58:14.768902 [info] LAN_NETWORK defined as '192.168.1.0/24, 192.168.10.0/24, 192.168.20.0/24'
2019-02-11 17:58:14.790439 [info] NAME_SERVERS defined as '209.222.18.222,37.235.1.174,1.1.1.1,8.8.8.8,209.222.18.218,37.235.1.177,1.0.0.1,8.8.4.4'
2019-02-11 17:58:14.811871 [info] VPN_USER defined as 'x'
2019-02-11 17:58:14.833512 [info] VPN_PASS defined as 'x'
2019-02-11 17:58:14.855026 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
2019-02-11 17:58:14.876855 [info] ENABLE_PRIVOXY defined as 'yes'
2019-02-11 17:58:14.898631 [info] WEBUI_PORT defined as '8080'
2019-02-11 17:58:14.925377 [info] Starting Supervisor...
2019-02-11 17:58:15,202 INFO Included extra file "/etc/supervisor/conf.d/qbittorrent.conf" during parsing
2019-02-11 17:58:15,202 INFO Set uid to user 0 succeeded
2019-02-11 17:58:15,204 INFO supervisord started with pid 6
2019-02-11 17:58:16,206 INFO spawned: 'start-script' with pid 141
2019-02-11 17:58:16,207 INFO spawned: 'watchdog-script' with pid 142
2019-02-11 17:58:16,208 INFO spawned: 'privoxy-script' with pid 143
2019-02-11 17:58:16,208 INFO reaped unknown pid 7
2019-02-11 17:58:16,212 DEBG 'start-script' stdout output:
[info] VPN is enabled, beginning configuration of VPN
2019-02-11 17:58:16,212 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2019-02-11 17:58:16,212 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2019-02-11 17:58:16,212 INFO success: privoxy-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2019-02-11 17:58:16,213 DEBG 'watchdog-script' stdout output:
[info] qBittorrent config file already exists, skipping copy
[info] Removing session lock file (if it exists)...
2019-02-11 17:58:16,215 DEBG 'watchdog-script' stderr output:
dos2unix: converting file /config/qBittorrent/config/qBittorrent.conf to Unix format...
2019-02-11 17:58:16,258 DEBG 'start-script' stdout output:
[info] Default route for container is 192.168.1.1
2019-02-11 17:58:16,261 DEBG 'start-script' stdout output:
[info] Adding 209.222.18.222 to /etc/resolv.conf
2019-02-11 17:58:16,263 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.174 to /etc/resolv.conf
2019-02-11 17:58:16,266 DEBG 'start-script' stdout output:
[info] Adding 1.1.1.1 to /etc/resolv.conf
2019-02-11 17:58:16,268 DEBG 'start-script' stdout output:
[info] Adding 8.8.8.8 to /etc/resolv.conf
2019-02-11 17:58:16,270 DEBG 'start-script' stdout output:
[info] Adding 209.222.18.218 to /etc/resolv.conf
2019-02-11 17:58:16,273 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.177 to /etc/resolv.conf
2019-02-11 17:58:16,275 DEBG 'start-script' stdout output:
[info] Adding 1.0.0.1 to /etc/resolv.conf
2019-02-11 17:58:16,278 DEBG 'start-script' stdout output:
[info] Adding 8.8.4.4 to /etc/resolv.conf
2019-02-11 17:58:16,497 DEBG 'start-script' stdout output:
[info] Attempting to load iptable_mangle module...
2019-02-11 17:58:16,498 DEBG 'start-script' stderr output:
modprobe: FATAL: Module iptable_mangle not found in directory /lib/modules/4.19.20-Unraid
2019-02-11 17:58:16,498 DEBG 'start-script' stdout output:
[warn] Unable to load iptable_mangle module using modprobe, trying insmod...
2019-02-11 17:58:16,498 DEBG 'start-script' stderr output:
insmod: ERROR: could not load module /lib/modules/iptable_mangle.ko: No such file or directory
2019-02-11 17:58:16,498 DEBG 'start-script' stdout output:
[warn] Unable to load iptable_mangle module, you will not be able to connect to the applications Web UI or Privoxy outside of your LAN
[info] unRAID/Ubuntu users: Please attempt to load the module by executing the following on your host: '/sbin/modprobe iptable_mangle'
[info] Synology users: Please attempt to load the module by executing the following on your host: 'insmod /lib/modules/iptable_mangle.ko'
2019-02-11 17:58:16,512 DEBG 'start-script' stdout output:
[info] Docker network defined as 192.168.1.0/24
2019-02-11 17:58:16,514 DEBG 'start-script' stdout output:
[info] Adding 192.168.1.0/24 as route via docker lan interface
2019-02-11 17:58:16,515 DEBG 'start-script' stderr output:
RTNETLINK answers: File exists
2019-02-11 17:58:16,518 DEBG 'start-script' stdout output:
[info] Adding 192.168.10.0/24 as route via docker lan interface
2019-02-11 17:58:16,521 DEBG 'start-script' stdout output:
[info] Adding 192.168.20.0/24 as route via docker lan interface
2019-02-11 17:58:16,522 DEBG 'start-script' stdout output:
[info] ip route defined as follows...
--------------------
2019-02-11 17:58:16,522 DEBG 'start-script' stdout output:
default via 192.168.1.1 dev eth0
192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.71
192.168.10.0/24 via 192.168.1.1 dev eth0
192.168.20.0/24 via 192.168.1.1 dev eth0
2019-02-11 17:58:16,522 DEBG 'start-script' stdout output:
--------------------
2019-02-11 17:58:16,567 DEBG 'start-script' stdout output:
[info] iptables defined as follows...
--------------------
2019-02-11 17:58:16,568 DEBG 'start-script' stdout output:
-P INPUT DROP
-P FORWARD ACCEPT
-P OUTPUT DROP
-A INPUT -i tun0 -j ACCEPT
-A INPUT -s 192.168.1.0/24 -d 192.168.1.0/24 -j ACCEPT
-A INPUT -i eth0 -p udp -m udp --sport 1301 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --dport 8080 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --sport 8080 -j ACCEPT
-A INPUT -s 192.168.1.0/24 -i eth0 -p tcp -m tcp --dport 8080 -j ACCEPT
-A INPUT -s 192.168.1.0/24 -d 192.168.1.0/24 -i eth0 -p tcp -j ACCEPT
-A INPUT -s 192.168.10.0/24 -i eth0 -p tcp -m tcp --dport 8080 -j ACCEPT
-A INPUT -s 192.168.10.0/24 -d 192.168.1.0/24 -i eth0 -p tcp -j ACCEPT
-A INPUT -s 192.168.20.0/24 -i eth0 -p tcp -m tcp --dport 8080 -j ACCEPT
-A INPUT -s 192.168.20.0/24 -d 192.168.1.0/24 -i eth0 -p tcp -j ACCEPT
-A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A OUTPUT -o tun0 -j ACCEPT
-A OUTPUT -s 192.168.1.0/24 -d 192.168.1.0/24 -j ACCEPT
-A OUTPUT -o eth0 -p udp -m udp --dport 1301 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --dport 8080 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --sport 8080 -j ACCEPT
-A OUTPUT -d 192.168.1.0/24 -o eth0 -p tcp -m tcp --sport 8080 -j ACCEPT
-A OUTPUT -s 192.168.1.0/24 -d 192.168.1.0/24 -o eth0 -p tcp -j ACCEPT
-A OUTPUT -d 192.168.10.0/24 -o eth0 -p tcp -m tcp --sport 8080 -j ACCEPT
-A OUTPUT -s 192.168.1.0/24 -d 192.168.10.0/24 -o eth0 -p tcp -j ACCEPT
-A OUTPUT -d 192.168.20.0/24 -o eth0 -p tcp -m tcp --sport 8080 -j ACCEPT
-A OUTPUT -s 192.168.1.0/24 -d 192.168.20.0/24 -o eth0 -p tcp -j ACCEPT
-A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT
-A OUTPUT -o lo -j ACCEPT
2019-02-11 17:58:16,568 DEBG 'start-script' stdout output:
--------------------
2019-02-11 17:58:16,569 DEBG 'start-script' stdout output:
[info] Starting OpenVPN...
2019-02-11 17:58:16,585 DEBG 'start-script' stdout output:
Mon Feb 11 17:58:16 2019 WARNING: file 'credentials.conf' is group or others accessible
Mon Feb 11 17:58:16 2019 OpenVPN 2.4.6 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Apr 24 2018
Mon Feb 11 17:58:16 2019 library versions: OpenSSL 1.1.1a 20 Nov 2018, LZO 2.10
2019-02-11 17:58:16,586 DEBG 'start-script' stdout output:
[info] OpenVPN started
2019-02-11 17:58:16,586 DEBG 'start-script' stdout output:
Mon Feb 11 17:58:16 2019 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
2019-02-11 17:58:16,586 DEBG 'start-script' stdout output:
Mon Feb 11 17:58:16 2019 TCP/UDP: Preserving recently used remote address: [AF_INET]xx
Mon Feb 11 17:58:16 2019 Socket Buffers: R=[212992->1048576] S=[212992->1048576]
Mon Feb 11 17:58:16 2019 UDP link local: (not bound)
2019-02-11 17:58:16,587 DEBG 'start-script' stdout output:
Mon Feb 11 17:58:16 2019 UDP link remote: [AF_INET]185.156.174.170:1301
2019-02-11 17:58:16,622 DEBG 'start-script' stdout output:
Mon Feb 11 17:58:16 2019 TLS: Initial packet from [AF_INET]185.156.174.170:1301, sid=bc491c1d 48695aa9
2019-02-11 17:58:16,732 DEBG 'start-script' stdout output:
Mon Feb 11 17:58:16 2019 VERIFY OK: depth=2, C=SE, ST=Gotaland, L=Gothenburg, O=Amagicom AB, OU=Mullvad, CN=Mullvad Root CA v2, [email protected]
2019-02-11 17:58:16,732 DEBG 'start-script' stdout output:
Mon Feb 11 17:58:16 2019 VERIFY OK: depth=1, C=SE, ST=Gotaland, O=Amagicom AB, OU=Mullvad, CN=Mullvad Transition-Intermediate CA v1, [email protected]
2019-02-11 17:58:16,732 DEBG 'start-script' stdout output:
Mon Feb 11 17:58:16 2019 VERIFY KU OK
Mon Feb 11 17:58:16 2019 Validating certificate extended key usage
Mon Feb 11 17:58:16 2019 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
Mon Feb 11 17:58:16 2019 VERIFY EKU OK
Mon Feb 11 17:58:16 2019 VERIFY OK: depth=0, C=SE, ST=Gotaland, O=Amagicom AB, OU=Mullvad, CN=cz-prg-002.mullvad.net, [email protected]
2019-02-11 17:58:16,885 DEBG 'start-script' stdout output:
Mon Feb 11 17:58:16 2019 WARNING: 'link-mtu' is used inconsistently, local='link-mtu 1557', remote='link-mtu 1558'
Mon Feb 11 17:58:16 2019 WARNING: 'comp-lzo' is present in remote config but missing in local config, remote='comp-lzo'
2019-02-11 17:58:16,886 DEBG 'start-script' stdout output:
Mon Feb 11 17:58:16 2019 Control Channel: TLSv1.2, cipher TLSv1.2 DHE-RSA-AES256-GCM-SHA384, 4096 bit RSA
Mon Feb 11 17:58:16 2019 [cz-prg-002.mullvad.net] Peer Connection Initiated with [AF_INET]185.156.174.170:1301
2019-02-11 17:58:17,988 DEBG 'start-script' stdout output:
Mon Feb 11 17:58:17 2019 SENT CONTROL [cz-prg-002.mullvad.net]: 'PUSH_REQUEST' (status=1)
2019-02-11 17:58:22,130 DEBG 'start-script' stdout output:
Mon Feb 11 17:58:22 2019 SENT CONTROL [cz-prg-002.mullvad.net]: 'PUSH_REQUEST' (status=1)
2019-02-11 17:58:22,166 DEBG 'start-script' stdout output:
Mon Feb 11 17:58:22 2019 PUSH: Received control message: 'PUSH_REPLY,dhcp-option DNS xx redirect-gateway def1 bypass-dhcp,route-ipv6 0000::/2,route-ipv6 4000::/2,route-ipv6 8000::/2,route-ipv6 C000::/2,comp-lzo no,route-gateway xx,topology subnet,socket-flags TCP_NODELAY,ifconfig-ipv6 fdda:d0d0:cafe:1301::1007/64 fdda:d0d0:cafe:1301::,ifconfig xx 255.255.0.0,peer-id 7,cipher AES-256-GCM'
Mon Feb 11 17:58:22 2019 Pushed option removed by filter: 'route-ipv6 0000::/2'
Mon Feb 11 17:58:22 2019 Pushed option removed by filter: 'route-ipv6 4000::/2'
Mon Feb 11 17:58:22 2019 Pushed option removed by filter: 'route-ipv6 8000::/2'
Mon Feb 11 17:58:22 2019 Pushed option removed by filter: 'route-ipv6 C000::/2'
2019-02-11 17:58:22,166 DEBG 'start-script' stdout output:
Mon Feb 11 17:58:22 2019 Pushed option removed by filter: 'ifconfig-ipv6 fdda:d0d0:cafe:1301::1007/64 fdda:d0d0:cafe:1301::'
Mon Feb 11 17:58:22 2019 OPTIONS IMPORT: compression parms modified
Mon Feb 11 17:58:22 2019 OPTIONS IMPORT: --socket-flags option modified
Mon Feb 11 17:58:22 2019 NOTE: setsockopt TCP_NODELAY=1 failed
Mon Feb 11 17:58:22 2019 OPTIONS IMPORT: --ifconfig/up options modified
Mon Feb 11 17:58:22 2019 OPTIONS IMPORT: route options modified
Mon Feb 11 17:58:22 2019 OPTIONS IMPORT: route-related options modified
Mon Feb 11 17:58:22 2019 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
Mon Feb 11 17:58:22 2019 OPTIONS IMPORT: peer-id set
Mon Feb 11 17:58:22 2019 OPTIONS IMPORT: adjusting link_mtu to 1624
Mon Feb 11 17:58:22 2019 OPTIONS IMPORT: data channel crypto options modified
Mon Feb 11 17:58:22 2019 Data Channel: using negotiated cipher 'AES-256-GCM'
Mon Feb 11 17:58:22 2019 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Mon Feb 11 17:58:22 2019 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Mon Feb 11 17:58:22 2019 ROUTE_GATEWAY 192.168.1.1/255.255.255.0 IFACE=eth0 HWADDR=02:42:c0:a8:01:47
2019-02-11 17:58:22,166 DEBG 'start-script' stdout output:
Mon Feb 11 17:58:22 2019 TUN/TAP device tun0 opened
Mon Feb 11 17:58:22 2019 TUN/TAP TX queue length set to 100
Mon Feb 11 17:58:22 2019 do_ifconfig, tt->did_ifconfig_ipv6_setup=0
Mon Feb 11 17:58:22 2019 /usr/bin/ip link set dev tun0 up mtu 1500
2019-02-11 17:58:22,167 DEBG 'start-script' stdout output:
Mon Feb 11 17:58:22 2019 /usr/bin/ip addr add dev tun0 xx/16 broadcast xx
2019-02-11 17:58:22,168 DEBG 'start-script' stdout output:
Mon Feb 11 17:58:22 2019 /root/openvpnup.sh tun0 1500 1552 xx 255.255.0.0 init
2019-02-11 17:58:22,169 DEBG 'start-script' stdout output:
Mon Feb 11 17:58:22 2019 /usr/bin/ip route add xx via 192.168.1.1
2019-02-11 17:58:22,170 DEBG 'start-script' stdout output:
Mon Feb 11 17:58:22 2019 /usr/bin/ip route add 0.0.0.0/1 via xx
2019-02-11 17:58:22,171 DEBG 'start-script' stdout output:
Mon Feb 11 17:58:22 2019 /usr/bin/ip route add 128.0.0.0/1 via xx
2019-02-11 17:58:22,172 DEBG 'start-script' stdout output:
Mon Feb 11 17:58:22 2019 Initialization Sequence Completed
2019-02-11 17:58:22,267 DEBG 'privoxy-script' stdout output:
[info] Configuring Privoxy...
2019-02-11 17:58:22,273 DEBG 'watchdog-script' stdout output:
[info] qBittorrent listening interface IP 0.0.0.0 and VPN provider IP xx different, marking for reconfigure
2019-02-11 17:58:22,276 DEBG 'watchdog-script' stdout output:
[info] qBittorrent not running
2019-02-11 17:58:22,350 DEBG 'privoxy-script' stdout output:
[info] All checks complete, starting Privoxy...
2019-02-11 17:58:22,359 DEBG 'privoxy-script' stderr output:
2019-02-11 17:58:22.359 1469b8052100 Info: Privoxy version 3.0.26
2019-02-11 17:58:22.359 1469b8052100 Info: Program name: /usr/bin/privoxy
2019-02-11 17:58:22,466 DEBG 'start-script' stdout output:
[info] Successfully retrieved external IP address xx
xx
xx
xx
2019-02-11 17:58:22,466 DEBG 'start-script' stdout output:
/root/getvpnextip.sh: line 58: 216.239.34.10: command not found
2019-02-11 17:58:22,467 DEBG 'start-script' stdout output:
/root/getvpnextip.sh: line 59: 216.239.36.10: command not found
2019-02-11 17:58:22,467 DEBG 'start-script' stdout output:
/root/getvpnextip.sh: line 60: 216.239.38.10: command not found
2019-02-11 17:58:22,479 DEBG 'watchdog-script' stdout output:
[info] Removing session lock file (if it exists)...
2019-02-11 17:58:22,479 DEBG 'watchdog-script' stdout output:
[info] Attempting to start qBittorrent...
2019-02-11 17:58:23,062 DEBG 'watchdog-script' stdout output:
[info] qBittorrent process started
[info] Waiting for qBittorrent process to start listening on port 8080...
2019-02-11 17:58:23,062 DEBG 'watchdog-script' stdout output:
[info] qBittorrent process started
[info] Waiting for qBittorrent process to start listening on port 8080.. -
im also not been able to login using admin and adminadmin
i cant test further as I need to head to bed so turned it off and went back to deluge.
Any hints?
-
People who used both this and DelugeVPN, which torrent client do you prefer?
RTorrent or Deluge?
-
yeah i think if new version of plugin needs 6.7.0 then plugin should not be released until new version of Unraid is out.
-
Anyone else get issue of some torrents never connecting to peers or seeds?
Several times a torrent just stops doing anything even though the same torrent on my local torrent client connects to peers right away.
-
2 hours ago, soundfx said:
I have tried for 3 days to get access to NextCloud on my unRAID working from outside my network. Here's were I stand:
I have NextCloud up and working, I can access it from a browser on a connection within my own network using unraidIP:444
I can also access NextCloud from the android app when I'm connected to my own network using unraidIP:444 in the NextCloud app "Server address https://..." field.
I have LetsEncrypt setup and working (I think). I using DuckDNS and the duckdns validation method. Here is the log from my LetsEncrypt.
------------------------------------- _ () | | ___ _ __ | | / __| | | / \ | | \__ \ | | | () | |_| |___/ |_| \__/ Brought to you by linuxserver.io We gratefully accept donations at: https://www.linuxserver.io/donate/ ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 20-config: executing... [cont-init.d] 20-config: exited 0. [cont-init.d] 30-keygen: executing... using keys found in /config/keys [cont-init.d] 30-keygen: exited 0. [cont-init.d] 50-config: executing... Variables set: PUID=99 PGID=100 TZ=Australia/Sydney URL=workdamnit.duckdns.org SUBDOMAINS=wildcard EXTRA_DOMAINS= ONLY_SUBDOMAINS=true DHLEVEL=2048 VALIDATION=duckdns DNSPLUGIN= EMAIL=*******@gmail.com STAGING= 2048 bit DH parameters present SUBDOMAINS entered, processing Wildcard cert for only the subdomains of workdamnit.duckdns.org will be requested E-mail address entered: ******@gmail.com duckdns validation is selected the resulting certificate will only cover the subdomains due to a limitation of duckdns, so it is advised to set the root location to use www.subdomain.duckdns.org Certificate exists; parameters unchanged; starting nginx [cont-init.d] 50-config: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. Server readyI've tried a lot of different things to test that my DuckDNS is working but I'm not sure that it's actually doing what it's suppose to. If, when connected to my home network, I use workdamnit.duckdns.org it takes me to my modem/router login page. But using it outside my home network gets me nowhere.
My NextCloud config.php file looks like this:
<?php $CONFIG = array ( 'memcache.local' => '\\OC\\Memcache\\APCu', 'datadirectory' => '/data', 'instanceid' => 'ocd07n9t02sn', 'passwordsalt' => '********', 'secret' => '*********', 'trusted_domains' => array ( 0 => '192.168.0.142:444', 1 => 'nextcloud.server.com', ), 'overwrite.cli.url' => 'https://192.168.0.142:444', 'dbtype' => 'mysql', 'version' => '13.0.1.1', 'dbname' => 'nextcloud', 'dbhost' => '192.168.0.142:3305', 'dbport' => '', 'dbtableprefix' => 'oc_', 'dbuser' => '********', 'dbpassword' => '*******', 'installed' => true, );
I've tried so many different approaches, test, changes that I feel like the solution might be masked by a change I've made prior. Could someone give me a hand to fault find this? I've feel a little out of my depth but really want to make this happen.
You need to forward port 443 or whatever you choose on your router to your letsencrypt container IP and port. Then set up nginx on the container to use the ssl cert and forward to nextcloud container. there is a example nextcloud config you can use and edit on the letsencrypt container. you just need to copy it to correct location ie /config/nginx/site-confs.
-
I know its probably not going to happen but would there be any chance to create a version of this container with naxsi module built in?
-
hi all
i downloaded this container and went through initial set up wizard but it hangs after the remote access allow screen.
then all access I get forbidden on when trying to access web ui via container IP and port 8096.
-
5 minutes ago, binhex said:
define LAN_NETWORK with a comma between networks, this will then add both.
thanks
-
would it be possible to specify routes to add to the container?
for example my network has 2 different LAN network CIDRs.
I added a big enough range for LAN_NETWORK but it does not add a route to the container.
it adds a 192.168.1.0/24 route but I would need 192.168.20.0/24 also.
doing it manually is not good as it gets removed next time container is re created.
-
ignore
-
25 minutes ago, binhex said:
are you usng a vpn on your laptop? if not you are comparing apples with pears. it could be the tracker is blocking vpn ip ranges or it could be you have no incoming port which may be causing connectivity issues, are the trackers public or private?
yes I am using same VPN as container on laptop, to be 100% accurate I switched to same country as the container.
Laptop connects fine in all scenarios.
Its a public tracker not private.
Incoming port test in deluge passes with a green dot as I have set the same port in client as well as VPN provider.
[Support] binhex - qBittorrentVPN
in Docker Containers
Posted
Sent from my Pixel 2 XL using Tapatalk