search

haugene / vpn-configs-contrib

A collection of configs for various VPN providers
GNU General Public License v3.0
188 stars 753 forks source link

Update for TrustZone .ovpn files #9

Closed bamojr closed 3 years ago

bamojr commented 3 years ago

Before creating this request I have:

REQUIRED

Which provider?

REQUIRED

TrustZone

Where are the configs?

REQUIRED

https://trust.zone/downloads/ovpn.zip

Additional context

Optional

Per the update on their website: https://trust.zone/post/big-security-update-trustzone-vpn image

pkishino commented 3 years ago

Not sure why the bot closed the original issue, but did you test the new files as custom and they work now? No more problem?

bamojr commented 3 years ago

@pkishino yup, I was able to use the new TZ ovpn file for the New York server and was able to get it working, so I think the new ovpn.zip should be good to be applied to the whole project!

Fagerinfoco commented 3 years ago

I am having a serious problem with this. I also use Trust.Zone. I pulled the configuration today, so this is not an issue of the old versions of the .ovpn files. I am initiating through docker-compose, but i am obviously missing something. When i launch i get this error:

Using OpenVPN provider: TRUSTZONE 2 servers found in OPENVPN_CONFIG, Trust.Zone-United-States-Colorado chosen randomly Supplied config Trust.Zone-United-States-Colorado.ovpn could not be found.

I broke it down and am starting this stack separate from my normal docker-compose file by running it through the editor in portainer.

version: "3.6" services: transmission-vpn: container_name: transmission-vpn image: haugene/transmission-openvpn cap_add:

I would really appreciate any help with this

bamojr commented 3 years ago

@Fagerinfoco, I don't think the OVPN files have yet been updated for Trust.Zone in the project yet. Using the OPENVPN_PROVIDER=TRUSTZONE won't work if that is the case. Trying looking at the documentation here to get a single custom ovpn file working: https://haugene.github.io/docker-transmission-openvpn/supported-providers/#using_a_local_set_of_ovpn_files_from_provider

pkishino commented 3 years ago

@Fagerinfoco First of all, the new files are not added to the report yet, there is no pull request made for them, so you need to use custom provider.. Second, your mounts look strange.. Why you mounting localtime? That’s hasn’t been needed in quite a while. TZ fixed this. Second, you are mounting /config to a local volume point, why? Follow the link above to use custom, rest looks ok

Fagerinfoco commented 3 years ago

First, thank you both for the quick response. the mount points look odd because i'm following a guide that might be a little out of date. I changed the volumes and followed the directions given: volumes:

pkishino commented 3 years ago

can you share the log when you use custom and also a ls of the /etc/openvpn/custom/ folder please?

On Sat, May 29, 2021 at 8:57 PM Fagerinfoco @.***> wrote:

First, thank you both for the quick response. the mount points look odd because i'm following a guide that might be a little out of date. I changed the volumes and followed the directions given: volumes:

  • ${USERDIR}/docker/transmission/trustzone/:/etc/openvpn/custom/
  • ${USERDIR}/docker/transmission-vpn:/data The ovpn and .cer files are in {$USERDIR}/docker/transmission/trustzone. removes the localtime mount. environment:
  • OPENVPN_PROVIDER=custom
  • OPENVPN_USERNAME=****
  • OPENVPN_PASSWORD=****
  • OPENVPN_CONFIG=Trust.Zone-United-States-MID the ovpn is named exactly the same as the OPENVPN_CONFIG. The CA is built into the ovpn file and the auth-user-pass has been adjusted to read "auth-user-pass /etc/openvpn/custom/openvpn-credentials.txt". That folder exists in both the host OS as well as the mount point in the container. Still getting "Supplied config Trust.Zone-United-States-MID.ovpn could not be found."

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/haugene/vpn-configs-contrib/issues/9#issuecomment-850820843, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA7OFYV6BXNK4SFD6DEIGWDTQDJDVANCNFSM434P2CIA .

Fagerinfoco commented 3 years ago

logs: Starting container with revision: fccd0ca9062110d77ab08ac385962207d84319c3 Creating TUN device /dev/net/tun mknod: /dev/net/tun: File exists Using OpenVPN provider: CUSTOM Supplied config Trust.Zone-United-States-MID.ovpn could not be found. Your options for this provider are: NB: Remember to not specify .ovpn as part of the config name.

Starting container with revision: fccd0ca9062110d77ab08ac385962207d84319c3 Creating TUN device /dev/net/tun mknod: /dev/net/tun: File exists Using OpenVPN provider: CUSTOM Supplied config Trust.Zone-United-States-MID.ovpn could not be found. Your options for this provider are: NB: Remember to not specify .ovpn as part of the config name.

(then it just repeats)

ls of /etc/openvpn/custom: drwxr-xr-x 2 root root 4096 May 28 19:23 . drwxr-xr-x 5 root root 4096 May 28 19:06 .. -rw-r--r-- 1 root root 9 May 28 19:08 openvpn-credentials.txt -rw-rw-r-- 1 {myuser} {myuser} 3156 May 28 19:12 Trust.Zone-United-States-Colorado_ca.cer -rw-rw-r-- 1 {myuser} {myuser} 7849 May 28 19:23 Trust.Zone-United-States-Colorado.ovpn -rw-rw-r-- 1 {myuser} {myuser} 3156 May 28 19:12 Trust.Zone-United-States-MID_ca.cer -rw-rw-r-- 1 {myuser} {myuser} 7850 May 28 19:23 Trust.Zone-United-States-MID.ovpn

had a thought...should those files be chownd to root?

pkishino commented 3 years ago

As they have read it should be fine.. but worth a try.. I’m wondering if the naming could be an issue.. could you try renaming it to default.ovpn instead? Then you can also drop the ovpn config line..

On Sat, May 29, 2021 at 21:34 Fagerinfoco @.***> wrote:

logs: Starting container with revision: fccd0ca9062110d77ab08ac385962207d84319c3 Creating TUN device /dev/net/tun mknod: /dev/net/tun: File exists Using OpenVPN provider: CUSTOM Supplied config Trust.Zone-United-States-MID.ovpn could not be found. Your options for this provider are: NB: Remember to not specify .ovpn as part of the config name.

Starting container with revision: fccd0ca9062110d77ab08ac385962207d84319c3 Creating TUN device /dev/net/tun mknod: /dev/net/tun: File exists Using OpenVPN provider: CUSTOM Supplied config Trust.Zone-United-States-MID.ovpn could not be found. Your options for this provider are: NB: Remember to not specify .ovpn as part of the config name.

(then it just repeats)

ls of /etc/openvpn/custom: drwxr-xr-x 2 root root 4096 May 28 19:23 . drwxr-xr-x 5 root root 4096 May 28 19:06 .. -rw-r--r-- 1 root root 9 May 28 19:08 openvpn-credentials.txt -rw-rw-r-- 1 {myuser} {myuser} 3156 May 28 19:12 Trust.Zone-United-States-Colorado_ca.cer -rw-rw-r-- 1 {myuser} {myuser} 7849 May 28 19:23 Trust.Zone-United-States-Colorado.ovpn -rw-rw-r-- 1 {myuser} {myuser} 3156 May 28 19:12 Trust.Zone-United-States-MID_ca.cer -rw-rw-r-- 1 {myuser} {myuser} 7850 May 28 19:23 Trust.Zone-United-States-MID.ovpn

had a thought...should those files be chownd to root?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/haugene/vpn-configs-contrib/issues/9#issuecomment-850825594, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA7OFYS2R4MXPGT5ADXWW5DTQDNLZANCNFSM434P2CIA .

Fagerinfoco commented 3 years ago

getting somewhere i think. New error from logs:

Starting container with revision: fccd0ca9062110d77ab08ac385962207d84319c3 Creating TUN device /dev/net/tun mknod: /dev/net/tun: File exists Using OpenVPN provider: CUSTOM No VPN configuration provided. Using default. Setting OpenVPN credentials... adding route to local network 192.168.1.0/24 via 172.23.0.1 dev eth0 Options error: In [CMD-LINE]:1: Error opening configuration file: /etc/openvpn/custom/default.ovpn Use --help for more information.

commented out the OPENVPN_CONFIG line. in both /etc/openvpn/custom (host OS) and {$USERDIR}/docker/transmission/trustzone (mount point in container) there is a default.ovpn (rw-rw-r--)

pkishino commented 3 years ago

Hmm, error opening.. then I would try to change owner to root first.. otherwise, file corrupted?

On Sat, May 29, 2021 at 22:09 Fagerinfoco @.***> wrote:

getting somewhere i think. New error from logs:

Starting container with revision: fccd0ca9062110d77ab08ac385962207d84319c3 Creating TUN device /dev/net/tun mknod: /dev/net/tun: File exists Using OpenVPN provider: CUSTOM No VPN configuration provided. Using default. Setting OpenVPN credentials... adding route to local network 192.168.1.0/24 via 172.23.0.1 dev eth0 Options error: In [CMD-LINE]:1: Error opening configuration file: /etc/openvpn/custom/default.ovpn Use --help for more information.

commented out the OPENVPN_CONFIG line. in both /etc/openvpn/custom (host OS) and {$USERDIR}/docker/transmission/trustzone (mount point in container) there is a default.ovpn (rw-rw-r--)

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/haugene/vpn-configs-contrib/issues/9#issuecomment-850831123, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA7OFYVMT526BOFUSYORWA3TQDRQRANCNFSM434P2CIA .

Fagerinfoco commented 3 years ago

i tried something else. i uncommented the OPENVPN_CONFIG line, but left it as a custom setup. I'm getting a different error:

Starting container with revision: fccd0ca9062110d77ab08ac385962207d84319c3 Creating TUN device /dev/net/tun mknod: /dev/net/tun: File exists Using OpenVPN provider: CUSTOM Supplied config Trust.Zone-United-States-MID.ovpn could not be found. Your options for this provider are: NB: Remember to not specify .ovpn as part of the config name.

indicates to me it's looking in a specific place for this file, but i don't have the file in the right location. Where should the .ovpn file be located (either in the host os or in the container volumes) for this to work?

pkishino commented 3 years ago

You did check the wiki entry right? Then it should work..

On Sun, May 30, 2021 at 20:43 Fagerinfoco @.***> wrote:

i tried something else. i uncommented the OPENVPN_CONFIG line, but left it as a custom setup. I'm getting a different error:

Starting container with revision: fccd0ca9062110d77ab08ac385962207d84319c3 Creating TUN device /dev/net/tun mknod: /dev/net/tun: File exists Using OpenVPN provider: CUSTOM Supplied config Trust.Zone-United-States-MID.ovpn could not be found. Your options for this provider are: NB: Remember to not specify .ovpn as part of the config name.

indicates to me it's looking in a specific place for this file, but i don't have the file in the right location. Where should the .ovpn file be located (either in the host os or in the container volumes) for this to work?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/haugene/vpn-configs-contrib/issues/9#issuecomment-850986165, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA7OFYU3R6QBLFMYHC3JNOTTQIQFTANCNFSM434P2CIA .

Fagerinfoco commented 3 years ago

yes. i replaced

pkishino commented 3 years ago

please check now that #17 has been merged