Wob76

Members
  • Content Count

    194
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Wob76

  • Rank
    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'='
  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... ___. .__ .__ \_ |__ |__| ____ | |__
  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
  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.
  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.