[[Support] binhex - qBittorrentVPN]

4 hours ago, chancedonmillion said:

I noticed that my qBittorrent web UI was down so I came to this thread and saw the discussion regarding the "cannot allocate 4611686018427387903 bytes" issue.

I tailed the containers logs and sure enough, that is what I was seeing.

2020-03-30 20:49:11,570 DEBG 'start-script' stderr output:
pgrep: cannot allocate 4611686018427387903 bytes

I upgraded to the latest which fixed the "cannot allocate 4611686018427387903 bytes" issue.

However the container is still failing to start.

This is what I am seeing at in the logs currently.

2020-03-30 21:13:47,329 DEBG 'start-script' stdout output:
[info] Attempting to curl http://209.222.18.222:2000/?client_id=adb8c2b559fdde17f847119ecdeb1c8fda5b852953313e0488ef16f2bdb45a52...

2020-03-30 21:13:47,429 DEBG 'start-script' stdout output:
[warn] Response code 000 from curl != 2xx
[warn] Exit code 56 from curl != 0
[info] 12 retries left
[info] Retrying in 10 secs...

...

2020-03-30 21:15:38,565 DEBG 'start-script' stdout output:
[warn] Response code 000 from curl != 2xx
[warn] Exit code 56 from curl != 0
[info] 1 retries left
[info] Retrying in 10 secs...

2020-03-30 21:15:48,670 DEBG 'start-script' stdout output:
[warn] Response code 000 from curl != 2xx, exhausted retries exiting script...

2020-03-30 21:15:48,670 DEBG 'start-script' stdout output:
[warn] PIA VPN port assignment API currently down, terminating OpenVPN process to force retry for incoming port...

 

Google tells me that code 56 is known to occur when the network adapter has a conflict with the third-party VPN installed on your system.

I would really appreciate any insight as to why the adapter has a conflict with the third-party VPN and what I may be able to do as a workaround. 

I also tried deleting the image and reinstalling the container, same issue.

I am getting the same thing. Not sure if it is the container or on pia's side. if you change STRICT_PORT_FORWARD to no in the docker settings it should get you back running.