Jump to content

Wob76

Members
  • Content Count

    194
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Wob76

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Yeah, I also tried an alternative browser, it's odd, 2.0 without VPN (PIA) works fine, v1 with VPN (PIA) no problem, only change between them is the repository being pulled. Are those with it working use PIA or another VPN provider? I'll investigate further at some point but for now I'm happy with v1, might wait for the plugin support to be ported. Thanks for the help. Sent from my Pixel 3 XL using Tapatalk
  2. I can't access the web UI with 2.0, but rolling back fixes it, did the configuration requirements change? Sent from my Pixel 3 XL using Tapatalk
  3. Good to know, so does the web GUI fall into the 3rd party plugin category? Wob Sent from my Pixel 3 XL using Tapatalk
  4. So rolling back to binhex/arch-delugevpn:1.3.15_18_ge050905b2-1-04 fixes my issue, but it's not just the deluge port that isn't working, I can't connect to the web socket or the privoxy ports, logs are not giving me much indication of the issue. Wob
  5. I tried directly on the docket port for the web, I usually access via reverse proxy, neither work. With VPN on I don't see any activity in the deluge web log. Here is the run command, but it hasn't been changed in months so I don't think it's the issue. docker run -d --name='delugevpn' --net='bridge' --log-opt max-size='50m' --log-opt max-file='3' --privileged=true -e TZ="Australia/Sydney" -e HOST_OS="Unraid" -e 'VPN_ENABLED'='yes' -e 'VPN_USER'='XXXX' -e 'VPN_PASS'='XXXX' -e 'VPN_PROV'='pia' -e 'VPN_OPTIONS'='' -e 'STRICT_PORT_FORWARD'='yes' -e 'ENABLE_PRIVOXY'='yes' -e 'LAN_NETWORK'='192.168.0.0/24' -e 'NAME_SERVERS'='209.222.18.222,1.1.1.1,8.8.8.8,209.222.18.218,1.0.0.1,8.8.4.4' -e 'DEBUG'='false' -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -p '8112:8112/tcp' -p '58846:58846/tcp' -p '58946:58946/tcp' -p '58946:58946/udp' -p '8118:8118/tcp' -v '/mnt/user/downloads/':'/data':'rw' -v '/mnt/user/downloads/':'/downloads':'rw' -v '/mnt/user/appdata/delugevpn':'/config':'rw' 'binhex/arch-delugevpn' I'll also try the updated thin client tomorrow to see if the deluge port is open, but to me it seems like none of the ports are open while the VPN is up. Sent from my Pixel 3 XL using Tapatalk
  6. I'm just trying to access the web GUI and I get nothing with the VPN on, I did try the windows app but it is probably outdated, I first noticed the issue as SickChill had an issue pushing a download to it. It was working find just a few days ago, but I can't work out if the issue is from the update or if it's a PIA issue. Sent from my Pixel 3 XL using Tapatalk
  7. As with a few others I seem to be having problems with PIA, It's been running fine since I moved from rutorrent around December last year, but stopped today after updating the docker yesterday. I have rolled back 2 versions and still can't get to the GUI and other dockers can't send torrents to it, I also tried a different PIA server to see if that was the issue without success. If I disable the VPN the GUI works. No sign of any issues within the logs that I can see. supervisord.log (VPN USER\PASS Masked) Created by... ___. .__ .__ \_ |__ |__| ____ | |__ ____ ___ ___ | __ \| |/ \| | \_/ __ \\ \/ / | \_\ \ | | \ Y \ ___/ > < |___ /__|___| /___| /\___ >__/\_ \ \/ \/ \/ \/ \/ https://hub.docker.com/u/binhex/ 2019-07-16 11:53:31.684483 [info] System information Linux b50183129941 4.19.41-Unraid #1 SMP Wed May 8 14:23:25 PDT 2019 x86_64 GNU/Linux 2019-07-16 11:53:31.739405 [info] PUID defined as '99' 2019-07-16 11:53:31.778824 [info] PGID defined as '100' 2019-07-16 11:53:31.880990 [info] UMASK defined as '000' 2019-07-16 11:53:31.910583 [info] Permissions already set for volume mappings 2019-07-16 11:53:31.944029 [info] DELUGE_DAEMON_LOG_LEVEL not defined,(via -e DELUGE_DAEMON_LOG_LEVEL), defaulting to 'info' 2019-07-16 11:53:31.975033 [info] DELUGE_WEB_LOG_LEVEL not defined,(via -e DELUGE_WEB_LOG_LEVEL), defaulting to 'info' 2019-07-16 11:53:32.005984 [info] VPN_ENABLED defined as 'yes' 2019-07-16 11:53:32.044512 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/openvpn.ovpn dos2unix: converting file /config/openvpn/openvpn.ovpn to Unix format... 2019-07-16 11:53:32.090271 [info] VPN remote line defined as 'remote ca-toronto.privateinternetaccess.com 1198' 2019-07-16 11:53:32.122070 [info] VPN_REMOTE defined as 'ca-toronto.privateinternetaccess.com' 2019-07-16 11:53:32.154766 [info] VPN_PORT defined as '1198' 2019-07-16 11:53:32.189617 [info] VPN_PROTOCOL defined as 'udp' 2019-07-16 11:53:32.222186 [info] VPN_DEVICE_TYPE defined as 'tun0' 2019-07-16 11:53:32.253393 [info] VPN_PROV defined as 'pia' 2019-07-16 11:53:32.290793 [info] LAN_NETWORK defined as '192.168.0.0/24' 2019-07-16 11:53:32.327020 [info] NAME_SERVERS defined as '209.222.18.222,1.1.1.1,8.8.8.8,209.222.18.218,1.0.0.1,8.8.4.4' 2019-07-16 11:53:32.361452 [info] VPN_USER defined as 'XXXX' 2019-07-16 11:53:32.394370 [info] VPN_PASS defined as 'XXXX' 2019-07-16 11:53:32.426857 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS) 2019-07-16 11:53:32.463078 [info] STRICT_PORT_FORWARD defined as 'yes' 2019-07-16 11:53:32.496076 [info] ENABLE_PRIVOXY defined as 'yes' 2019-07-16 11:53:32.530811 [info] Starting Supervisor... 2019-07-16 11:53:32,723 INFO Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing 2019-07-16 11:53:32,723 INFO Set uid to user 0 succeeded 2019-07-16 11:53:32,725 INFO supervisord started with pid 6 2019-07-16 11:53:33,728 INFO spawned: 'start-script' with pid 147 2019-07-16 11:53:33,729 INFO spawned: 'watchdog-script' with pid 148 2019-07-16 11:53:33,730 INFO reaped unknown pid 7 2019-07-16 11:53:33,736 DEBG 'start-script' stdout output: [info] VPN is enabled, beginning configuration of VPN 2019-07-16 11:53:33,736 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2019-07-16 11:53:33,736 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2019-07-16 11:53:33,738 DEBG 'watchdog-script' stderr output: dos2unix: converting file /config/core.conf to Unix format... 2019-07-16 11:53:33,789 DEBG 'start-script' stdout output: [info] Default route for container is 172.17.0.1 2019-07-16 11:53:33,792 DEBG 'start-script' stdout output: [info] Adding 209.222.18.222 to /etc/resolv.conf 2019-07-16 11:53:33,796 DEBG 'start-script' stdout output: [info] Adding 1.1.1.1 to /etc/resolv.conf 2019-07-16 11:53:33,799 DEBG 'start-script' stdout output: [info] Adding 8.8.8.8 to /etc/resolv.conf 2019-07-16 11:53:33,803 DEBG 'start-script' stdout output: [info] Adding 209.222.18.218 to /etc/resolv.conf 2019-07-16 11:53:33,806 DEBG 'start-script' stdout output: [info] Adding 1.0.0.1 to /etc/resolv.conf 2019-07-16 11:53:33,810 DEBG 'start-script' stdout output: [info] Adding 8.8.4.4 to /etc/resolv.conf 2019-07-16 11:53:33,853 DEBG 'start-script' stdout output: [info] Docker network defined as 172.17.0.0/16 2019-07-16 11:53:33,856 DEBG 'start-script' stdout output: [info] Adding 192.168.0.0/24 as route via docker eth0 2019-07-16 11:53:33,858 DEBG 'start-script' stdout output: [info] ip route defined as follows... -------------------- 2019-07-16 11:53:33,858 DEBG 'start-script' stdout output: default via 172.17.0.1 dev eth0 172.17.0.0/16 dev eth0 proto kernel scope link src 172.17.0.4 192.168.0.0/24 via 172.17.0.1 dev eth0 2019-07-16 11:53:33,859 DEBG 'start-script' stdout output: -------------------- 2019-07-16 11:53:33,861 DEBG 'start-script' stdout output: iptable_mangle 16384 1 ip_tables 24576 3 iptable_filter,iptable_nat,iptable_mangle 2019-07-16 11:53:33,862 DEBG 'start-script' stdout output: [info] iptable_mangle support detected, adding fwmark for tables 2019-07-16 11:53:33,898 DEBG 'start-script' stdout output: [info] iptables defined as follows... -------------------- 2019-07-16 11:53:33,899 DEBG 'start-script' stdout output: -P INPUT DROP -P FORWARD DROP -P OUTPUT DROP -A INPUT -i tun0 -j ACCEPT -A INPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT -A INPUT -i eth0 -p udp -m udp --sport 1198 -j ACCEPT -A INPUT -i eth0 -p tcp -m tcp --dport 8112 -j ACCEPT -A INPUT -i eth0 -p tcp -m tcp --sport 8112 -j ACCEPT -A INPUT -s 192.168.0.0/24 -i eth0 -p tcp -m tcp --dport 58846 -j ACCEPT -A INPUT -s 192.168.0.0/24 -d 172.17.0.0/16 -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 -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT -A OUTPUT -o eth0 -p udp -m udp --dport 1198 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --dport 8112 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --sport 8112 -j ACCEPT -A OUTPUT -d 192.168.0.0/24 -o eth0 -p tcp -m tcp --sport 58846 -j ACCEPT -A OUTPUT -s 172.17.0.0/16 -d 192.168.0.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 -A OUTPUT -o tun0 -j ACCEPT 2019-07-16 11:53:33,900 DEBG 'start-script' stdout output: -------------------- 2019-07-16 11:53:33,901 DEBG 'start-script' stdout output: [info] Starting OpenVPN... 2019-07-16 11:53:33,908 DEBG 'start-script' stdout output: Tue Jul 16 11:53:33 2019 WARNING: file 'credentials.conf' is group or others accessible Tue Jul 16 11:53:33 2019 OpenVPN 2.4.7 [git:makepkg/2b8aec62d5db2c17+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Feb 19 2019 Tue Jul 16 11:53:33 2019 library versions: OpenSSL 1.1.1c 28 May 2019, LZO 2.10 2019-07-16 11:53:33,909 DEBG 'start-script' stdout output: [info] OpenVPN started Tue Jul 16 11:53:33 2019 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts 2019-07-16 11:53:33,910 DEBG 'start-script' stdout output: Tue Jul 16 11:53:33 2019 TCP/UDP: Preserving recently used remote address: [AF_INET]172.98.67.107:1198 2019-07-16 11:53:33,910 DEBG 'start-script' stdout output: Tue Jul 16 11:53:33 2019 UDP link local: (not bound) Tue Jul 16 11:53:33 2019 UDP link remote: [AF_INET]172.98.67.107:1198 2019-07-16 11:53:34,796 DEBG 'start-script' stdout output: Tue Jul 16 11:53:34 2019 [dfa7c579c79a374870350adc620b3760] Peer Connection Initiated with [AF_INET]172.98.67.107:1198 2019-07-16 11:53:36,271 DEBG 'start-script' stdout output: Tue Jul 16 11:53:36 2019 TUN/TAP device tun0 opened Tue Jul 16 11:53:36 2019 /usr/bin/ip link set dev tun0 up mtu 1500 2019-07-16 11:53:36,272 DEBG 'start-script' stdout output: Tue Jul 16 11:53:36 2019 /usr/bin/ip addr add dev tun0 local 10.22.10.14 peer 10.22.10.13 2019-07-16 11:53:36,273 DEBG 'start-script' stdout output: Tue Jul 16 11:53:36 2019 /root/openvpnup.sh tun0 1500 1558 10.22.10.14 10.22.10.13 init 2019-07-16 11:53:36,279 DEBG 'start-script' stdout output: Tue Jul 16 11:53:36 2019 Initialization Sequence Completed 2019-07-16 11:53:36,394 DEBG 'start-script' stdout output: [info] Attempting to curl https://www.privateinternetaccess.com/vpninfo/servers?version=82... 2019-07-16 11:53:38,815 DEBG 'start-script' stdout output: [info] Curl successful for https://www.privateinternetaccess.com/vpninfo/servers?version=82, response code 200 2019-07-16 11:53:38,886 DEBG 'start-script' stdout output: [info] List of PIA endpoints that support port forwarding:- [info] ca-toronto.privateinternetaccess.com [info] ca-montreal.privateinternetaccess.com [info] ca-vancouver.privateinternetaccess.com [info] de-berlin.privateinternetaccess.com [info] de-frankfurt.privateinternetaccess.com 2019-07-16 11:53:38,887 DEBG 'start-script' stdout output: [info] sweden.privateinternetaccess.com [info] swiss.privateinternetaccess.com [info] france.privateinternetaccess.com [info] czech.privateinternetaccess.com [info] spain.privateinternetaccess.com [info] ro.privateinternetaccess.com [info] israel.privateinternetaccess.com 2019-07-16 11:53:38,891 DEBG 'start-script' stdout output: [info] Attempting to curl http://209.222.18.222:2000/?client_id=3dc3cde325c5b407199370458da9d041bb4d98e05d49cf6311983f2ac9112af7... 2019-07-16 11:53:40,015 DEBG 'start-script' stdout output: [info] Curl successful for http://209.222.18.222:2000/?client_id=3dc3cde325c5b407199370458da9d041bb4d98e05d49cf6311983f2ac9112af7, response code 200 2019-07-16 11:53:40,052 DEBG 'start-script' stdout output: [info] Checking we can resolve name 'www.google.com' to address... 2019-07-16 11:53:40,272 DEBG 'start-script' stdout output: [info] DNS operational, we can resolve name 'www.google.com' to address '172.217.164.228' 2019-07-16 11:53:40,273 DEBG 'start-script' stdout output: [info] Attempting to get external IP using Name Server 'ns1.google.com'... 2019-07-16 11:53:40,961 DEBG 'start-script' stdout output: [info] Successfully retrieved external IP address 172.98.67.107 2019-07-16 11:53:41,010 DEBG 'watchdog-script' stdout output: [info] Deluge listening interface IP 0.0.0.0 and VPN provider IP 10.22.10.14 different, marking for reconfigure 2019-07-16 11:53:41,014 DEBG 'watchdog-script' stdout output: [info] Deluge not running 2019-07-16 11:53:41,017 DEBG 'watchdog-script' stdout output: [info] Deluge Web UI not running 2019-07-16 11:53:41,020 DEBG 'watchdog-script' stdout output: [info] Privoxy not running 2019-07-16 11:53:41,020 DEBG 'watchdog-script' stdout output: [info] Deluge incoming port 6890 and VPN incoming port 22783 different, marking for reconfigure 2019-07-16 11:53:41,020 DEBG 'watchdog-script' stdout output: [info] Attempting to start Deluge... [info] Removing deluge pid file (if it exists)... 2019-07-16 11:53:41,375 DEBG 'watchdog-script' stdout output: [info] Deluge key 'listen_interface' currently has a value of '10.2.11.6' [info] Deluge key 'listen_interface' will have a new value '10.22.10.14' [info] Writing changes to Deluge config file '/config/core.conf'... 2019-07-16 11:53:41,586 DEBG 'watchdog-script' stdout output: [info] Deluge key 'outgoing_interface' currently has a value of 'tun0' [info] Deluge key 'outgoing_interface' will have a new value 'tun0' [info] Writing changes to Deluge config file '/config/core.conf'... 2019-07-16 11:53:41,780 DEBG 'watchdog-script' stdout output: [info] Deluge key 'default_daemon' currently has a value of 'c11d5166a94dc914db6aea06fdfb28ed32903ef4' [info] Deluge key 'default_daemon' will have a new value 'c11d5166a94dc914db6aea06fdfb28ed32903ef4' [info] Writing changes to Deluge config file '/config/web.conf'... 2019-07-16 11:53:42,105 DEBG 'watchdog-script' stdout output: [info] Deluge process started [info] Waiting for Deluge process to start listening on port 58846... 2019-07-16 11:53:42,320 DEBG 'watchdog-script' stdout output: [info] Deluge process listening on port 58846 2019-07-16 11:53:45,895 DEBG 'watchdog-script' stdout output: Setting "random_port" to: False Configuration value successfully updated. deluged.log 11:47:53 [INFO ][deluge.core.torrentmanager :885 ] Finished loading 224 torrents in 0:00:00.325328 11:47:54 [INFO ][deluge.core.torrentmanager :1609] on_alert_external_ip: 172.98.67.77 11:47:56 [INFO ][deluge.core.rpcserver :171 ] Deluge Client connection made from: 127.0.0.1:46286 11:47:56 [INFO ][deluge.core.rpcserver :197 ] Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost.
  8. Nice, I just did a quick test and I seem to get speeds more aligned with my connection, are you planning on updating the plugin to use this? Thanks, Wob
  9. Is anyone else finding the setting are not saving between reboots? Each time I start up nothing is configured within this plugin.
  10. Not exactly helpful considering this is a couchpotato thread. I am still waiting for nest folder support in the library before radar is useful for me. Sent from my SM-G935F using Tapatalk
  11. Hi, thanks for the plugin, I just installed this as I am having some issues with nodered startup, hoping a delay will help. I have 2 nodered containers, nodered nodered.dev I can only select the first of the two, I can select the rest OK, so seems it be the names are too similar, or the fact the icons are both the same? Thanks, Wob Sent from my SM-G935F using Tapatalk
  12. Just an update on my progress, It seems to be a stability issue with dzVents, with that disabled the docker is fairly stable (still crashed after a week), but as soon as I enable the scripts it will crash every few days. I have updated with each docker release, and currently at the version with Domoticz v3.8875, still crashing. The VM I am running is on v3.8834 and has been up for almost 13 days, so for the moment I am going to stick with a VM, seems more logical for my config as I have a few customisations I was having to do after each pull anyway, resources are higher, but not a deal breaker. Thanks for your efforts, I might revisit the docker again if future. Wob
  13. OK, I built up a VM with ubuntu server 16.04.3 and pulled down domoticz as per the install guide (https://www.domoticz.com/wiki/Linux) to ensure I wasn't messing anything up. After the install dzVents runtime is located in ~/domoticz/dzVents/runtime I did the same thing I was doing on a new pull of the container, created a dzvents script using the example code, this caused caused a segfault crash of the system. I found a thread that suggested going to Setup\Settings\Other and disabling both EventSystem and dzVents and then re-enabling them. This fixed the segfault. I then enabled the sample script, no crashing, created dummy hardware and a dummy switch, linking them, testing the switch and script and all behaved as expected. I could try the above on the container, but as you mention the dzvents runtime just doesn't exist, it seems it get cleaned from the old location, but not created in the new location. I can pull it seperate, but I want to ensure I am not introducing issues. I have now restored my database to see if it runs anymore stable than the container (at the moment it crashes every few days), I have just disabled any scripts that directly control anything, I have enough others running that dzVents it still active. I would like to stick to a container, as it uses less system resources, but stability is causing me issues, just trying to work out if this is due to the container, domoticz (maybe the beta) or I have a corruption in my database. Also considering going to a pi, now that my automation scripts are working nicely I need to keep it stable to keep the WAF and stop the lights, etc being manually turned off :). I would go back to a stable build, but I am using stuff in my scripting that requires dzVents 2.3 and that is not in stable, also much of the Xiaomi plugin requires beta and I have a heap of those sensors, hoping they get to another stable soon, but much of the bugs being reported seem to go without much response.
  14. @ken-ji Thanks for the details, I guess I could look at setting up a VLAN, seems like an odd choice to be able to put a device on a LAN, but not have it talk to other device on the LAN (Host or otherwise). For the moment I'll just stick with pipeworks, it has been plodding along nicely for some time now.