Replies: 1 comment
-
Unfortunately, I rushed with the idea. I haven't been able to make this configuration work reliably yet. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello, recently I encountered a problem, actually a couple of them.
In my country (Russia), PIA is blocked:
The solution is to use a connection through socks5 (provided by PIA or external).
Here's how to use a socks5 proxy for OpenVPN.
For the connection, you'll need (an example for PIA proxy):
You can find it at the bottom of the page: https://www.privateint…ontrol-panel#downloads
Section: VPN settings --> SOCKS
Make sure to get the IP address specifically.
The user's login and password need to be placed in a file, which should then be mounted into the container. The file format should be text, with the user's login on the first line and their password on the second line. More information can be found in the documentation: https://openvpn.net/community-resources/reference-manual-for-openvpn-2-4/
The server IP, port, and authentication file need to be passed as launch arguments for OpenVPN.
-v /volume1/docker/pia/socks-auth.txt:/etc/socks-auth.txt \ -e "OPENVPN_OPTS=--inactive 3600 --ping 10 --ping-exit 60 --socks-proxy **** 1080 /etc/socks-auth.txt" \
I suggest adding a note about using socks5 to the documentation.
Beta Was this translation helpful? Give feedback.
All reactions