Deluge WebUI not accessible, when VPN is on

[FalconX14]

I have the same problem, like an other user mentioned here at reddit (can't access Deluge WebUI, with VPN turned on).
https://www.reddit.com/r/docker/comments/bl24mu/ledokunarmhfarchdelugevpn/

I am using Ivacy VPN and I also don't know, who I can tell the Docker container to connect to a specific country?

My Log:
Wed Dec 18 10:44:56 2019 do_ifconfig, tt->did_ifconfig_ipv6_setup=0,
Wed Dec 18 10:44:56 2019 /usr/bin/ip link set dev tun0 up mtu 1500,
,
2019-12-18 10:44:56,609 DEBG 'start-script' stdout output:,
Wed Dec 18 10:44:56 2019 /usr/bin/ip addr add dev tun0 172.111.147.132/26 broadcast 172.111.147.191,
,
2019-12-18 10:44:56,615 DEBG 'start-script' stdout output:,
Wed Dec 18 10:44:56 2019 /root/openvpnup.sh tun0 1500 1560 172.111.147.132 255.255.255.192 init,
,
2019-12-18 10:44:56,653 DEBG 'start-script' stdout output:,
[debug] Waiting for valid IP address from tunnel...,
[debug] Waiting for valid IP address from tunnel...,
,
2019-12-18 10:44:56,747 DEBG 'privoxy-script' stdout output:,
[debug] Valid IP address from tunnel acquired '172.111.147.132',
[info] Configuring Privoxy...,
,
2019-12-18 10:44:56,754 DEBG 'start-script' stdout output:,
[debug] Valid IP address from tunnel acquired '172.111.147.132',
,
2019-12-18 10:44:56,840 DEBG 'deluge-script' stdout output:,
[debug] Valid IP address from tunnel acquired '172.111.147.132',
,
2019-12-18 10:44:56,861 DEBG 'deluge-script' stdout output:,
[info] Deluge not running,
[info] Deluge listening interface IP 0.0.0.0 and VPN provider IP 172.111.147.132 different, marking for reconfigure,
[info] Attempting to start Deluge...,
,
2019-12-18 10:44:56,875 DEBG 'start-script' stdout output:,
[debug] Valid IP address from tunnel acquired '172.111.147.132',
[debug] Valid IP address from tunnel acquired '172.111.147.132',
,
2019-12-18 10:44:56,879 DEBG 'start-script' stdout output:,
[debug] Attempting to get external IP using Name Server 'ns1.google.com'...,
,
2019-12-18 10:44:56,882 DEBG 'start-script' stdout output:,
[debug] VPN provider custom is != pia, skipping incoming port detection,
,
2019-12-18 10:44:56,938 DEBG 'privoxy-script' stdout output:,
[info] All checks complete, starting Privoxy...,
,
2019-12-18 10:44:56,974 DEBG 'privoxy-script' stderr output:,
2019-12-18 10:44:56.972 f6eb8010 Info: Privoxy version 3.0.26,
2019-12-18 10:44:56.972 f6eb8010 Info: Program name: /usr/bin/privoxy,
,
2019-12-18 10:44:56,979 DEBG 'start-script' stdout output:,
[debug] Failed to get external IP using Name Server 'ns1.google.com', trying 'resolver1.opendns.com'...,
,
2019-12-18 10:44:57,041 DEBG 'start-script' stdout output:,
[debug] Cannot determine external IP address, retrying...,
,
2019-12-18 10:44:58,046 DEBG 'start-script' stdout output:,
[debug] Attempting to get external IP using Name Server 'ns1.google.com'...,
,
2019-12-18 10:44:58,133 DEBG 'start-script' stdout output:,
[debug] Failed to get external IP using Name Server 'ns1.google.com', trying 'resolver1.opendns.com'...,
,
2019-12-18 10:44:58,193 DEBG 'start-script' stdout output:,
[debug] Cannot determine external IP address, retrying...,
,
2019-12-18 10:44:58,229 DEBG 'deluge-script' stdout output:,
[info] Deluge listening interface currently defined as 172.111.147.132,
[info] Deluge listening interface will be changed to 172.111.147.132,
[info] Saving changes to Deluge config file /config/core.conf...,
,
2019-12-18 10:44:58,768 DEBG 'start-script' stdout output:,
RTNETLINK answers: File exists,
,
2019-12-18 10:44:58,772 DEBG 'start-script' stdout output:,
Wed Dec 18 10:44:58 2019 ERROR: Linux route add command failed: external program exited with error status: 2,
Wed Dec 18 10:44:58 2019 Initialization Sequence Completed,
,
2019-12-18 10:44:59,199 DEBG 'start-script' stdout output:,
[debug] Attempting to get external IP using Name Server 'ns1.google.com'...,
,
2019-12-18 10:44:59,521 DEBG 'deluge-script' stdout output:,
[info] Deluge started,
[debug] VPN incoming port is ,
[debug] VPN IP is 172.111.147.132,
[debug] Deluge incoming port is ,
[debug] Deluge IP is 172.111.147.132,
,
2019-12-18 10:45:02,590 DEBG 'deluge-web-script' stdout output:,
[info] Starting Deluge webui...,
,
2019-12-18 10:45:05,664 DEBG 'start-script' stdout output:,
[info] Successfully retrieved external IP address 172.111.147.132,
,
2019-12-18 10:45:29,529 DEBG 'deluge-script' stdout output:,
[debug] Waiting for valid IP address from tunnel...,
,
2019-12-18 10:45:29,728 DEBG 'deluge-script' stdout output:,
[debug] Valid IP address from tunnel acquired '172.111.147.132',
,
2019-12-18 10:45:29,746 DEBG 'deluge-script' stdout output:,
[debug] VPN incoming port is ,
[debug] VPN IP is 172.111.147.132,
[debug] Deluge incoming port is ,
[debug] Deluge IP is 172.111.147.132,
,

[usmcamp0811]

I've got the same issues going on... was working then I restarted the container and got this..

[usmcamp0811]

found the answer in the FAQ of all places..

Q10. I can't connect to the Web UI and i see the following repeated over and over in the logs, what does mean and how do i fix it?

2018-04-02 21:13:42,659 DEBG 'start-script' stdout output:
[warn] Response code 000 from curl != 2xx
[warn] Exit code 7 from curl != 0
[info] 4 retries left
[info] Retrying in 10 secs...
A10. The above message means that you have env var 'STRICT_PORT_FORWARD' set to a value of 'yes' but the endpoint you are connecting to does NOT support port forwarding. For a current list of port forward enabled endpoints for PIA, see the link below:-

https://www.privateinternetaccess.com/helpdesk/kb/articles/how-do-i-enable-port-forwarding-on-my-vpn

The alternative to this is to set env var 'STRICT_PORT_FORWARD' value to 'no', this will then skip any port forwarding and allow you to connect to ANY PIA endpoint independent of whether it supports port forwarding or not (not recommended).

Note:- The above is ONLY true for PIA users, the env var 'STRICT_PORT_FORWARD' does nothing for any other VPN providers.