3proxy
docker-openvpn-client
Our great sponsors
3proxy | docker-openvpn-client | |
---|---|---|
2 | 6 | |
3,533 | 346 | |
2.2% | - | |
7.2 | 0.0 | |
about 1 month ago | about 1 month ago | |
C | Shell | |
GNU General Public License v3.0 or later | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
3proxy
-
Split Tunneling WireGuard in Windows using 3proxy
I have managed to get Split Tunneling working for WireGuard on windows using this method from this website. I didn't want to use the binding method that was mentioned on the website. Instead I used 3proxy to create a local socks5 on my machine and let other programs.
- Browse from server ip
docker-openvpn-client
-
Can someone explain the device and connection limits on mullvad?
I was planning to do that. I am using this image https://github.com/wfg/docker-openvpn-client
- Docker-openvpn-client, lets containers use VPN
-
Multiple Fortinet VPN connections suggestion?
What I want to know is which alternative client can be used to establish a connection to VPNs B and C? I've looked at OpenConnect but it seems that the download links for Windows builds are broken? What about others like SoftEther, OpenVPN or freelan? There's also the possibility of running a containerized Linux client inside Docker, as shown here? I do have WSL (running Debian, solely) and Docker Desktop installed on the machine so maybe? There are more options for native Linux clients (AFAIK) but I'm stuck with Windows 10 and that's not going to change anytime soon.
-
Prowlarr behind vpn and traefik in docker not accessible on local IP
Because all the traffic is routed into the vpn. You have to provide a route to your local network. I dont know if this is possible with your image. I use this one https://github.com/wfg/docker-openvpn-client there you can set your network via the SUBNETS environment variable.
-
Portainer/Transmission/VPN cant connect to web client
I'm assuming you followed the instructions at https://github.com/wfg/docker-openvpn-client/pkgs/container/openvpn-client to get the containers set up.
- Can't accessing services behind VPN service
What are some alternatives?
proxychains-ng - proxychains ng (new generation) - a preloader which hooks calls to sockets in dynamically linked programs and redirects it through one or more socks/http proxies. continuation of the unmaintained proxychains project. the sf.net page is currently not updated, use releases from github release page instead.
alpine-qbittorrent-openvpn - qBittorrent docker container with OpenVPN client running as unprivileged user on alpine linux
haproxy - HAProxy Load Balancer's development branch (mirror of git.haproxy.org)
multitor - Create multiple TOR instances with a load-balancing.
microsocks - tiny, portable SOCKS5 server with very moderate resource usage
gluetun - VPN client in a thin Docker container for multiple VPN providers, written in Go, and using OpenVPN or Wireguard, DNS over TLS, with a few proxy servers built-in.
go-socks - SOCKS4, SOCKS4a and SOCKS5 proxy server in Go
Qubes-vpn-support - VPN configuration in Qubes OS
Jool - SIIT and NAT64 for Linux
SoftEther - Cross-platform multi-protocol VPN software. Pull requests are welcome. The stable version is available at https://github.com/SoftEtherVPN/SoftEtherVPN_Stable.
mubeng - An incredibly fast proxy checker & IP rotator with ease.
containers