![]() If ExecutionEnvironment().killswitch != KillswitchStatusEnum.DISABLED:įile "/usr/lib/python3/dist-packages/protonvpn_nm_lib/core/environment.py", line 66, in killswitchįile "/usr/lib/python3/dist-packages/protonvpn_nm_lib/core/killswitch/killswitch.py", line 61, in _init_įile "/usr/lib/python3/dist-packages/protonvpn_nm_lib/core/killswitch/killswitch.py", line 597, in get_status_connectivity_check Utils.ensure_internet_connection_is_available()įile "/usr/lib/python3/dist-packages/protonvpn_nm_lib/core/utilities.py", line 22, in ensure_internet_connection_is_available service filesįile "/usr/lib/python3/dist-packages/dbus/bus.py", line 175, in activate_name_ownerįile "/usr/lib/python3/dist-packages/dbus/bus.py", line 361, in get_name_ownerįile "/usr/lib/python3/dist-packages/dbus/connection.py", line 651, in call_blockingĭ: .NameHasNoOwner: Could not get owner of name '': no such nameĭuring handling of the above exception, another exception occurred:įile "/usr/lib/python3/dist-packages/protonvpn_cli/cli_wrapper.py", line 73, in loginįile "/usr/lib/python3/dist-packages/protonvpn_nm_lib/api.py", line 30, in loginįile "/usr/lib/python3/dist-packages/protonvpn_nm_lib/core/utilities.py", line 16, in ensure_connectivity 18:34:42,862 - cli_wrapper.py - ERROR - login:117 - .ServiceUnknown: The name was not provided by any. 18:34:42,859 - cli_wrapper.py - INFO - login:68 - Credentials provided, attempting to login 18:34:40,253 - cli.py - INFO - _init_:64 - CLI command: Namespace(command='login', get_logs=False, help=False, version=False) I tried that, but still not working for me If you follow corretly, you should be able to connect. To troubleshoot the connection, you can monitor the systemd service that controls the vpn client with journalctl -u qubes-tunnel and view any errors that appear. If when you restart sys-vpn instead you receive continuous popup notifications stating ‘Ready to start link’, you may need to troubleshoot the connection. Regular usage is simple: Just use sys-vpn as NetVM for other VMs and start them! Troubleshooting This will autostart the VPN client and you should see a popup notification ‘LINK IS UP’! Following what’s the last sentence said, still as root or using sudo, in sys-vpn copy the OpenVPN config file from your service provider, for example called user_config.ovpn to /rw/config/qtunnel/ cp user_config.ovpn /rw/config/qtunnel/nf.Next, copy or link your config file to /rw/config/qtunnel/nf Login info saved to /rw/config/qtunnel/tunneluserpwd.txt As root or using sudo, in sys-vpn execute /usr/lib/qubes/qtunnel-setup -config /usr/lib/qubes/qtunnel-setup -config.Note: There is no need for adding network-manager service. In sys-vpn settings Services tab, add qubes-tunnel service.Make a choice for the NetVM setting, such as sys-firewall. Create an AppVM, called for example sys-vpn, with the provides network option enabled using a template with the previously installed qubes-tunnel package.Then, install qubes-tunnel in the same way. Install qubes-repo-contrib package using apt-get or dnf in template. Note : to use our NetShield DNS filtering feature, append the suffix +f1 to your username to block malware, or +f2 to block malware, ads, and trackers (for example 123456789+f2). So please configure the OpenVPN credentials to your preference as you will need to use them to establish a Linux VPN connection. OpenVPN / IKEv2 Username is used on manual connections. The credentials ProtonVPN Login are used in our applications. Here you will see your two type of credentials. Log in to the ProtonVPN dashboard and click on Account tab. Learn more about how two pairs of credentials increase the security of ProtonVPN. ServiceUnknown: The name is not activatableġ880×894 52.5 KB Find your OpenVPN credentials:įor increased security, ProtonVPN is set-up with two separate credentials to authenticate a connection. Sudo dnf install protonvpn-cli protonvpn ~]$ protonvpn-cli login openvpnidĮnter your ProtonVPN password: myopenvpnpwd ServiceUnknown: The name was not provided by any. Sudo apt-get install protonvpn-cli protonvpn-cli login openvpnid protonvpn-stable-release_1.0.1-1_all.deb -y The tuto is from here : How to use the official ProtonVPN Linux CLI But it’s working fine in a normal debian 10 OS and fedora 33 OS without QubesOS ![]() Before, proton vpn was maintained by the community and was working fine in a appVM in QubesOS.īut since last year, it’s possible tu use the officicial version of protonvpn, and I since then I never make it to work in a appVM in QubesOS for both debian 10 and fedora 33.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |