ProtonVPN / protonvpn-cli

Legacy protonvpn-cli: ProtonVPN Command-Line Tool for Linux and macOS. This has been superseded by https://github.com/ProtonVPN/protonvpn-cli-ng
Other
603 stars 95 forks source link

Cannot open TUN/TAP dev /dev/net/tun #99

Closed Bloopps closed 6 years ago

Bloopps commented 6 years ago

Hi

I have this error ERROR: Cannot open TUN/TAP dev /dev/net/tun: No such file or directory (errno=2 when I run the command./protonvpn-cli.sh -f but only on a Debian container in Proxmox Virtual Environment. I do the same thing in a Debian 9 environment without Proxmox virtual environment and everything works fine.

the log file PROTONVPN_CLI_LOG=true ./protonvpn-cli.sh -f : Log_Protoncli.txt

Thanks for your help

xilopaint commented 6 years ago

Are you running these commands in a root shell? I don't see the sudo command.

Also, as you have been told before, you should not run ./protonvpn-cli.sh, use protonvpn-cli or pvpn instead. But not before running the --update flag to ensure you have the latest version of protonvpn-cli.

mazen160 commented 6 years ago

Hi @Bloopps This is probably either a kernel related issue, or permission related.

Can you do the following:

$ sudo su
$ id
$ pvpn -update
$ pvpn -f

and if it's still not working, can you share the output?

Bloopps commented 6 years ago

@xilopaint Foul typing when I asked my question, i use these command in a root shell, sorry. Yes i have runnning the --update.

@mazen160

$ root@CT101:~# sudo su
$ root@CT101:~# id
$ uid=0(root) gid=0(root) groups=0(root)
$ root@CT101:~# pvpn -update
$ [#] Checking for update.
$ [*] protonvpn-cli is up-to-date!
$ root@CT101:~# pvpn -f
$ Fetching ProtonVPN Servers...
$ Connecting...
$ [!] Error connecting to VPN.
mazen160 commented 6 years ago

Can you try to connect with manual openvpn config? The bug is definitely appearing in an odd configuration on you machine's end.

Bloopps commented 6 years ago

Hi @mazen160 Sorry I didn't answer before Here is a test in manual connect with openvpn config =>openvpncli.log

mazen160 commented 6 years ago

Hi @Bloopps I have checked the issues with the team. It appears to be an issue in your setup (from your end).

It's a container issue where no dev/tun device is created.

Please refer to the following references to get an idea about the issue:

Best regards, Mazin

Bloopps commented 6 years ago

Hi, I finally solved my problem with this:

Protonvpn-cli works perfectly now Thanks @mazen160 for your help !

mazen160 commented 6 years ago

Hi @Bloopps Great!! Totally glad to help!:)