spikey1973

Members
  • Posts

    34
  • Joined

  • Last visited

Everything posted by spikey1973

  1. Hello, I am imbareced to ask another question here. I a still having issues with my NAS, and to solve this i had to put my own router behind the modem, with the latter one in bridge mode. While doing so the my Lan network ip's have all changed from 192.168.178.XXX to 192.168.1.XXX So i changed the LAN network line to: LAN_NETWORK=192.168.1.0/24 (i had this wrong the lat couple of times i posted an issue i couldn't solve, but i believe it to be correct now) never the less the container does not seem to start (still using portainer (2.15.1) instead of unraid) as far as i know nothing else changed. the following keeps repeating does anyone have an idea about what the issue could be? it seems to me like an authentification issue, just don't understand why. Kindest greetz Matthieu 2022-09-25 14:54:45,626 DEBG 'start-script' stdout output: 2022-09-25 14:54:45 SENT CONTROL [be-anr-v023.prod.surfshark.com]: 'PUSH_REQUEST' (status=1) 2022-09-25 14:54:45,662 DEBG 'start-script' stdout output: 2022-09-25 14:54:45 AUTH: Received control message: AUTH_FAILED 2022-09-25 14:54:45,662 DEBG 'start-script' stdout output: 2022-09-25 14:54:45 SIGTERM[soft,auth-failure] received, process exiting 2022-09-25 14:54:45,665 DEBG 'start-script' stdout output: [info] Starting OpenVPN (non daemonised)... 2022-09-25 14:54:45,677 DEBG 'start-script' stdout output: 2022-09-25 14:54:45 DEPRECATED OPTION: --cipher set to 'AES-256-CBC' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM). Future OpenVPN version will ignore --cipher for cipher negotiations. Add 'AES-256-CBC' to --data-ciphers or change --cipher 'AES-256-CBC' to --data-ciphers-fallback 'AES-256-CBC' to silence this warning. 2022-09-25 14:54:45,678 DEBG 'start-script' stdout output: 2022-09-25 14:54:45 WARNING: file 'credentials.conf' is group or others accessible 2022-09-25 14:54:45 OpenVPN 2.5.7 [git:makepkg/a0f9a3e9404c8321+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on May 31 2022 2022-09-25 14:54:45 library versions: OpenSSL 1.1.1q 5 Jul 2022, LZO 2.10 2022-09-25 14:54:45 WARNING: --ping should normally be used with --ping-restart or --ping-exit 2022-09-25 14:54:45 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts 2022-09-25 14:54:45 NOTE: --fast-io is disabled since we are not using UDP 2022-09-25 14:54:45,679 DEBG 'start-script' stdout output: 2022-09-25 14:54:45 Outgoing Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication 2022-09-25 14:54:45 Incoming Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication 2022-09-25 14:54:45,680 DEBG 'start-script' stdout output: 2022-09-25 14:54:45 TCP/UDP: Preserving recently used remote address: [AF_INET]188.95.54.18:1443 2022-09-25 14:54:45 Socket Buffers: R=[131072->131072] S=[16384->16384] 2022-09-25 14:54:45,680 DEBG 'start-script' stdout output: 2022-09-25 14:54:45 Attempting to establish TCP connection with [AF_INET]188.95.54.18:1443 [nonblock] 2022-09-25 14:54:45,699 DEBG 'start-script' stdout output: 2022-09-25 14:54:45 TCP connection established with [AF_INET]188.95.54.18:1443 2022-09-25 14:54:45 TCP_CLIENT link local: (not bound) 2022-09-25 14:54:45 TCP_CLIENT link remote: [AF_INET]188.95.54.18:1443 2022-09-25 14:54:45,718 DEBG 'start-script' stdout output: 2022-09-25 14:54:45 TLS: Initial packet from [AF_INET]188.95.54.18:1443, sid=139b612a ad1d11c0 2022-09-25 14:54:45,827 DEBG 'start-script' stdout output: 2022-09-25 14:54:45 VERIFY OK: depth=2, C=VG, O=Surfshark, CN=Surfshark Root CA 2022-09-25 14:54:45,829 DEBG 'start-script' stdout output: 2022-09-25 14:54:45 VERIFY OK: depth=1, C=VG, O=Surfshark, CN=Surfshark Intermediate CA 2022-09-25 14:54:45 VERIFY KU OK 2022-09-25 14:54:45 Validating certificate extended key usage 2022-09-25 14:54:45 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication 2022-09-25 14:54:45 VERIFY EKU OK 2022-09-25 14:54:45 VERIFY OK: depth=0, CN=be-anr-v023.prod.surfshark.com 2022-09-25 14:54:45,915 DEBG 'start-script' stdout output: 2022-09-25 14:54:45 WARNING: 'link-mtu' is used inconsistently, local='link-mtu 1635', remote='link-mtu 1583' 2022-09-25 14:54:45 WARNING: 'auth' is used inconsistently, local='auth SHA512', remote='auth [null-digest]' 2022-09-25 14:54:45,916 DEBG 'start-script' stdout output: 2022-09-25 14:54:45 Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, peer certificate: 2048 bit RSA, signature: RSA-SHA256 2022-09-25 14:54:45 [be-anr-v023.prod.surfshark.com] Peer Connection Initiated with [AF_INET]188.95.54.18:1443 2022-09-25 14:54:46,960 DEBG 'start-script' stdout output: 2022-09-25 14:54:46 SENT CONTROL [be-anr-v023.prod.surfshark.com]: 'PUSH_REQUEST' (status=1)
  2. hmmm, well yeah that explains, thanks for explaining that!
  3. @ Members: thnk you so much again. indeed this did it again. guess i am still not onboard with ip's as i thought i was. Never the less, what i wonder is why could i connect with VPN off, with the same IP settings?, to me that would mean i shouldn't have been able to connect either, but as i said... i could. Kindest regards and appreciation!
  4. i am so sorry to ask this question "again" I recently needed to re-initialise my nas, just after when i finally got things working again docker wise. This because there were issues with the initial nas initialisation, which seemed to have nothing to docker related). Unfortunately I haven't been able to connect to the webUI (which has seem to have started) of DelugeVPN since then. I verified my LAN network ip in the stack as this was the silly error i over looked last time i asked a question related to a topic, with similar issues. ( LAN_NETWORK=192.168.178.1/24), while my NAS is running on IP:192.168.178.45 I used the ports as standard (basically using the same stack as always) so i try to connect via. 192.168.178.45:8112, but it time's out. So as i read through a similar (very similar indeed) issue here in this thread i verified the following. 1:) VPN subscription is paid for and working, which it is. 2) VPN end point is not down, which it isn't as i used the same end point on my laptop without issues. Never the less if I turn VPN off (VPN_ENABLED=no) there is no issue to connect to the WEBUI at all, but ofcourse then i loose the protection on the VPN. Additionally i checked that there were no issue with my login credentials (actually recreated a new password) but unfortunately, to no avail. Honoustly, now i have absolutely no idea what to look for, any thoughts / sugestions? As looking at the logs, all is supposed to be running fine, in the console all also seems to be fine. stack: version: "2.1" services: arch-delugevpn: image: binhex/arch-delugevpn:latest container_name: DelugeVPN cap_add: - NET_ADMIN environment: - VPN_ENABLED=yes - VPN_USER=LPRyc2GmAjUbxtuGThtm.... - VPN_PASS=KZ2qpsTxCTfCBBTgfxxj.... - VPN_PROV=custom - VPN_CLIENT=openvpn - STRICT_PORT_FORWARD=yes - ENABLE_PRIVOXY=yes - LAN_NETWORK=192.168.178.1/24 - NAME_SERVERS=209.222.18.222,84.200.69.80,37.235.1.174,1.1.1.1,209.222.18.218,37.235.1.177,84.200.70.40,1.0.0.1 - DELUGE_DAEMON_LOG_LEVEL=info - DELUGE_WEB_LOG_LEVEL=info - ADDITIONAL_PORTS=1234 - DEBUG=false - PUID=111 - PGID=321 - UMASK=022 volumes: - /volume1/Docker/DelugeVPN/Config:/config - /volume3/Movies/Downloads:/download - /etc/localtime:/etc/localtime:ro ports: - 8112:8112 - 8118:8118 - 58846:58846 - 58946:58946 restart: always _DelugeVPN_logs.txt
  5. thank you so much, This will indeed be it, but i would so not have seen this for months without our input. so again, thanks ver much., much appreciated.
  6. hey hello, i have been using delugevpn for a few years now with good results.. even though i have a strange issue with my nas.. which is not deluge or docker related, i have shince shortly bumped into another strange issue. Even though delugevpn seems to be running fine, can't seem to contact the web UI anymore.. my nas (asustor 6114T, running ADM 4.0.5.RT42, with docker-ce, portainer 2.13.1) is at lan ip : 192.168.178.45 so i contact portainer via 192.168.178.45:19943 succesfully. when i try to contact delugevpn via 192.168.178.45:8112 it times out. , also tried port 8118, but ofcourse this doen't work either.. as it shouldn't. i did resently convert my dual router setup to a mono router setup, this mono router is provider supplied, so i am less familiar with it then my own. i did this to solve the nas issue. my stack under portainer is: version: "2.1" services: arch-delugevpn: image: binhex/arch-delugevpn:latest container_name: DelugeVPN cap_add: - NET_ADMIN environment: - VPN_ENABLED=yes - VPN_USER=LPRyc2GmAjUbxtuGTht..... - VPN_PASS=FxydMbghENSQT5UneQR..... - VPN_PROV=custom - VPN_CLIENT=openvpn - STRICT_PORT_FORWARD=yes - ENABLE_PRIVOXY=yes - LAN_NETWORK=192.168.1.0/24 - NAME_SERVERS=209.222.18.222,84.200.69.80,37.235.1.174,1.1.1.1,209.222.18.218,37.235.1.177,84.200.70.40,1.0.0.1 - DELUGE_DAEMON_LOG_LEVEL=info - DELUGE_WEB_LOG_LEVEL=info - ADDITIONAL_PORTS=1234 - DEBUG=false - PUID=111 - PGID=321 - UMASK=022 volumes: - /volume1/Docker/DelugeVPN/Config:/config - /volume2/Files2/Downloads:/files/downloads - /etc/localtime:/etc/localtime:ro ports: - 8112:8112 - 8118:8118 - 58846:58846 - 58946:58946 restart: always logs: 2022-05-29 18:01:34 Socket Buffers: R=[131072->425984] S=[87040->425984] 2022-05-29 18:01:34 OPTIONS IMPORT: --ifconfig/up options modified 2022-05-29 18:01:34 OPTIONS IMPORT: route options modified 2022-05-29 18:01:34 OPTIONS IMPORT: route-related options modified 2022-05-29 18:01:34 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified 2022-05-29 18:01:34 OPTIONS IMPORT: peer-id set 2022-05-29 18:01:34 OPTIONS IMPORT: adjusting link_mtu to 1658 2022-05-29 18:01:34 OPTIONS IMPORT: data channel crypto options modified 2022-05-29 18:01:34 Data Channel: using negotiated cipher 'AES-256-GCM' 2022-05-29 18:01:34 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key 2022-05-29 18:01:34 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key 2022-05-29 18:01:34 net_route_v4_best_gw query: dst 0.0.0.0 2022-05-29 18:01:34 net_route_v4_best_gw result: via 172.19.0.1 dev eth0 2022-05-29 18:01:34,878 DEBG 'start-script' stdout output: 2022-05-29 18:01:34 ROUTE_GATEWAY 172.19.0.1/255.255.0.0 IFACE=eth0 HWADDR=02:42:ac:13:00:02 2022-05-29 18:01:34,878 DEBG 'start-script' stdout output: 2022-05-29 18:01:34 TUN/TAP device tun0 opened 2022-05-29 18:01:34,878 DEBG 'start-script' stdout output: 2022-05-29 18:01:34 net_iface_mtu_set: mtu 1500 for tun0 2022-05-29 18:01:34 net_iface_up: set tun0 up 2022-05-29 18:01:34 net_addr_v4_add: 10.7.7.14/24 dev tun0 2022-05-29 18:01:34,878 DEBG 'start-script' stdout output: 2022-05-29 18:01:34 /root/openvpnup.sh tun0 1500 1586 10.7.7.14 255.255.255.0 init 2022-05-29 18:01:34,882 DEBG 'start-script' stdout output: 2022-05-29 18:01:34 net_route_v4_add: 194.110.115.85/32 via 172.19.0.1 dev [NULL] table 0 metric -1 2022-05-29 18:01:34 net_route_v4_add: 0.0.0.0/1 via 10.7.7.1 dev [NULL] table 0 metric -1 2022-05-29 18:01:34 net_route_v4_add: 128.0.0.0/1 via 10.7.7.1 dev [NULL] table 0 metric -1 2022-05-29 18:01:34 Initialization Sequence Completed 2022-05-29 18:02:06,223 DEBG 'start-script' stdout output: [info] Attempting to get external IP using 'http://checkip.amazonaws.com'... 2022-05-29 18:02:12,901 DEBG 'start-script' stdout output: [info] Successfully retrieved external IP address 194.110.115.86 2022-05-29 18:02:12,903 DEBG 'start-script' stdout output: [info] Application does not require port forwarding or VPN provider is != pia, skipping incoming port assignment 2022-05-29 18:02:12,979 DEBG 'watchdog-script' stdout output: [info] Deluge listening interface IP 0.0.0.0 and VPN provider IP 10.7.7.14 different, marking for reconfigure 2022-05-29 18:02:12,985 DEBG 'watchdog-script' stdout output: [info] Deluge not running 2022-05-29 18:02:12,992 DEBG 'watchdog-script' stdout output: [info] Deluge Web UI not running 2022-05-29 18:02:12,999 DEBG 'watchdog-script' stdout output: [info] Privoxy not running 2022-05-29 18:02:12,999 DEBG 'watchdog-script' stdout output: [info] Attempting to start Deluge... [info] Removing deluge pid file (if it exists)... 2022-05-29 18:02:13,281 DEBG 'watchdog-script' stdout output: [info] Deluge key 'listen_interface' currently has a value of '10.7.7.14' [info] Deluge key 'listen_interface' will have a new value '10.7.7.14' [info] Writing changes to Deluge config file '/config/core.conf'... 2022-05-29 18:02:13,592 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'... 2022-05-29 18:02:13,916 DEBG 'watchdog-script' stdout output: [info] Deluge key 'default_daemon' currently has a value of '136bb0e8b9534e178fa5deda01456c5b' [info] Deluge key 'default_daemon' will have a new value '136bb0e8b9534e178fa5deda01456c5b' [info] Writing changes to Deluge config file '/config/web.conf'... 2022-05-29 18:02:14,607 DEBG 'watchdog-script' stdout output: [info] Deluge process started [info] Waiting for Deluge process to start listening on port 58846... 2022-05-29 18:02:14,943 DEBG 'watchdog-script' stdout output: [info] Deluge process listening on port 58846 2022-05-29 18:02:19,574 DEBG 'watchdog-script' stdout output: [info] No torrents with state 'Error' found 2022-05-29 18:02:19,574 DEBG 'watchdog-script' stdout output: [info] Starting Deluge Web UI... 2022-05-29 18:02:19,574 DEBG 'watchdog-script' stdout output: [info] Deluge Web UI started 2022-05-29 18:02:19,576 DEBG 'watchdog-script' stdout output: [info] Attempting to start Privoxy... 2022-05-29 18:02:20,592 DEBG 'watchdog-script' stdout output: [info] Privoxy process started [info] Waiting for Privoxy process to start listening on port 8118... 2022-05-29 18:02:20,596 DEBG 'watchdog-script' stdout output: [info] Privoxy process listening on port 8118 so all seems to be fine there... inspect: { "AppArmorProfile": "", "Args": [ "-g", "--", "/bin/bash", "/usr/local/bin/init.sh" ], "Config": { "AttachStderr": false, "AttachStdin": false, "AttachStdout": false, "Cmd": [ "/bin/bash", "/usr/local/bin/init.sh" ], "Domainname": "", "Entrypoint": [ "/usr/bin/tini", "-g", "--" ], "Env": [ "VPN_ENABLED=yes", "VPN_USER=LPRyc2GmAjUbxtuGTht.....", "VPN_PASS=FxydMbghENSQT5UneQR.....", "VPN_PROV=custom", "VPN_CLIENT=openvpn", "STRICT_PORT_FORWARD=yes", "ENABLE_PRIVOXY=yes", "LAN_NETWORK=192.168.1.0/24", "NAME_SERVERS=209.222.18.222,84.200.69.80,37.235.1.174,1.1.1.1,209.222.18.218,37.235.1.177,84.200.70.40,1.0.0.1", "DELUGE_DAEMON_LOG_LEVEL=info", "DELUGE_WEB_LOG_LEVEL=info", "ADDITIONAL_PORTS=1234", "DEBUG=false", "PUID=111", "PGID=321", "UMASK=022", "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin", "HOME=/home/nobody", "TERM=xterm", "LANG=en_GB.UTF-8" ], "ExposedPorts": { "58846/tcp": {}, "58946/tcp": {}, "58946/udp": {}, "8112/tcp": {}, "8118/tcp": {} }, "Hostname": "9390dd6813cc", "Image": "binhex/arch-delugevpn:latest", "Labels": { "com.docker.compose.config-hash": "9eef52e8498fac0504f35fb668e4e2331d120d573e1b335af3ab04a9c98c884a", "com.docker.compose.container-number": "1", "com.docker.compose.oneoff": "False", "com.docker.compose.project": "delugevpn", "com.docker.compose.project.config_files": "/data/compose/1/docker-compose.yml", "com.docker.compose.project.working_dir": "/data/compose/1", "com.docker.compose.service": "arch-delugevpn", "com.docker.compose.version": "1.27.4", "org.opencontainers.image.authors": "= binhex", "org.opencontainers.image.source": "= https://github.com/binhex/arch-delugevpn" }, "OnBuild": null, "OpenStdin": false, "StdinOnce": false, "Tty": false, "User": "", "Volumes": { "/config": {}, "/etc/localtime": {}, "/files/downloads": {} }, "WorkingDir": "" }, "Created": "2022-05-29T14:53:50.860723031Z", "Driver": "btrfs", "ExecIDs": null, "GraphDriver": { "Data": null, "Name": "btrfs" }, "HostConfig": { "AutoRemove": false, "Binds": [ "/etc/localtime:/etc/localtime:ro", "/volume1/Docker/DelugeVPN/Config:/config:rw", "/volume2/Files2/Downloads:/files/downloads:rw" ], "BlkioDeviceReadBps": null, "BlkioDeviceReadIOps": null, "BlkioDeviceWriteBps": null, "BlkioDeviceWriteIOps": null, "BlkioWeight": 0, "BlkioWeightDevice": null, "CapAdd": [ "NET_ADMIN" ], "CapDrop": null, "Cgroup": "", "CgroupParent": "", "CgroupnsMode": "host", "ConsoleSize": [ 0, 0 ], "ContainerIDFile": "", "CpuCount": 0, "CpuPercent": 0, "CpuPeriod": 0, "CpuQuota": 0, "CpuRealtimePeriod": 0, "CpuRealtimeRuntime": 0, "CpuShares": 0, "CpusetCpus": "", "CpusetMems": "", "DeviceCgroupRules": null, "DeviceRequests": null, "Devices": null, "Dns": null, "DnsOptions": null, "DnsSearch": null, "ExtraHosts": null, "GroupAdd": null, "IOMaximumBandwidth": 0, "IOMaximumIOps": 0, "IpcMode": "private", "Isolation": "", "KernelMemory": 0, "KernelMemoryTCP": 0, "Links": null, "LogConfig": { "Config": {}, "Type": "json-file" }, "MaskedPaths": [ "/proc/asound", "/proc/acpi", "/proc/kcore", "/proc/keys", "/proc/latency_stats", "/proc/timer_list", "/proc/timer_stats", "/proc/sched_debug", "/proc/scsi", "/sys/firmware" ], "Memory": 0, "MemoryReservation": 0, "MemorySwap": 0, "MemorySwappiness": null, "NanoCpus": 0, "NetworkMode": "delugevpn_default", "OomKillDisable": false, "OomScoreAdj": 0, "PidMode": "", "PidsLimit": null, "PortBindings": { "58846/tcp": [ { "HostIp": "", "HostPort": "58846" } ], "58946/tcp": [ { "HostIp": "", "HostPort": "58946" } ], "8112/tcp": [ { "HostIp": "", "HostPort": "8112" } ], "8118/tcp": [ { "HostIp": "", "HostPort": "8118" } ] }, "Privileged": false, "PublishAllPorts": false, "ReadonlyPaths": [ "/proc/bus", "/proc/fs", "/proc/irq", "/proc/sys", "/proc/sysrq-trigger" ], "ReadonlyRootfs": false, "RestartPolicy": { "MaximumRetryCount": 0, "Name": "always" }, "Runtime": "runc", "SecurityOpt": null, "ShmSize": 67108864, "UTSMode": "", "Ulimits": null, "UsernsMode": "", "VolumeDriver": "", "VolumesFrom": [] }, "HostnamePath": "/volume1/.@plugins/AppCentral/docker-ce/docker_lib/containers/9390dd6813cc70d3de0c6971dcc18c98ea125dba7976a91d48936eb24825a1ec/hostname", "HostsPath": "/volume1/.@plugins/AppCentral/docker-ce/docker_lib/containers/9390dd6813cc70d3de0c6971dcc18c98ea125dba7976a91d48936eb24825a1ec/hosts", "Id": "9390dd6813cc70d3de0c6971dcc18c98ea125dba7976a91d48936eb24825a1ec", "Image": "sha256:33f5d4f3dc4917804fe6db408b6ad969915d6d79841457492b9e77f350bf075d", "LogPath": "/volume1/.@plugins/AppCentral/docker-ce/docker_lib/containers/9390dd6813cc70d3de0c6971dcc18c98ea125dba7976a91d48936eb24825a1ec/9390dd6813cc70d3de0c6971dcc18c98ea125dba7976a91d48936eb24825a1ec-json.log", "MountLabel": "", "Mounts": [ { "Destination": "/etc/localtime", "Mode": "ro", "Propagation": "rprivate", "RW": false, "Source": "/etc/localtime", "Type": "bind" }, { "Destination": "/config", "Mode": "rw", "Propagation": "rprivate", "RW": true, "Source": "/volume1/Docker/DelugeVPN/Config", "Type": "bind" }, { "Destination": "/files/downloads", "Mode": "rw", "Propagation": "rprivate", "RW": true, "Source": "/volume2/Files2/Downloads", "Type": "bind" } ], "Name": "/DelugeVPN", "NetworkSettings": { "Bridge": "", "EndpointID": "", "Gateway": "", "GlobalIPv6Address": "", "GlobalIPv6PrefixLen": 0, "HairpinMode": false, "IPAddress": "", "IPPrefixLen": 0, "IPv6Gateway": "", "LinkLocalIPv6Address": "", "LinkLocalIPv6PrefixLen": 0, "MacAddress": "", "Networks": { "delugevpn_default": { "Aliases": [ "9390dd6813cc", "arch-delugevpn" ], "DriverOpts": null, "EndpointID": "9937875026ac9ceb2a776dbe1a4b471280bc14b7895b0c2a3744ad77be526a4c", "Gateway": "172.19.0.1", "GlobalIPv6Address": "", "GlobalIPv6PrefixLen": 0, "IPAMConfig": null, "IPAddress": "172.19.0.2", "IPPrefixLen": 16, "IPv6Gateway": "", "Links": null, "MacAddress": "02:42:ac:13:00:02", "NetworkID": "e2729335d81558d586acd6b5942a1a7b07c0cff7d47d8f887277bbc4a8d7bcf9" } }, "Ports": { "58846/tcp": [ { "HostIp": "0.0.0.0", "HostPort": "58846" }, { "HostIp": "::", "HostPort": "58846" } ], "58946/tcp": [ { "HostIp": "0.0.0.0", "HostPort": "58946" }, { "HostIp": "::", "HostPort": "58946" } ], "58946/udp": null, "8112/tcp": [ { "HostIp": "0.0.0.0", "HostPort": "8112" }, { "HostIp": "::", "HostPort": "8112" } ], "8118/tcp": [ { "HostIp": "0.0.0.0", "HostPort": "8118" }, { "HostIp": "::", "HostPort": "8118" } ] }, "SandboxID": "f388afc650832850f696df998f8905fe6d7bcace90a64ae91a6305d4f2b2a8ab", "SandboxKey": "/var/run/docker/netns/f388afc65083", "SecondaryIPAddresses": null, "SecondaryIPv6Addresses": null }, "Path": "/usr/bin/tini", "Platform": "linux", "Portainer": { "ResourceControl": { "Id": 1, "ResourceId": "2_delugevpn", "SubResourceIds": [], "Type": 6, "UserAccesses": [], "TeamAccesses": [], "Public": false, "AdministratorsOnly": true, "System": false } }, "ProcessLabel": "", "ResolvConfPath": "/volume1/.@plugins/AppCentral/docker-ce/docker_lib/containers/9390dd6813cc70d3de0c6971dcc18c98ea125dba7976a91d48936eb24825a1ec/resolv.conf", "RestartCount": 0, "State": { "Dead": false, "Error": "", "ExitCode": 0, "FinishedAt": "2022-05-29T16:01:21.283842661Z", "OOMKilled": false, "Paused": false, "Pid": 26386, "Restarting": false, "Running": true, "StartedAt": "2022-05-29T16:01:29.114885459Z", "Status": "running" } } and checked resolve.conf: nameserver 209.222.18.222 nameserver 84.200.69.80 nameserver 37.235.1.174 nameserver 1.1.1.1 nameserver 209.222.18.218 nameserver 37.235.1.177 nameserver 84.200.70.40 nameserver 1.0.0.1 I can contact to console without any issue. and as said. i can connect to any other running container without issue. amongst which radarr, which recognizes delugevpn as deluge and running (it gives errors if it doesn't) sorry for the long post..
  7. yeah that is what I was afraid of. Thank you for confirming that..
  8. @corfoto4: thanks for pointing out this tutorial, very informative.. specifically finding out the python version. @all: sive clearly the python version is up and running and up to date so the latest version of YaRSS2 sould be perfect.. never the less.. and as pointed out above: i found the following on https://dev.deluge-torrent.org/wiki/Plugins. YaRSS2: An RSS plugin configurable through the GUI: Support webgui :No, deluge 2.x support: Yes does this mean i can't get YaRSS2 to work with this version? any thoughts are much appreciated, as if it can't work i can give up this quest.
  9. @ados Could this be the cause of my issue too? although I tried to install 1.x versions too? in the plugins folder a zip-folder named: [object FileList] with in this folder two other folders: EGG-INFO and yarss2.. from this it would seem that the installation worked.. never the less it doesn't work. now i just also saw the following: YaRSS2: An RSS plugin configurable through the GUI: Support webgui :No, deluge 2.x support: Yes this confuses me.. as delugevpn is 2.0.4dev38 and i believe webui (also/only) so is this supported or not? would really appeciate a though on this, can it work with delugevpn or wont it?
  10. have a look at this link: https://wiki.servarr.com/Docker_Guide i am not sure this will be helpfull for you. but it has definately been helpfull for me for anderstanding file structures outside and inside containers and getting containers to work with each other while still keeping an understandable folder tree.. I do also seem to have an issue with the sonarr renaming part not working. but i need to dive into that later, first i need to solve other issues, never the less the above tutorial have made things quite a lot clearer (for me) ps: if you solve your sonarr renaming issue, can you tag me on this? could help me out there too (maybe).
  11. i have again another question though, sorry.. i am trying to install a YaRSS2 plugin, as your container is ofcourse running as docker container i have no thoughts on if there is pythn running and ifso which, but according to tutorials i need python to install plugins and one would also need to choose the plugin file accordlingly. I do have python3.7 runnning on my nas outside the container, but don't know how to use this in this situation really. Doesn anyone here have any experience with installing plugins on this deluge version or any thoughts on the matter? ps: i read through the deluge FAQ, troubleshooting and plugin files but did not find a working solution, still could've missed something.
  12. hey all as mentioned all is up and running beautifully (delugevpn) but i am not sure about the logic behind the downloaded file locations. these are my set volumes: /volume1/Download:/Downloads /volume1/Docker/Deluge/config:/config /volume1/Docker:/data i just can't seem to locate the downloaded files once done.. i intended them to arrive in /volume1/Download. but it isn't there.. (location in deluge /root/Downloads) when i relocated the downloaded files it ends up in: /volume1/Docker/Deluge/config/NEWFOLDER. so in a different 'branch' and higher up in the folder tree, also in /volume1/Docker/Deluge/config/ there is no Downloads folder, which i would've then expected. the thing is.. i would really like the files to end in the actual /volume1/Download folder, is this in anyway possible? the reason why this is 'important' that the explorer in ADM is really bad.. so going up and down all the branches in the tree everytime i need to relocate files when done will take a lot of time and really is an anuisence. any thoughts? Kind greats. Matthieu
  13. @binhex thank you!!! thank you so much!!! that did it.. 2 weeks of work completed
  14. @binhex thanks for that pointer.. i am startving now.. but i will dive into it tonight.
  15. in addition to the question above.. i thought maybe there is some limitation on access, so to run it through portainer as stack (sorry!!) and make sure i had the "enable access control' turned off... so i ran the following docker-compose code (manually converted, was actually sort of proud that i managed to do so ) version: "2.1" services: arch-delugevpn: image: binhex/arch-delugevpn container_name: delugevpn cap_add: - NET_ADMIN environment: - VPN_ENABLED=yes - VPN_USER=LPRy................... - VPN_PASS=SV2..................... - VPN_PROV=custom - VPN_CLIENT=openvpn - STRICT_PORT_FORWARD=yes - ENABLE_PRIVOXY=yes - LAN_NETWORK=192.168.1.109/32 - NAME_SERVERS=209.222.18.222,84.200.69.80,37.235.1.174,1.1.1.1,209.222.18.218,37.235.1.177,84.200.70.40,1.0.0.1 - DELUGE_DAEMON_LOG_LEVEL=info - DELUGE_WEB_LOG_LEVEL=info - ADDITIONAL_PORTS=1234 - DEBUG=false - UMASK=000 - PUID=0 - PGID=0 volumes - /volume1/Download:/Downloads - /volume1/Docker/Deluge/config:/config - /volume1/Docker:/data - /etc/localtime:/etc/localtime:ro ports: - 8112:8112 - 8118:8118 - 58846:58846 - 58946:58946 restart: unless-stopped unfortunately the same issue remains, no access via http://localhost:8112/ and http://192.168.1.109:8112/ and the same for privoxy :8118 also no error msg, just timing out. would be happy with any suggestion here. Kind regards delugevpn syslog2.pdf
  16. hello all i have finally the delugevpn container running.. and the log seems to be fine.. unfortunately when i try to access the web gui (192.168.1.109:8112) it doesn't open and finally times out (running only delugevpn container) i should NOT run an instance of binhex/arch-delugevpn and linuxserver/deluge correct? any idea why i can't get the web gui opened? ps: 8118 for privoxy didn't work either. i added the log as pdf (so i don't clutter the forum more then i already do ) delugevpn syslog.pdf
  17. "and the certificates referenced in the ovpn file (certificates will normally have a crt and/or pem extension)." i have the open vpn file i need. but about the referenced certificate(s), the CA is incorporated into the ovpn file for surfshark, so there is no seperate ca.crt file, ofcourse i can create one but i believe it not to be necessary. but there are certificates mentioned, should there be another (.crt / key) file? and ifso, what is the name?
  18. thank you! agai this should have been obvious to me, still it wasn't many thanks!!
  19. oke that is clear! unfortunately that calls for another question (which i hope to understand but dot). this line: -v /etc/localtime:/etc/localtime:ro \ has three parts. /etc/localtime: = system? /etc/localtime: = Deluge (but the same) but what is the ro \. i specifically ask as my ADM os on my nas doesnt's have a etc/ folder at all, but there has to be a way it draws the time from somewhere.. so that is my next step to figure out. Kind greatings Matthieu
  20. that is clear! thank you. one more question though.. taking the line again: -v /apps/docker/deluge/config:/config \ i get ofcourse the tree part /apps/docker/config part also the : but what does the second /config and \ mean? thanks for all the help!
  21. oke not using unraid i still have a few delugevpn specific questions if i may? 1) -v /apps/docker/deluge/data:/data \ this line refers to the place where the downloads end up, basically i can choose this location myself? 2) -v /apps/docker/deluge/config:/config \ this line refers to the place where: a: the openvpn config files are placed? or b: the deluge config files are created? if it is a i need to place two files there? .ovpn and a .crt right?
  22. @ Walter ah that screenshot, no that is a screenshot posted as an example by Chesh on page 291, as that is where it is located on his system. that is what i am tring to find on my system. i did post 2 screen shots though.. a little bit further on, also on page 291 but i will post them here again. but i doubt this gives any information except a possible tab inside portainer the info should be. sorry for the confusion, i should've been more clear. Matthieu
  23. @ Walter: thank you for your help!! these are screenshots of portainers.io i made when ssh to my nas from my laptop on the same LAN. looking back at the screenshots i can not find how you concluded it is on my cache drive though (understanding this would probably be very helpfull not?) did you find it back in the "containers" or the " images" screenshot? kind regards.