You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
STARTING TINYPROXY
Setting tinyproxy port to 8888
Starting tinyproxy: tinyproxy.
Tinyproxy startup script complete.
RTNETLINK answers: File exists
Fri Jan 11 16:31:20 2019 ERROR: Linux route add command failed: external program exited with error status: 2
Fri Jan 11 16:31:20 2019 Initialization Sequence Completed
I have followed the instructions (proper username and password for IVACY), using the latest build with updated IVACY certs, I cannot figure out why I am receiving error status 2.
Anyone have a similar issue?
EDIT: full log:
Using OpenVPN provider: IVACY
Starting OpenVPN using config CanadaTorontoTCP.ovpn
Setting OPENVPN credentials...
Fri Jan 11 19:21:05 2019 WARNING: file '/etc/openvpn/ivacy/Wdc.key' is group or others accessible
Fri Jan 11 19:21:05 2019 OpenVPN 2.4.6 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Apr 24 2018
Fri Jan 11 19:21:05 2019 library versions: OpenSSL 1.0.2g 1 Mar 2016, LZO 2.08
Fri Jan 11 19:21:05 2019 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
Fri Jan 11 19:21:05 2019 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Fri Jan 11 19:21:05 2019 TCP/UDP: Preserving recently used remote address: [AF_INET]172.111.177.2:80
Fri Jan 11 19:21:05 2019 Attempting to establish TCP connection with [AF_INET]172.111.177.2:80 [nonblock]
Fri Jan 11 19:21:06 2019 TCP connection established with [AF_INET]172.111.177.2:80
Fri Jan 11 19:21:06 2019 TCP_CLIENT link local: (not bound)
Fri Jan 11 19:21:06 2019 TCP_CLIENT link remote: [AF_INET]172.111.177.2:80
Fri Jan 11 19:21:06 2019 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Fri Jan 11 19:21:08 2019 [Secure-Server] Peer Connection Initiated with [AF_INET]172.111.177.2:80
Fri Jan 11 19:21:10 2019 TUN/TAP device tun0 opened
Fri Jan 11 19:21:10 2019 do_ifconfig, tt->did_ifconfig_ipv6_setup=0
Fri Jan 11 19:21:10 2019 /sbin/ip link set dev tun0 up mtu 1500
Fri Jan 11 19:21:10 2019 /sbin/ip addr add dev tun0 172.111.177.107/27 broadcast 172.111.177.127
Fri Jan 11 19:21:10 2019 /etc/openvpn/tunnelUp.sh tun0 1500 1560 172.111.177.107 255.255.255.224 init
Up script executed with tun0 1500 1560 172.111.177.107 255.255.255.224 init
Updating TRANSMISSION_BIND_ADDRESS_IPV4 to the ip of tun0 : 172.111.177.107
Using Transmission Web Control UI, overriding TRANSMISSION_WEB_HOME
Generating transmission settings.json from env variables
sed'ing True to true
Enforcing ownership on transmission config directories
Applying permissions to transmission config directories
Setting owner for transmission paths to 1000:100
Setting permission for files (644) and directories (755)
-------------------------------------
Transmission will run as
-------------------------------------
User name: abc
User uid: 1000
User gid: 100
-------------------------------------
STARTING TRANSMISSION
NO PORT UPDATER FOR THIS PROVIDER
Transmission startup script complete.
STARTING TINYPROXY
Setting tinyproxy port to 8888
Starting tinyproxy: tinyproxy.
Tinyproxy startup script complete.
RTNETLINK answers: File exists
Fri Jan 11 19:21:12 2019 ERROR: Linux route add command failed: external program exited with error status: 2
Fri Jan 11 19:21:12 2019 Initialization Sequence Completed
Edit #2:
I can ping www.google.ca within the docker container, however when I am in transmission, I cannot confirm a test on the port. I have the port forwarded on my router so that shouldn't be an issue... I did also confirm that the Public IP I have for the docker container is not my ISP provided Public IP so I am connecting through the VPN, but the communication with Transmission through the VPN seems wrong...
The text was updated successfully, but these errors were encountered:
Here is the pastebin of my error;
https://pastebin.com/kxsUYqqS
and the raw log:
I have followed the instructions (proper username and password for IVACY), using the latest build with updated IVACY certs, I cannot figure out why I am receiving error status 2.
Anyone have a similar issue?
EDIT: full log:
Edit #2:
I can ping www.google.ca within the docker container, however when I am in transmission, I cannot confirm a test on the port. I have the port forwarded on my router so that shouldn't be an issue... I did also confirm that the Public IP I have for the docker container is not my ISP provided Public IP so I am connecting through the VPN, but the communication with Transmission through the VPN seems wrong...
The text was updated successfully, but these errors were encountered: