-
Notifications
You must be signed in to change notification settings - Fork 195
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Mageia 7 KDE issue #51
Comments
That's because you didn't install as root. When you then use sudo, it won't be in root's $PATH because it's installed only for your user. If you don't want to install with sudo you can follow this guide to install it globally in a virtual environment.
The package that gets installed by python3-dialog should be installed by PIP, so not sure why this error exists for you when not using the package provided by the repositories.
Are you using the ProtonVPN OpenVPN credentials? You can find them on https://account.protonvpn.com/accounts. Note that you can't use your normal login credentials for ProtonVPN, but you need to use those special credentials for this tool. This is also described in the example installation. |
I have bash history and I have check the root commands in my history:
So I have installed protonvpn-cli as root, it is sure.
I don't know, python3-dialog was not installed, so I had to installed it manually.
Yes, sorry, I have not read the manual and have used the site credentials. Now I have not login error but API error:
So I have installed protonvpn with pip3 as root and have the error:
protonvpn in in my root $PATH. |
Can you access https://api.protonmail.ch/tests/ping in your browser? It could be that your access to this site is blocked for some reason. If not, you can run
What did you do different, it seemed to work in the previous example you posted? The CLI checks for the running user with Python's built-in getpass.getuser() function, so getting this error when executing as root means your environment variables aren't what they should be. Can you send me the output of the following command, executed as root:
|
Yes, I can.
log.txt
Is It a Mageia 7 bug? It returns the user in root mode and not superuser, only sudo works correctly. |
Thanks for the log file, I definitely need to improve logging a bit and noted this. The error seems to be that you can't connect to the ProtonVPN API after the connection was successfully initiated by OpenVPN itself, so you should be connected, but the CLI might break because there's still some information missing (especially in the config file). To be precise, this line seems to be the issue. I will look into improving this.
Might be. How exactly do you switch to the root user? Maybe I can reproduce this on another distro as well. |
Tanx for your efforts.
Mageia has not sudo implemented by default. So I ( and every mageia user) do:
Another little issue is that after:
I get:
and Internet is blocked via browser (maybe DNS (resolv.conf file) problem?) so I do
and all goes fine. Internet works. |
Tried this on Ubuntu and Fedora and I don't have this issue. Using
Might be. Can you try |
I have not enough knowledge to open a bug into mageia bugzilla, I have understand only that python have an issue into mageia environment. I can post only this.
nope.
|
To be honest, the easiest thing to do would probably to install sudo. It's recommended for security reasons anyway to disable the root account itself so you can't log in with it and only use sudo. But you have to decide for yourself.
Can you maybe try following this guide and see if it works if you just go through the normal setup with OpenVPN config files? I'm not sure if it's something with OpenVPN then that doesn't seem to work for you. |
The guida that I can follow is this: Option B: VPN setup for Linux using the Terminal (CLI) with this config file: ProtonVPN_server_configs.zip and this file: wget ? |
Yes. I just want to know if this will work for you. |
Hi, I also use Mageia 7 and I also experienced the same issue. I reproduced all the step described in this thread and get exactly the same output.
Then, I tried to connect to a website on Firefox but I was not able to reach it. |
It looks like Mageia has some weird anomalies/issues with OpenVPN itself. If the config files don't work the CLI can't either. So this does not seem to be a bug with the CLI. |
It is different to be conected as root using |
The process I follow was: Then I'm getting the very same error after
Into this machine I have squid, dhcpd, bind and shorewall, they works fine and share the internet network with my LAN desktops. Do you think the problem is that I can't share my VPN connection to a LAN. When I look into |
Yeah, OpenVPN isn't working on Mageia. This isn't really an issue with ProtonVPN. |
Interesting that OpenVPN for Mageia 7 works fine with config files from PrivateInternetAccess. |
@gramo44 What happens when you attempt to use https://api.protonmail.ch/vpn/location in a browser on the host on which protonvpn is running? Do you get JSON returned similar to but not the same as |
Hi... I find the solution!!!! I just enter to the firewall configuration and opened |
So the complete process I did in order to get connected was as follows:
At MCC go to firewall and open
|
@Rafficer ProtonVPN needs to clearly document that port 443 needs to be opened in the firewall for it to be able work. |
My test. I have previously installed all the software, so I used only So I confirm that the firewall must be open at port 443 and it is a lack of protonvpn manual. Bug closed? |
What exactly is Mageia doing? I've just tested on Linux Mint and blocked all incoming ports and it still worked perfectly. If Mageia is blocking 443/tcp outgoing then yeah, kinda obvious that it doesn't work. But also why would it do that? |
Mageia seems to have iptables policies in place that drop everything, even outgoing, that isn't from a known network interface. So honestly, this isn't ProtonVPN that needs to document that port 443 needs to be open, this is Mageia's default setting that doesn't allow any network interface to be introduced and connect to anything, which is what happens with OpenVPN. Anyway... Solution
I guess this issue can be closed with this guide now. I will also notify the ProtonVPN support team about this so they can help future users that run into this issue with Mageia. Thank you all. |
I have attempt to install protonvpn-cli to Mageia 7:
openvpn installed
python3-pip installed
python3-setuptools installed
I have not dialog, I have kdialog and Xdialog installed, It is not installed python3-dialog and python-dialog: I have installed they. Without this I have a dialog error into protonvpn.
# pip3 install protonvpn-cli
works fine.
# protonvpn init
don't works: [!] The program was not executed as root.
I add my username to sudoers (mageia has not sudo, only root) and then try:
$ sudo protonvpn init
don't works: unknown protonvpn command
$ sudo /usr/local/bin/protonvpn init
works!
$ sudo /usr/local/bin/protonvpn connect
don't work (dialog problem), I install python3-dialog and the dialog windows works.
I have try all configuration but I get always:
[!] Authentication failed. into $ sudo /usr/local/bin/protonvpn connect
Checked my login data with $ sudo /usr/local/bin/protonvpn configure and copy and paste my login data (username and password) without success.
Firewall problem?
The text was updated successfully, but these errors were encountered: