[Support] binhex - DelugeVPN

binhex

By binhex
in Docker Containers

Recommended Posts

Recommended

Posted by binhex,

There has been an issue raised on GitHub related to tracker announce request IP leakage under certain circumstances, after careful review of iptables i have tightened up the rules to prevent this. A new image has now been rolled out for all vpn enabled docker images (25th Feb 2021) i produce with the fix in place, i would encourage everyone to update to the recently created 'latest' tagged image.   You can force the upgrade by toggling 'basic view' to 'advanced view' and then clicking on
Recommended by binhex
  • Thanks
  • Like

8 reactions

Go to this post
Recommended

Posted by Ryanoc3ros,

Found the solution on reddit.   Due to the recent change in the authentication process, using your email and password for the manual connection method will no longer work. You will need to use the service credentials instead. You can find your service credentials by following these steps: Please log in to your Nord Account by following this link: https://my.nordaccount.com/dashboard/nordvpn/ Click on the NordVPN tab on the left panel which is under the Services tab.

NordVPN authentication issues - Solution

Recommended by binhex

  • Upvote
  • Thanks
  • Like

13 reactions

Go to this post
  • Replies 10.3k
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

Ryanoc3ros
Ryanoc3ros

Found the solution on reddit.   Due to the recent change in the authentication process, using your email and password for the manual connection method will no longer work. You will need to u

Dad_Rage
Dad_Rage

I wanted to summarize how I got Mullvad working with DelugeVPN as I had to piece together several "solutions" from different comments in this thread and there was some incorrect info; likely old.

binhex
binhex

OK guys, multi remote endpoint support is now in for this image please pull down the new image (this change will be rolled out to all my vpn images shortly).   What this means is that the im

Posted Images

binhex Mentor

binhex

Posted
  • Author
Posted
4 minutes ago, mwoods98 said:

I'm also having an issue after updating this docker:

 

I can't connect to the WebGUI and I had noticed a few times before that the web gui was getting disconnected. 

I removed the docker and, reinstalled it.

 

Here is what's in the logs. 

 

Thanks in advance. 

deluge.txt 1.44 kB · 0 downloads

out of date ovpn/wireguard config would be the first thing to look at, go download the latest from your vpn provider.

Link to comment
nraygun Contributor

nraygun

Posted
Posted
55 minutes ago, binhex said:

out of date ovpn/wireguard config would be the first thing to look at, go download the latest from your vpn provider.

 

Mine stays up for a while, then overnight it goes into the state you are seeing. I think I have a good ovpn file since it does work upon a restart.

We'll see what happens tomorrow morning since I recreated the container.

Link to comment
heat-pump Noob

heat-pump

Posted
Posted

Hi, I'm in the process of switching from a regular deluge container to the arch-delugevpn one and setting it up for the first time, and I'm losing my mind.
Web UI is broken (can't add torrents, settings don't seem to work [empty values, no plugins], bottom panel shows NaN, n/a, Error instead of values) but accessible; I spent several hours trying to find the issue, no luck.
binhex/arch-delugevpn:latest, Mullvad/WireGuard, docker-compose, Docker 23, Ubuntu host.

It happens no matter if VPN is enabled or not (VPN_ENABLED=yes/no).
The only interesting thing is this log line: Failure: deluge.error.NotAuthorizedError: Auth level too low: 0 < 5

People online suggested downgrading to a certain version of arch-delugevpn or changing to a different WireGuard config, but it didn't help.
Does anyone know what this might be?
More details:

Spoiler

./config/wireguard has wg0.conf in it
docker-compose.yml: 

version: "3.8"

services:
  deluge:
    container_name: arch-delugevpn
    image: binhex/arch-delugevpn:latest
    ports:
      - 8113:8112
      - 8118:8118
      - 58846:58846
      - 58946:58946
    volumes:
      - ./config:/config
      - ./data:/data
      - /etc/localtime:/etc/localtime:ro
    environment:
      - VPN_ENABLED=yes
      - VPN_PROV=custom
      - VPN_CLIENT=wireguard
      - STRICT_PORT_FORWARD=yes
      - ENABLE_PRIVOXY=no
      - LAN_NETWORK=10.0.0.0/24
      - NAME_SERVERS=172.23.0.2,84.200.69.80,37.235.1.174,1.1.1.1,37.235.1.177,84.200.70.40,1.0.0.1
      - DELUGE_DAEMON_LOG_LEVEL=debug
      - DELUGE_WEB_LOG_LEVEL=debug
      - DELUGE_ENABLE_WEBUI_PASSWORD=no
      - DEBUG=false
      - UMASK=000
      - PUID=1000
      - PGID=1000
    sysctls:
      - net.ipv4.conf.all.src_valid_mark=1
    privileged: true
    restart: unless-stopped
    networks:
      shared:
        ipv4_address: 172.23.0.11
networks:
  shared:
    external: true

 

Mullvad is connected (in container): 

# curl https://am.i.mullvad.net/connected
You are connected to Mullvad (server nl-ams-wg-202). Your IP address is 169.150.196.26

 

Logs on restart: 

[#] ip -4 address add 10.64.221.175/32 dev wg0

2023-04-04 19:06:51,005 DEBG 'start-script' stderr output:
[#] ip link set mtu 1420 up dev wg0

2023-04-04 19:06:51,007 DEBG 'start-script' stderr output:
[#] resolvconf -a wg0 -m 0 -x

2023-04-04 19:06:51,024 DEBG 'start-script' stderr output:
[#] wg set wg0 fwmark 51820

2023-04-04 19:06:51,025 DEBG 'start-script' stderr output:
[#] ip -4 route add 0.0.0.0/0 dev wg0 table 51820

2023-04-04 19:06:51,026 DEBG 'start-script' stderr output:
[#] ip -4 rule add not fwmark 51820 table 51820

2023-04-04 19:06:51,027 DEBG 'start-script' stderr output:
[#] ip -4 rule add table main suppress_prefixlength 0

2023-04-04 19:06:51,030 DEBG 'start-script' stderr output:
[#] sysctl -q net.ipv4.conf.all.src_valid_mark=1

2023-04-04 19:06:51,032 DEBG 'start-script' stderr output:
[#] iptables-restore -n

2023-04-04 19:06:51,035 DEBG 'start-script' stderr output:
[#] '/root/wireguardup.sh'

2023-04-04 19:06:51,040 DEBG 'start-script' stderr output:
egrep: warning: egrep is obsolescent; using grep -E

2023-04-04 19:06:52,045 DEBG 'start-script' stderr output:
egrep: warning: egrep is obsolescent; using grep -E

2023-04-04 19:06:52,052 DEBG 'start-script' stderr output:
egrep: warning: egrep is obsolescent; using grep -E

2023-04-04 19:06:52,078 DEBG 'start-script' stdout output:
[info] Attempting to get external IP using 'http://checkip.amazonaws.com'...

2023-04-04 19:06:52,339 DEBG 'start-script' stderr output:
egrep: warning: egrep is obsolescent; using grep -E

2023-04-04 19:06:52,344 DEBG 'start-script' stdout output:
[info] Successfully retrieved external IP address 192.252.212.46

2023-04-04 19:06:52,345 DEBG 'start-script' stdout output:
[info] WireGuard interface 'up'

2023-04-04 19:06:52,346 DEBG 'start-script' stdout output:
[info] Application does not require port forwarding or VPN provider is != pia, skipping incoming port assignment

2023-04-04 19:06:52,416 DEBG 'watchdog-script' stdout output:
[info] Deluge listening interface IP 0.0.0.0 and VPN provider IP 10.64.221.175 different, marking for reconfigure

2023-04-04 19:06:52,420 DEBG 'watchdog-script' stdout output:
[info] Deluge not running

2023-04-04 19:06:52,423 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI not running

2023-04-04 19:06:52,424 DEBG 'watchdog-script' stdout output:
[info] Attempting to start Deluge...
[info] Removing deluge pid file (if it exists)...

2023-04-04 19:06:52,669 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'listen_interface' currently has a value of '10.64.221.175'
[info] Deluge key 'listen_interface' will have a new value '10.64.221.175'
[info] Writing changes to Deluge config file '/config/core.conf'...

2023-04-04 19:06:52,925 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'outgoing_interface' currently has a value of 'wg0'
[info] Deluge key 'outgoing_interface' will have a new value 'wg0'
[info] Writing changes to Deluge config file '/config/core.conf'...

2023-04-04 19:06:53,195 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'default_daemon' currently has a value of '98ea4cc357404810bfc0e59c34602b4f'
[info] Deluge key 'default_daemon' will have a new value '98ea4cc357404810bfc0e59c34602b4f'
[info] Writing changes to Deluge config file '/config/web.conf'...

2023-04-04 19:06:53,601 DEBG 'watchdog-script' stdout output:
[info] Deluge process started
[info] Waiting for Deluge process to start listening on port 58846...

2023-04-04 19:06:53,813 DEBG 'watchdog-script' stdout output:
[info] Deluge process listening on port 58846

2023-04-04 19:06:56,470 DEBG 'watchdog-script' stderr output:
<Deferred at 0x7f40a394dab0 current result: None>

2023-04-04 19:06:56,555 DEBG 'watchdog-script' stdout output:
[info] No torrents with state 'Error' found

2023-04-04 19:06:56,556 DEBG 'watchdog-script' stdout output:
[info] Starting Deluge Web UI...

2023-04-04 19:06:56,556 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI started

After trying to add a torrent, I get this error (no torrent added): 

2023-04-04 19:09:59,881 DEBG 'watchdog-script' stderr output:
Unhandled error in Deferred:

2023-04-04 19:09:59,884 DEBG 'watchdog-script' stderr output:

Traceback (most recent call last):
  File "/usr/lib/python3.10/site-packages/twisted/internet/defer.py", line 891, in _runCallbacks
    current.result = callback(  # type: ignore[misc]
  File "/usr/lib/python3.10/site-packages/twisted/internet/defer.py", line 1370, in _cbDeferred
    self.callback(cast(_DeferredListResultListT, self.resultList))
  File "/usr/lib/python3.10/site-packages/twisted/internet/defer.py", line 695, in callback
    self._startRunCallbacks(result)
  File "/usr/lib/python3.10/site-packages/twisted/internet/defer.py", line 797, in _startRunCallbacks
    self._runCallbacks()
--- <exception caught here> ---
  File "/usr/lib/python3.10/site-packages/twisted/internet/defer.py", line 891, in _runCallbacks
    current.result = callback(  # type: ignore[misc]
  File "/usr/lib/python3.10/site-packages/deluge/ui/web/json_api.py", line 187, in _on_rpc_request_failed
    return self._send_response(request, response)
  File "/usr/lib/python3.10/site-packages/deluge/ui/web/json_api.py", line 229, in _send_response
    response = json.dumps(response)
  File "/usr/lib/python3.10/json/__init__.py", line 231, in dumps
    return _default_encoder.encode(obj)
  File "/usr/lib/python3.10/json/encoder.py", line 199, in encode
    chunks = self.iterencode(o, _one_shot=True)
  File "/usr/lib/python3.10/json/encoder.py", line 257, in iterencode
    return _iterencode(o, 0)
  File "/usr/lib/python3.10/json/encoder.py", line 179, in default
    raise TypeError(f'Object of type {o.__class__.__name__} '
builtins.TypeError: Object of type Failure is not JSON serializable


2023-04-04 19:09:59,884 DEBG 'watchdog-script' stderr output:
Unhandled error in Deferred:

Traceback (most recent call last):
Failure: deluge.error.NotAuthorizedError: Auth level too low: 0 < 5


 

Link to comment
WexfordStyle Rookie

WexfordStyle

Posted
Posted (edited)

I am also having issues with accessing the WebUI all of a sudden for this container. It just times out...


I am using PIA with wireguard and tried deleting the wg0.conf and starting fresh based on the comment above but no luck.

 

It seems like the container starts OK!?!

 

Container logs are below:

  

2023-04-07 10:09:00,240 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '34242'

2023-04-07 10:09:20,555 DEBG 'watchdog-script' stdout output:
[info] Deluge listening interface IP 0.0.0.0 and VPN provider IP 10.36.156.178 different, marking for reconfigure

2023-04-07 10:09:20,560 DEBG 'watchdog-script' stdout output:
[info] Deluge not running

2023-04-07 10:09:20,565 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI not running

2023-04-07 10:09:20,566 DEBG 'watchdog-script' stdout output:
[info] Deluge incoming port 6890 and VPN incoming port 34242 different, marking for reconfigure

2023-04-07 10:09:20,566 DEBG 'watchdog-script' stdout output:
[info] Attempting to start Deluge...
[info] Removing deluge pid file (if it exists)...

2023-04-07 10:09:21,070 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'listen_interface' currently has a value of '10.11.249.36'
[info] Deluge key 'listen_interface' will have a new value '10.36.156.178'
[info] Writing changes to Deluge config file '/config/core.conf'...

2023-04-07 10:09:21,446 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'outgoing_interface' currently has a value of 'wg0'
[info] Deluge key 'outgoing_interface' will have a new value 'wg0'
[info] Writing changes to Deluge config file '/config/core.conf'...

2023-04-07 10:09:21,789 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'default_daemon' currently has a value of 'c1954debc9694ab798b3aa0100ea3e86'
[info] Deluge key 'default_daemon' will have a new value 'c1954debc9694ab798b3aa0100ea3e86'
[info] Writing changes to Deluge config file '/config/web.conf'...

2023-04-07 10:09:22,274 DEBG 'watchdog-script' stdout output:
[info] Deluge process started
[info] Waiting for Deluge process to start listening on port 58846...

2023-04-07 10:09:22,621 DEBG 'watchdog-script' stdout output:
[info] Deluge process listening on port 58846

2023-04-07 10:09:26,479 DEBG 'watchdog-script' stdout output:
Setting "random_port" to: False
Configuration value successfully updated.

2023-04-07 10:09:26,480 DEBG 'watchdog-script' stderr output:
<Deferred at 0x1463e4293580 current result: None>

2023-04-07 10:09:30,379 DEBG 'watchdog-script' stdout output:
Setting "listen_ports" to: (34242, 34242)
Configuration value successfully updated.

2023-04-07 10:09:30,380 DEBG 'watchdog-script' stderr output:
<Deferred at 0x14d96cc935b0 current result: None>

2023-04-07 10:09:34,583 DEBG 'watchdog-script' stderr output:
<Deferred at 0x1491bcf63400 current result: None>

2023-04-07 10:09:34,666 DEBG 'watchdog-script' stdout output:
[info] No torrents with state 'Error' found

2023-04-07 10:09:34,667 DEBG 'watchdog-script' stdout output:
[info] Starting Deluge Web UI...

2023-04-07 10:09:34,667 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI started

 

Edited by WexfordStyle
Link to comment
nraygun Contributor

nraygun

Posted
Posted
On 3/31/2023 at 12:39 PM, nraygun said:

 

Mine stays up for a while, then overnight it goes into the state you are seeing. I think I have a good ovpn file since it does work upon a restart.

We'll see what happens tomorrow morning since I recreated the container.

So far, so good.

The recreated container seems to be staying up. It even withstood an appdata backup.

Continuing to monitor.

Link to comment
nraygun Contributor

nraygun

Posted
Posted
On 4/8/2023 at 10:41 AM, nraygun said:

So far, so good.

The recreated container seems to be staying up. It even withstood an appdata backup.

Continuing to monitor.

Oh well, so much for that idea.

It went into the error state again. I did a restart and it's back up and seeding a file.

 

Anyone have any ideas why this keeps happening?

Link to comment
nraygun Contributor

nraygun

Posted
Posted
On 4/9/2023 at 1:13 PM, nraygun said:

Oh well, so much for that idea.

It went into the error state again. I did a restart and it's back up and seeding a file.

 

Anyone have any ideas why this keeps happening?

I found another thread that might imply the Deluge problems I'm having and a few server crashes are related.

https://forums.unraid.net/bug-reports/stable-releases/crashes-since-updating-to-v611x-for-qbittorrent-and-deluge-users-r2153/page/8/?tab=comments

Link to comment
gellux Rookie

gellux

Posted
Posted
On 4/7/2023 at 3:12 PM, WexfordStyle said:

I am also having issues with accessing the WebUI all of a sudden for this container. It just times out...


I am using PIA with wireguard and tried deleting the wg0.conf and starting fresh based on the comment above but no luck.

 

It seems like the container starts OK!?!

 

Container logs are below:

  

2023-04-07 10:09:00,240 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '34242'

2023-04-07 10:09:20,555 DEBG 'watchdog-script' stdout output:
[info] Deluge listening interface IP 0.0.0.0 and VPN provider IP 10.36.156.178 different, marking for reconfigure

2023-04-07 10:09:20,560 DEBG 'watchdog-script' stdout output:
[info] Deluge not running

2023-04-07 10:09:20,565 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI not running

2023-04-07 10:09:20,566 DEBG 'watchdog-script' stdout output:
[info] Deluge incoming port 6890 and VPN incoming port 34242 different, marking for reconfigure

2023-04-07 10:09:20,566 DEBG 'watchdog-script' stdout output:
[info] Attempting to start Deluge...
[info] Removing deluge pid file (if it exists)...

2023-04-07 10:09:21,070 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'listen_interface' currently has a value of '10.11.249.36'
[info] Deluge key 'listen_interface' will have a new value '10.36.156.178'
[info] Writing changes to Deluge config file '/config/core.conf'...

2023-04-07 10:09:21,446 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'outgoing_interface' currently has a value of 'wg0'
[info] Deluge key 'outgoing_interface' will have a new value 'wg0'
[info] Writing changes to Deluge config file '/config/core.conf'...

2023-04-07 10:09:21,789 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'default_daemon' currently has a value of 'c1954debc9694ab798b3aa0100ea3e86'
[info] Deluge key 'default_daemon' will have a new value 'c1954debc9694ab798b3aa0100ea3e86'
[info] Writing changes to Deluge config file '/config/web.conf'...

2023-04-07 10:09:22,274 DEBG 'watchdog-script' stdout output:
[info] Deluge process started
[info] Waiting for Deluge process to start listening on port 58846...

2023-04-07 10:09:22,621 DEBG 'watchdog-script' stdout output:
[info] Deluge process listening on port 58846

2023-04-07 10:09:26,479 DEBG 'watchdog-script' stdout output:
Setting "random_port" to: False
Configuration value successfully updated.

2023-04-07 10:09:26,480 DEBG 'watchdog-script' stderr output:
<Deferred at 0x1463e4293580 current result: None>

2023-04-07 10:09:30,379 DEBG 'watchdog-script' stdout output:
Setting "listen_ports" to: (34242, 34242)
Configuration value successfully updated.

2023-04-07 10:09:30,380 DEBG 'watchdog-script' stderr output:
<Deferred at 0x14d96cc935b0 current result: None>

2023-04-07 10:09:34,583 DEBG 'watchdog-script' stderr output:
<Deferred at 0x1491bcf63400 current result: None>

2023-04-07 10:09:34,666 DEBG 'watchdog-script' stdout output:
[info] No torrents with state 'Error' found

2023-04-07 10:09:34,667 DEBG 'watchdog-script' stdout output:
[info] Starting Deluge Web UI...

2023-04-07 10:09:34,667 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI started

 

exactly the same boat here. set it up so long ago i can't even remember what i'll need to do to fix it. let me know if you get it working again!

Link to comment
binhex Mentor

binhex

Posted
  • Author
Posted
On 4/7/2023 at 3:12 PM, WexfordStyle said:

I am also having issues with accessing the WebUI all of a sudden for this container. It just times out...


I am using PIA with wireguard and tried deleting the wg0.conf and starting fresh based on the comment above but no luck.

 

It seems like the container starts OK!?!

 

Container logs are below:

from that snipet yes it looks ok, so i need to see the full log, please do the following:- https://github.com/binhex/documentation/blob/master/docker/faq/help.md

Link to comment
yyc321 Rookie

yyc321

Posted
Posted
On 4/10/2023 at 1:51 PM, nraygun said:

I found another thread that might imply the Deluge problems I'm having and a few server crashes are related.

https://forums.unraid.net/bug-reports/stable-releases/crashes-since-updating-to-v611x-for-qbittorrent-and-deluge-users-r2153/page/8/?tab=comments

I had the same issue posted in this thread.

The update there from JorgeB shows that it's related to libtorrent 2.x.

 

In my case, the unraid gui becomes unresponsive.

 

 

Link to comment
binhex Mentor

binhex

Posted
  • Author
Posted
On 4/10/2023 at 8:51 PM, nraygun said:

I found another thread that might imply the Deluge problems I'm having and a few server crashes are related.

https://forums.unraid.net/bug-reports/stable-releases/crashes-since-updating-to-v611x-for-qbittorrent-and-deluge-users-r2153/page/8/?tab=comments

 

21 hours ago, yyc321 said:

I had the same issue posted in this thread.

The update there from JorgeB shows that it's related to libtorrent 2.x.

 

In my case, the unraid gui becomes unresponsive.

 

 

hi guys, i have been patiently waiting for a fix to libtorrent v2 to drop, sadly its taking longer than expected!, in the meantime i decided to build a new image with libtorrent-rasterbar v1, if you want to give the image a go then append tag name 'libtorrentv1' to the repository name, see Q5 if you are unsure how to do this:- https://github.com/binhex/documentation/blob/master/docker/faq/unraid.md

  • Thanks 2
Link to comment
NAGUnraidNewbie Noob

NAGUnraidNewbie

Posted
Posted

Hi Guys,

 

I'm not overly techie my friend helped me setup my Unraid server previously. I recently moved my unraid server in to a rack mounted case. Since restarting it I cannot get Binhex-DelugeVPN to work correctly, in the past I have issues with the server PIA is directed to and had to change the .ovpn file in the OpenVPN folder and this has usually sorted it but this time to no avail.

 

Could someone look at my Deluge log and give me some pointers on how to sort my issue please?

 

Quote

2023-04-14 22:33:21,141 DEBG 'start-script' stdout output:
[info] morocco.privacy.network
[info] ca-montreal.privacy.network
[info] mk.privacy.network
[info] montenegro.privacy.network
[info] nigeria.privacy.network
[info] georgia.privacy.network
[info] lt.privacy.network
[info] rs.privacy.network
[info] sofia.privacy.network
[info] spain.privacy.network
[info] fi-2.privacy.network
[info] slovenia.privacy.network
[info] sanjose.privacy.network
[info] ee.privacy.network
[info] lu.privacy.network
[info] brussels.privacy.network
[info] fi.privacy.network
[info] japan.privacy.network
[info] cambodia.privacy.network
[info] kualalumpur.privacy.network
[info] bahamas.privacy.network
[info] mexico.privacy.network
[info] swiss.privacy.network
[info] au-sydney.privacy.network
[info] al.privacy.network
[info] de-berlin.privacy.network
[info] ba.privacy.network
[info] austria.privacy.network
[info] uk-southampton.privacy.network
[info] bogota.privacy.network
[info] china.privacy.network
[info] hk.privacy.network
[info] panama.privacy.network
[info] sweden-2.privacy.network
[info] philippines.privacy.network
[info] in.privacy.network
[info] poland.privacy.network
[info] uk-manchester.privacy.network
[info] liechtenstein.privacy.network
[info] pt.privacy.network

2023-04-14 22:33:21,142 DEBG 'start-script' stdout output:
[info] ae.privacy.network
[info] hungary.privacy.network
[info] saudiarabia.privacy.network
[info] denmark.privacy.network
[info] taiwan.privacy.network
[info] sk.privacy.network
[info] de-frankfurt.privacy.network
[info] uk-2.privacy.network
[info] no.privacy.network
[info] bangladesh.privacy.network
[info] jakarta.privacy.network
[info] ca-toronto.privacy.network
[info] france.privacy.network
[info] aus-melbourne.privacy.network
[info] qatar.privacy.network
[info] au-adelaide-pf.privacy.network
[info] vietnam.privacy.network
[info] nl-amsterdam.privacy.network
[info] au-australia-so.privacy.network
[info] br.privacy.network
[info] japan-2.privacy.network

2023-04-14 22:33:23,835 DEBG 'start-script' stdout output:
[warn] Unable to successfully download PIA json to generate token from URL 'https://www.privateinternetaccess.com/gtoken/generateToken'
[info] 12 retries left
[info] Retrying in 10 secs...

2023-04-14 22:33:34,509 DEBG 'start-script' stdout output:
[warn] Unable to successfully download PIA json to generate token from URL 'https://www.privateinternetaccess.com/gtoken/generateToken'
[info] 11 retries left
[info] Retrying in 10 secs...

2023-04-14 22:33:45,177 DEBG 'start-script' stdout output:
[warn] Unable to successfully download PIA json to generate token from URL 'https://www.privateinternetaccess.com/gtoken/generateToken'
[info] 10 retries left
[info] Retrying in 10 secs...

2023-04-14 22:33:55,850 DEBG 'start-script' stdout output:
[warn] Unable to successfully download PIA json to generate token from URL 'https://www.privateinternetaccess.com/gtoken/generateToken'
[info] 9 retries left
[info] Retrying in 10 secs...

2023-04-14 22:34:06,525 DEBG 'start-script' stdout output:
[warn] Unable to successfully download PIA json to generate token from URL 'https://www.privateinternetaccess.com/gtoken/generateToken'
[info] 8 retries left
[info] Retrying in 10 secs...

2023-04-14 22:34:17,198 DEBG 'start-script' stdout output:
[warn] Unable to successfully download PIA json to generate token from URL 'https://www.privateinternetaccess.com/gtoken/generateToken'
[info] 7 retries left
[info] Retrying in 10 secs...

2023-04-14 22:34:27,867 DEBG 'start-script' stdout output:
[warn] Unable to successfully download PIA json to generate token from URL 'https://www.privateinternetaccess.com/gtoken/generateToken'
[info] 6 retries left
[info] Retrying in 10 secs...

2023-04-14 22:34:38,547 DEBG 'start-script' stdout output:
[warn] Unable to successfully download PIA json to generate token from URL 'https://www.privateinternetaccess.com/gtoken/generateToken'
[info] 5 retries left
[info] Retrying in 10 secs...

2023-04-14 22:34:49,219 DEBG 'start-script' stdout output:
[warn] Unable to successfully download PIA json to generate token from URL 'https://www.privateinternetaccess.com/gtoken/generateToken'
[info] 4 retries left
[info] Retrying in 10 secs...

2023-04-14 22:34:59,933 DEBG 'start-script' stdout output:
[warn] Unable to successfully download PIA json to generate token from URL 'https://www.privateinternetaccess.com/gtoken/generateToken'
[info] 3 retries left
[info] Retrying in 10 secs...

2023-04-14 22:35:10,611 DEBG 'start-script' stdout output:
[warn] Unable to successfully download PIA json to generate token from URL 'https://www.privateinternetaccess.com/gtoken/generateToken'
[info] 2 retries left
[info] Retrying in 10 secs...

2023-04-14 22:35:21,276 DEBG 'start-script' stdout output:
[warn] Unable to successfully download PIA json to generate token from URL 'https://www.privateinternetaccess.com/gtoken/generateToken'
[info] 1 retries left
[info] Retrying in 10 secs...

2023-04-14 22:35:31,278 DEBG 'start-script' stdout output:
[warn] Unable to download PIA json to generate token for port forwarding, exiting script...
[info] Port forwarding failure, creating file '/tmp/portfailure' to indicate failure...

2023-04-14 22:35:31,283 DEBG 'start-script' stdout output:
[info] Script finished to assign incoming port

2023-04-14 22:35:31,284 DEBG 'start-script' stdout output:
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]

2023-04-14 22:35:50,873 DEBG 'start-script' stdout output:
[info] Sending SIGTERM (-15) to 'openvpn' due to incoming port allocation failure...

2023-04-14 22:35:50,879 DEBG 'start-script' stdout output:
2023-04-14 22:35:50 event_wait : Interrupted system call (fd=-1,code=4)

2023-04-14 22:35:50,879 DEBG 'start-script' stdout output:
2023-04-14 22:35:50 net_addr_v4_del: 10.18.112.12 dev tun0

2023-04-14 22:35:50,896 DEBG 'start-script' stdout output:
2023-04-14 22:35:50 /root/openvpndown.sh tun0 1500 0 10.18.112.12 255.255.255.0 init

2023-04-14 22:35:50,900 DEBG 'start-script' stdout output:
2023-04-14 22:35:50 SIGTERM[hard,] received, process exiting

2023-04-14 22:35:50,902 DEBG 'start-script' stdout output:
[info] Starting OpenVPN (non daemonised)...

2023-04-14 22:35:50,910 DEBG 'start-script' stdout output:
2023-04-14 22:35:50 DEPRECATED OPTION: --cipher set to 'aes-128-cbc' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM:CHACHA20-POLY1305). OpenVPN ignores --cipher for cipher negotiations. 

2023-04-14 22:35:50,910 DEBG 'start-script' stdout output:
2023-04-14 22:35:50 WARNING: file 'credentials.conf' is group or others accessible
2023-04-14 22:35:50 OpenVPN 2.6.0 [git:makepkg/b999466418dddb89+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Jan 25 2023
2023-04-14 22:35:50 library versions: OpenSSL 3.0.8 7 Feb 2023, LZO 2.10

2023-04-14 22:35:50,910 DEBG 'start-script' stdout output:
2023-04-14 22:35:50 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

2023-04-14 22:35:50,911 DEBG 'start-script' stdout output:
2023-04-14 22:35:50 CRL: loaded 1 CRLs from file -----BEGIN X509 CRL-----
MIICWDCCAUAwDQYJKoZIhvcNAQENBQAwgegxCzAJBgNVBAYTAlVTMQswCQYDVQQI
EwJDQTETMBEGA1UEBxMKTG9zQW5nZWxlczEgMB4GA1UEChMXUHJpdmF0ZSBJbnRl
cm5ldCBBY2Nlc3MxIDAeBgNVBAsTF1ByaXZhdGUgSW50ZXJuZXQgQWNjZXNzMSAw
HgYDVQQDExdQcml2YXRlIEludGVybmV0IEFjY2VzczEgMB4GA1UEKRMXUHJpdmF0
ZSBJbnRlcm5ldCBBY2Nlc3MxLzAtBgkqhkiG9w0BCQEWIHNlY3VyZUBwcml2YXRl
aW50ZXJuZXRhY2Nlc3MuY29tFw0xNjA3MDgxOTAwNDZaFw0zNjA3MDMxOTAwNDZa
MCYwEQIBARcMMTYwNzA4MTkwMDQ2MBECAQYXDDE2MDcwODE5MDA0NjANBgkqhkiG
9w0BAQ0FAAOCAQEAQZo9X97ci8EcPYu/uK2HB152OZbeZCINmYyluLDOdcSvg6B5
jI+ffKN3laDvczsG6CxmY3jNyc79XVpEYUnq4rT3FfveW1+Ralf+Vf38HdpwB8EW
B4hZlQ205+21CALLvZvR8HcPxC9KEnev1mU46wkTiov0EKc+EdRxkj5yMgv0V2Re
ze7AP+NQ9ykvDScH4eYCsmufNpIjBLhpLE2cuZZXBLcPhuRzVoU3l7A9lvzG9mjA
5YijHJGHNjlWFqyrn1CfYS6koa4TGEPngBoAziWRbDGdhEgJABHrpoaFYaL61zqy
MR6jC0K2ps9qyZAN74LEBedEfK7tBOzWMwr58A==
-----END X509 CRL-----


2023-04-14 22:35:50,911 DEBG 'start-script' stdout output:
2023-04-14 22:35:50 TCP/UDP: Preserving recently used remote address: [AF_INET]181.214.153.207:1198
2023-04-14 22:35:50 UDPv4 link local: (not bound)
2023-04-14 22:35:50 UDPv4 link remote: [AF_INET]181.214.153.207:1198

2023-04-14 22:35:51,542 DEBG 'start-script' stdout output:
2023-04-14 22:35:51 [vancouver426] Peer Connection Initiated with [AF_INET]181.214.153.207:1198

2023-04-14 22:35:51,713 DEBG 'start-script' stdout output:
2023-04-14 22:35:51 TUN/TAP device tun0 opened
2023-04-14 22:35:51 net_iface_mtu_set: mtu 1500 for tun0
2023-04-14 22:35:51 net_iface_up: set tun0 up
2023-04-14 22:35:51 net_addr_v4_add: 10.18.112.12/24 dev tun0

2023-04-14 22:35:51,713 DEBG 'start-script' stdout output:
2023-04-14 22:35:51 /root/openvpnup.sh tun0 1500 0 10.18.112.12 255.255.255.0 init

2023-04-14 22:35:51,716 DEBG 'start-script' stdout output:
2023-04-14 22:35:51 Initialization Sequence Completed

2023-04-14 22:36:38,962 DEBG 'start-script' stdout output:
[info] Attempting to get external IP using 'http://checkip.amazonaws.com'...

2023-04-14 22:36:44,971 DEBG 'start-script' stdout output:
[info] Successfully retrieved external IP address 181.214.153.207

2023-04-14 22:36:44,973 DEBG 'start-script' stdout output:
[info] Script started to assign incoming port

2023-04-14 22:36:44,974 DEBG 'start-script' stdout output:
[info] Port forwarding is enabled
[info] Checking endpoint 'ca-vancouver.privacy.network' is port forward enabled...

2023-04-14 22:36:45,897 DEBG 'start-script' stdout output:
[info] PIA endpoint 'ca-vancouver.privacy.network' is in the list of endpoints that support port forwarding

2023-04-14 22:36:45,898 DEBG 'start-script' stdout output:
[info] List of PIA endpoints that support port forwarding:-

2023-04-14 22:36:45,898 DEBG 'start-script' stdout output:
[info] denmark-2.privacy.network
[info] ad.privacy.network
[info] fi-2.privacy.network
[info] monaco.privacy.network
[info] ua.privacy.network
[info] macau.privacy.network
[info] za.privacy.network
[info] ca-montreal.privacy.network
[info] denmark.privacy.network
[info] nl-amsterdam.privacy.network
[info] liechtenstein.privacy.network
[info] slovenia.privacy.network
[info] no.privacy.network
[info] tr.privacy.network
[info] sweden-2.privacy.network

2023-04-14 22:36:45,898 DEBG 'start-script' stdout output:
[info] bahamas.privacy.network
[info] poland.privacy.network
[info] vietnam.privacy.network
[info] mexico.privacy.network
[info] au-australia-so.privacy.network
[info] ca-vancouver.privacy.network
[info] ro.privacy.network
[info] sweden.privacy.network
[info] lu.privacy.network
[info] sofia.privacy.network
[info] hungary.privacy.network
[info] es-valencia.privacy.network
[info] fi.privacy.network
[info] zagreb.privacy.network
[info] egypt.privacy.network
[info] hk.privacy.network
[info] de-frankfurt.privacy.network
[info] aus-melbourne.privacy.network
[info] uk-london.privacy.network
[info] georgia.privacy.network
[info] lv.privacy.network
[info] mk.privacy.network
[info] morocco.privacy.network
[info] md.privacy.network
[info] sanjose.privacy.network
[info] sg.privacy.network
[info] br.privacy.network
[info] czech.privacy.network
[info] jakarta.privacy.network
[info] man.privacy.network
[info] spain.privacy.network
[info] srilanka.privacy.network
[info] rs.privacy.network
[info] ireland.privacy.network
[info] aus-perth.privacy.network
[info] gr.privacy.network
[info] malta.privacy.network

2023-04-14 22:36:45,899 DEBG 'start-script' stdout output:
[info] ae.privacy.network
[info] ar.privacy.network
[info] ca-toronto.privacy.network
[info] dz.privacy.network
[info] cyprus.privacy.network
[info] philippines.privacy.network
[info] pt.privacy.network
[info] uk-2.privacy.network
[info] uk-manchester.privacy.network
[info] cambodia.privacy.network
[info] panama.privacy.network
[info] de-berlin.privacy.network
[info] montenegro.privacy.network
[info] austria.privacy.network
[info] italy-2.privacy.network
[info] uk-southampton.privacy.network
[info] bangladesh.privacy.network
[info] in.privacy.network
[info] kualalumpur.privacy.network
[info] au-adelaide-pf.privacy.network
[info] israel.privacy.network
[info] kazakhstan.privacy.network
[info] saudiarabia.privacy.network
[info] china.privacy.network
[info] santiago.privacy.network
[info] yerevan.privacy.network
[info] italy.privacy.network
[info] qatar.privacy.network
[info] au-sydney.privacy.network
[info] swiss.privacy.network
[info] ca-ontario.privacy.network
[info] venezuela.privacy.network
[info] sk.privacy.network
[info] france.privacy.network
[info] nigeria.privacy.network
[info] taiwan.privacy.network
[info] ee.privacy.network
[info] mongolia.privacy.network
[info] al.privacy.network
[info] brussels.privacy.network
[info] is.privacy.network
[info] ba.privacy.network
[info] bogota.privacy.network
[info] japan-2.privacy.network
[info] greenland.privacy.network
[info] japan.privacy.network
[info] au-brisbane-pf.privacy.network
[info] lt.privacy.network
[info] nz.privacy.network

2023-04-14 22:36:48,587 DEBG 'start-script' stdout output:
[warn] Unable to successfully download PIA json to generate token from URL 'https://www.privateinternetaccess.com/gtoken/generateToken'
[info] 12 retries left
[info] Retrying in 10 secs...

2023-04-14 22:36:59,254 DEBG 'start-script' stdout output:
[warn] Unable to successfully download PIA json to generate token from URL 'https://www.privateinternetaccess.com/gtoken/generateToken'
[info] 11 retries left
[info] Retrying in 10 secs...

2023-04-14 22:37:09,922 DEBG 'start-script' stdout output:
[warn] Unable to successfully download PIA json to generate token from URL 'https://www.privateinternetaccess.com/gtoken/generateToken'
[info] 10 retries left
[info] Retrying in 10 secs...

2023-04-14 22:37:20,592 DEBG 'start-script' stdout output:
[warn] Unable to successfully download PIA json to generate token from URL 'https://www.privateinternetaccess.com/gtoken/generateToken'
[info] 9 retries left
[info] Retrying in 10 secs...

2023-04-14 22:37:31,259 DEBG 'start-script' stdout output:
[warn] Unable to successfully download PIA json to generate token from URL 'https://www.privateinternetaccess.com/gtoken/generateToken'
[info] 8 retries left
[info] Retrying in 10 secs...

2023-04-14 22:37:41,932 DEBG 'start-script' stdout output:
[warn] Unable to successfully download PIA json to generate token from URL 'https://www.privateinternetaccess.com/gtoken/generateToken'
[info] 7 retries left
[info] Retrying in 10 secs...

2023-04-14 22:37:52,604 DEBG 'start-script' stdout output:
[warn] Unable to successfully download PIA json to generate token from URL 'https://www.privateinternetaccess.com/gtoken/generateToken'
[info] 6 retries left
[info] Retrying in 10 secs...

2023-04-14 22:38:03,274 DEBG 'start-script' stdout output:
[warn] Unable to successfully download PIA json to generate token from URL 'https://www.privateinternetaccess.com/gtoken/generateToken'
[info] 5 retries left
[info] Retrying in 10 secs...

2023-04-14 22:38:13,950 DEBG 'start-script' stdout output:
[warn] Unable to successfully download PIA json to generate token from URL 'https://www.privateinternetaccess.com/gtoken/generateToken'
[info] 4 retries left
[info] Retrying in 10 secs...

2023-04-14 22:38:24,625 DEBG 'start-script' stdout output:
[warn] Unable to successfully download PIA json to generate token from URL 'https://www.privateinternetaccess.com/gtoken/generateToken'
[info] 3 retries left
[info] Retrying in 10 secs...

2023-04-14 22:38:35,302 DEBG 'start-script' stdout output:
[warn] Unable to successfully download PIA json to generate token from URL 'https://www.privateinternetaccess.com/gtoken/generateToken'
[info] 2 retries left
[info] Retrying in 10 secs...

2023-04-14 22:38:45,975 DEBG 'start-script' stdout output:
[warn] Unable to successfully download PIA json to generate token from URL 'https://www.privateinternetaccess.com/gtoken/generateToken'
[info] 1 retries left
[info] Retrying in 10 secs...

2023-04-14 22:38:55,976 DEBG 'start-script' stdout output:
[warn] Unable to download PIA json to generate token for port forwarding, exiting script...
[info] Port forwarding failure, creating file '/tmp/portfailure' to indicate failure...

2023-04-14 22:38:55,979 DEBG 'start-script' stdout output:
[info] Script finished to assign incoming port

2023-04-14 22:38:55,980 DEBG 'start-script' stdout output:
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]

2023-04-14 22:39:20,891 DEBG 'start-script' stdout output:
[info] Sending SIGTERM (-15) to 'openvpn' due to incoming port allocation failure...

2023-04-14 22:39:20,897 DEBG 'start-script' stdout output:
2023-04-14 22:39:20 event_wait : Interrupted system call (fd=-1,code=4)

2023-04-14 22:39:20,897 DEBG 'start-script' stdout output:
2023-04-14 22:39:20 net_addr_v4_del: 10.18.112.12 dev tun0

2023-04-14 22:39:20,908 DEBG 'start-script' stdout output:
2023-04-14 22:39:20 /root/openvpndown.sh tun0 1500 0 10.18.112.12 255.255.255.0 init

2023-04-14 22:39:20,913 DEBG 'start-script' stdout output:
2023-04-14 22:39:20 SIGTERM[hard,] received, process exiting

2023-04-14 22:39:20,915 DEBG 'start-script' stdout output:
[info] Starting OpenVPN (non daemonised)...

2023-04-14 22:39:20,922 DEBG 'start-script' stdout output:
2023-04-14 22:39:20 DEPRECATED OPTION: --cipher set to 'aes-128-cbc' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM:CHACHA20-POLY1305). OpenVPN ignores --cipher for cipher negotiations. 

2023-04-14 22:39:20,923 DEBG 'start-script' stdout output:
2023-04-14 22:39:20 WARNING: file 'credentials.conf' is group or others accessible
2023-04-14 22:39:20 OpenVPN 2.6.0 [git:makepkg/b999466418dddb89+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Jan 25 2023
2023-04-14 22:39:20 library versions: OpenSSL 3.0.8 7 Feb 2023, LZO 2.10

2023-04-14 22:39:20,923 DEBG 'start-script' stdout output:
2023-04-14 22:39:20 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

2023-04-14 22:39:20,925 DEBG 'start-script' stdout output:
2023-04-14 22:39:20 CRL: loaded 1 CRLs from file -----BEGIN X509 CRL-----
MIICWDCCAUAwDQYJKoZIhvcNAQENBQAwgegxCzAJBgNVBAYTAlVTMQswCQYDVQQI
EwJDQTETMBEGA1UEBxMKTG9zQW5nZWxlczEgMB4GA1UEChMXUHJpdmF0ZSBJbnRl
cm5ldCBBY2Nlc3MxIDAeBgNVBAsTF1ByaXZhdGUgSW50ZXJuZXQgQWNjZXNzMSAw
HgYDVQQDExdQcml2YXRlIEludGVybmV0IEFjY2VzczEgMB4GA1UEKRMXUHJpdmF0
ZSBJbnRlcm5ldCBBY2Nlc3MxLzAtBgkqhkiG9w0BCQEWIHNlY3VyZUBwcml2YXRl
aW50ZXJuZXRhY2Nlc3MuY29tFw0xNjA3MDgxOTAwNDZaFw0zNjA3MDMxOTAwNDZa
MCYwEQIBARcMMTYwNzA4MTkwMDQ2MBECAQYXDDE2MDcwODE5MDA0NjANBgkqhkiG
9w0BAQ0FAAOCAQEAQZo9X97ci8EcPYu/uK2HB152OZbeZCINmYyluLDOdcSvg6B5
jI+ffKN3laDvczsG6CxmY3jNyc79XVpEYUnq4rT3FfveW1+Ralf+Vf38HdpwB8EW
B4hZlQ205+21CALLvZvR8HcPxC9KEnev1mU46wkTiov0EKc+EdRxkj5yMgv0V2Re
ze7AP+NQ9ykvDScH4eYCsmufNpIjBLhpLE2cuZZXBLcPhuRzVoU3l7A9lvzG9mjA
5YijHJGHNjlWFqyrn1CfYS6koa4TGEPngBoAziWRbDGdhEgJABHrpoaFYaL61zqy
MR6jC0K2ps9qyZAN74LEBedEfK7tBOzWMwr58A==
-----END X509 CRL-----


2023-04-14 22:39:20,925 DEBG 'start-script' stdout output:
2023-04-14 22:39:20 TCP/UDP: Preserving recently used remote address: [AF_INET]181.214.153.207:1198
2023-04-14 22:39:20 UDPv4 link local: (not bound)
2023-04-14 22:39:20 UDPv4 link remote: [AF_INET]181.214.153.207:1198

2023-04-14 22:39:21,564 DEBG 'start-script' stdout output:
2023-04-14 22:39:21 [vancouver426] Peer Connection Initiated with [AF_INET]181.214.153.207:1198

2023-04-14 22:39:21,736 DEBG 'start-script' stdout output:
2023-04-14 22:39:21 TUN/TAP device tun0 opened
2023-04-14 22:39:21 net_iface_mtu_set: mtu 1500 for tun0
2023-04-14 22:39:21 net_iface_up: set tun0 up
2023-04-14 22:39:21 net_addr_v4_add: 10.18.112.12/24 dev tun0

2023-04-14 22:39:21,736 DEBG 'start-script' stdout output:
2023-04-14 22:39:21 /root/openvpnup.sh tun0 1500 0 10.18.112.12 255.255.255.0 init

2023-04-14 22:39:21,739 DEBG 'start-script' stdout output:
2023-04-14 22:39:21 Initialization Sequence Completed

2023-04-14 22:39:38,960 DEBG 'start-script' stdout output:
[info] Attempting to get external IP using 'http://checkip.amazonaws.com'...

 

Link to comment
NAGUnraidNewbie Noob

NAGUnraidNewbie

Posted
Posted
9 minutes ago, NAGUnraidNewbie said:

Hi Guys,

 

I'm not overly techie my friend helped me setup my Unraid server previously. I recently moved my unraid server in to a rack mounted case. Since restarting it I cannot get Binhex-DelugeVPN to work correctly, in the past I have issues with the server PIA is directed to and had to change the .ovpn file in the OpenVPN folder and this has usually sorted it but this time to no avail.

 

Could someone look at my Deluge log and give me some pointers on how to sort my issue please?

 

 

If it makes a difference from memory (as this has been an on going saga for a few months) I also upgrade my Unraid OS to the latest 6.11.5, I was previously on 6.9.2. I haven't tried rolling that back

Link to comment
WexfordStyle Rookie

WexfordStyle

Posted
Posted
On 4/11/2023 at 4:47 AM, binhex said:

from that snipet yes it looks ok, so i need to see the full log, please do the following:- https://github.com/binhex/documentation/blob/master/docker/faq/help.md

 

I just came back here to follow-up and saw your post. When I went to do the steps in the link and tried to access the website and it randomly is working again!?

 

Was there a fix for something?

Link to comment
binhex Mentor

binhex

Posted
  • Author
Posted
2 hours ago, WexfordStyle said:

 

I just came back here to follow-up and saw your post. When I went to do the steps in the link and tried to access the website and it randomly is working again!?

 

Was there a fix for something?

no fix from me.

Link to comment
hios Noob

hios

Posted
Posted

My container started throwing DNS failures last night out of nowhere. It's been running for the last year+ with no problems. I did restart the server twice during that time while trying to fix an encrypted volume that wouldn't unmount, but it wasn't in any way related to deluge. What's odd is that my binhex-sabnzbdvpn container is working just fine, with the same config. All other containers and Unraid are working just fine. I've tried:

  • Stopping/restarting the container multiple times
  • Restarting the server
  • Changing the DNS servers back to the default (I was using Mullvad's, and am still using Mullvad's for sabnzbd)

I could easily be wrong, but based on the logs it seems like the vpn starts up and gets a public IP. However, I can't ping from the container and a website port checker says the connection isn't open. My logs are attached and I'd appreciate any thoughts, as I've spent a few hours on this today and didn't get anywhere.

supervisord.log

Link to comment
hios Noob

hios

Posted
Posted
10 hours ago, hios said:

My container started throwing DNS failures last night out of nowhere. It's been running for the last year+ with no problems. I did restart the server twice during that time while trying to fix an encrypted volume that wouldn't unmount, but it wasn't in any way related to deluge. What's odd is that my binhex-sabnzbdvpn container is working just fine, with the same config. All other containers and Unraid are working just fine. I've tried:

 

Generating a new Mullvad config fixed it. No clue why the old one stopped working all of a sudden.

Link to comment
Xoron Noob

Xoron

Posted
Posted (edited)
On 4/14/2023 at 4:51 PM, NAGUnraidNewbie said:

If it makes a difference from memory (as this has been an on going saga for a few months) I also upgrade my Unraid OS to the latest 6.11.5, I was previously on 6.9.2. I haven't tried rolling that back

I'm having the same deluge no WebUi issue since updating to 6.11.5 today.  I too am using Mullvad VPN for the docker image.  I'm getting the same exact message in the logs that I've seen mentioned elsewhere

  

[info] Deluge process started
[info] Waiting for Deluge process to start listening on port 58846...

 

What I've tried so far

  • Force Updating the Deluge VPN Container
  • Removing the container, and reinstalling it
  • Generated a new Mullvad OVPN file
  • Changed DNS servers around in the Container config

I think my VPN is actually up, just the WebUI for Deluge won't load.  I can actually access the Web UI of my other dockers that I route through Deluge VPN.

 

Following this thread for a solution. 

Edited by Xoron
Link to comment
JEThree Noob

JEThree

Posted
Posted

Hello,

Love the apps, thank you.
Having trouble with deluge vpn crashing and not starting.
Currently in a boot cycle.


2023-04-19 04:12:09,434 DEBG 'start-script' stdout output:
2023-04-19 04:12:09 WARNING: file 'credentials.conf' is group or others accessible
2023-04-19 04:12:09 OpenVPN 2.6.0 [git:makepkg/b999466418dddb89+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Jan 25 2023

2023-04-19 04:12:09,434 DEBG 'start-script' stdout output:
2023-04-19 04:12:09 library versions: OpenSSL 3.0.8 7 Feb 2023, LZO 2.10

2023-04-19 04:12:10,434 DEBG 'start-script' stdout output:
2023-04-19 04:12:10 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

2023-04-19 04:12:10,437 DEBG 'start-script' stdout output:
2023-04-19 04:12:10 TCP/UDP: Preserving recently used remote address: [AF_INET]IP:PORT
2023-04-19 04:12:10 UDPv4 link local: (not bound)
2023-04-19 04:12:10 UDPv4 link remote: [AF_INET](IP:PORT)

2023-04-19 04:13:10,966 DEBG 'start-script' stdout output:
2023-04-19 04:13:10 [UNDEF] Inactivity timeout (--ping-restart), restarting

2023-04-19 04:13:10,967 DEBG 'start-script' stdout output:
2023-04-19 04:13:10 SIGHUP[soft,ping-restart] received, process restarting

2023-04-19 04:13:10,968 DEBG 'start-script' stdout output:
2023-04-19 04:13:10 DEPRECATED OPTION: --cipher set to 'AES-128-CBC' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM:CHACHA20-POLY1305). OpenVPN ignores --cipher for cipher negotiations.

It seems to not load my credentials and doesn't load the GUI.

It's been working for months, happened before but restarts fixed it.
Had all the -arr apps using it with no problem. Has crashed before, can't see the logs because reasons.
Have tried privileged mode to no success.

Can't see memory runaway or crash info because it's too late before I find it.

Any help would be great.

Link to comment
Xoron Noob

Xoron

Posted
Posted (edited)
8 hours ago, Xoron said:

I'm having the same deluge no WebUi issue since updating to 6.11.5 today.  I too am using Mullvad VPN for the docker image.  I'm getting the same exact message in the logs that I've seen mentioned elsewhere

  

[info] Deluge process started
[info] Waiting for Deluge process to start listening on port 58846...

 

What I've tried so far

  • Force Updating the Deluge VPN Container
  • Removing the container, and reinstalling it
  • Generated a new Mullvad OVPN file
  • Changed DNS servers around in the Container config

I think my VPN is actually up, just the WebUI for Deluge won't load.  I can actually access the Web UI of my other dockers that I route through Deluge VPN.

 

Following this thread for a solution. 

I resolved my issue by looking deep into the deluge logs.

 

First, I was getting an error that /config/ssl/daemon.cert could not be read. It has permissions of 600 and was owned by root:root.  I changed permissions to 666 on the file.

  

chmod 666 /config/ssl/daemon.*

 

Next it was throwing the same error in /config/auth.  So I performed the same chmod on it

  

chmod 666 /config/auth

 

Now I no longer get the never get the error below, and the GUI loads correctly:

  

[info] Deluge process started
[info] Waiting for Deluge process to start listening on port 58846...
Edited by Xoron
Link to comment
binhex Mentor

binhex

Posted
  • Author
Posted
1 minute ago, Xoron said:

since updating to 6.11.5 today.

that is your issue, unraid has a bug where upgrading to 6.11.x can sometimes screw up permissions, it doesn't happen for all users (luckily i was unaffected) hopefully this is a one time pain and fingers crossed no such issue should occur when upgrading unraid in the future.

  • Thanks 1
Link to comment
Inch Noob

Inch

Posted
Posted (edited)

Hi Binhex, 

First, thank you for all the effort you've put into this. I've setup the delugevpn docker container, I can even see it connecting to the vpn provider i use, when i login to console and run ifconfig.io etc. 

I'm having issues running Radar and Sonarr through it, it seems to just not be routing the ports properly (getting timeouts when i go to the <serverip>:port), and I've added them to input/output port fields. Is the issue I'm running into related to the above mention of a library fix being needed? 

Attached the log file with debug enabled. 

P.S. I've already ran: /sbin/modprobe iptable_mangle.

supervisord.log

Edited by Inch
Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
Go to topic listing