testdasi / openvpn-client-aio Goto Github PK

Hello,
how I can set more than one HOST_NETWORK.
Example, like this..
HOST_NETWORK=192.168.0.0/16,10.10.0.0/24

Hello, see attached log. I used the configuration you provided with only 1 change: HOST_NETWORK - my router is on 192.168.0.1. My RPI4 is at 192.168.0.155 so I configured SwitchyOmega Proxy for Chrome to use 192.168.0.155:8118 but I can't hit the internet. It looks like the VPN is configured correctly because 94.140.11.62 is not my public IP address. How else I can troubleshoot this issue? There is only 1 error in the log but it seems to be related to TOR. I've tried all of the services but none work. I have other containers running on the PI (portainer as an example) and I can access that without issue. Your project looks like a fantastic AIO solution for my home network so I really wanted to get it to work but I'm stuck.

_openvpn_client_logs.txt

Hey!
I have been using you'r docker for a long time now, and i just love it!
The only thing i am missing, is the "iputils-ping" package, so i can combine it with Rebuild-DNDC docker.
Could you add this in an up-coming update?

Would be awesome!

Thanks.

This was a bit unclear, but is TOR completely tunnelled through VPN (thus hiding TOR usage)?

Having trouble with this container as it seems my.opendns.com is offline...?

I did try to use https://myip.dnsomatic.com/ in its place, but it seems something with how the apps setup works also kills this...

Hi, I have a vpn supporting port forwarding (purevpn) and I have a dockerized qbittorrent instance connecting to openvpn-aio thru socks5. The issue seems that I can get direct incoming connections only via UDP and nothing with TCP. I was using gluetunvpn docker before and after opening the firewall I got incoming connections fully working. With gluetunvpn not supporting socks5 I was connecting with --network=container:gluetunvpn docker option tho. I decided to switch to this because with socks5 updating the VPN container creates less hassles and be fully unattended. So are there some rules that could block incoming TCP connections from VPN to socks5 client? Thanks

Hi,

I use a VPN provider called Integrity (https://integrity.st) and can´t seem to get this working correctly on my Unraid server, see log below.

My ovpn config file:

The auth.txt file is a 2-liner file with user and pass

Hi, I'm trying to use the container on Unraid and I'm using the provider airvpn , just listing a piece of the configuration
"client
dev tun
remote 134.19.179.242 443"

When I look at the logs of docker, it's trying to connect on a port 2443 regardless of the port set in the openvpn.ovpn file.

[info] Setting up OpenVPN tunnel
[info] Create tunnel device
[info] Allow DnS-over-TLS for openvpn to lookup VPN server
[info] Connecting to VPN on port 2443 with proto udp...
[info] Connection in progress, wait 10s...
[info] Connection in progress, wait 10s...
[info] Connection in progress, wait 10s...
[info] Connection in progress, wait 10s...

Thanks for your promising container

Hi

I have multiple vlans on my network, if I set the HOST_NETWORK variable to 192.168.1.0/24 then only machines on that vlan can connect to the proxy, also if I set it to 192.168.5.0/24 then machines on that vlan can connect.

I know I could run two instances... that said is there a wild card entry? I've tried the obvious 192.168.*.0/24 and 192.168.0.0/24 but no dice. Even being able to disable incoming IP filtering would be ok?

Thanks!

Mark