Dublindog

Members
  • Posts

    2
  • Joined

  • Last visited

Dublindog's Achievements

Noob

Noob (1/14)

0

Reputation

  1. [EDIT - wanted to cancel my request for help as I found the problem, but also wanted to document the solution for others. Turns out the issue was the default “localhost” addresses for the Sonarr/Radar configurations. Changing those to the direct IP of the server fixed all of the connectivity issues.] HI all, I'm having problems using delugevpn with other docker containers (like NZBGET or the ***ars). The other containers all have DNS or connection or "pipe closed" issues, which leads me to guess they aren't able to communicate through Delugevpn. But since I'm a relative newbie to Docker, am not sure what the issue might be, and was hoping some of you folks might be able to point me in the right direction. Errors I see include: "Unable to communicate with NZBGet. Unable to write data to the transport connection: The socket has been shut down." (Sonarr) - verified that NZBGet is up and running "Could not resolve hostname https://api.nzbgeek.info/: Error -2 - Name does not resolve" (NZBGet, when trying to add newshost and testing) Deluge (part of the DelugeVPN package obviously) *does* work, which seems to hint at some sort of Docker/DelugeVPN networking configuration issue AFAIKT. My docker-compose file for DelugeVPN (using ProtonVPN) is below. Note that I'm locked to this specific image due to a known kernel version on Synology which blocks me from using the most recent builds. It would be good to know if that's the issue in itself, in which case I guess I'll need to try to set up another VPN. Appreciate any tips you might be able to share, with thanks! version: "2" services: deluge-openvpn: restart: always image: binhex/arch-delugevpn:2.0.4.dev38_g23a48dd01-3-01 cap_add: - NET_ADMIN ports: - "8112:8112" - "8118:8118" - "58846:58846" volumes: - /volume1/data:/volume1/data #don't understand why I need this for Deluge to write files - /volume1/docker/delugevpn_protonvpn/config:/config - /volume1/data/downloads/torrents:/data - /etc/localtime:/etc/localtime:ro environment: - VPN_ENABLED=yes - VPN_USER=XXX - VPN_PASS=XXX - VPN_PORT=443 - VPN_PROTOCOL=udp - VPN_DEVICE_TYPE=tun - VPN_PROV=protonvpn - STRONG_CERTS=no - ENABLE_PRIVOXY=no - LAN_NETWORK=192.168.1.0/24 - NAME_SERVERS=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 - DEBUG=false - PUID=1029 - PGID=100 - UMASK=000 - TZ=America/Vancouver
  2. [Update: issue resolved via this FAQ entry: Q13. I can see from the '/config/supervisord.log' file that the openvpn process keeps getting killed every 30 seconds on my QNAP appliance, what could be the cause of this? A13. For some reason (unknown at this time) QNAP decided to kill any openvpn process running on the host by adding in a line to the 'daemon_mgr.conf' file. In order to prevent this you need to delete the following line from the 'daemon_mgr.conf':- DAEMONxx = openvpn, stop, /usr/sbin/openvpn Where xx will be 2 random digits. Additional note: found instructions on how to use WinSCP to edit the daemon_mgr.conf file on QNAP here: https://forum.qnap.com/viewtopic.php?t=117004#p519883 end update.] Hi, been working through setting up DelugeVPN in a Docker container on QNAP. Have it basically working, but get occasional errors. Using this script: docker run \ --cap-add=NET_ADMIN \ -p 8112:8112 \ -p 8118:8118 \ -p 58846:58846 \ -p 58946:58946 \ --name=delugevpn \ -v /share/CACHEDEV1_DATA/appdata/delugevpn/data:/data \ -v /share/CACHEDEV1_DATA/appdata/delugevpn/config:/config \ -v /etc/localtime:/etc/localtime:ro \ -e VPN_USER=[removed] \ -e VPN_PASS=[rempved] \ -e VPN_PROV=torguard \ -e STRICT_PORT_FORWARD=yes \ -e ENABLE_PRIVOXY=yes \ -e LAN_NETWORK=192.168.1.0/24 \ -e NAME_SERVERS=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 \ -e DELUGE_DAEMON_LOG_LEVEL=info \ -e DELUGE_WEB_LOG_LEVEL=info \ -e DEBUG=false \ -e UMASK=000 \ -e PUID=0 \ -e PGID=0 \ binhex/arch-delugevpn I seem to get it running, and it does connect through VPN and show the right VPN external IP address. However, I regularly see this error: 2019-01-29 11:09:20,815 DEBG 'start-script' stdout output: Tue Jan 29 11:09:20 2019 ERROR: Linux route add command failed: external program exited with error status: 2 Is this something of concern? Possibly related, when I go to the Privoxy port (8118), a web page loads but I only see this error message: "Invalid header received from client." Appreciate any feedback or assistance, with thanks!