Kill switch has been enabled. Please reconnect to VPN to activate it.
3.protonvpn-cli c
Setting up Proton VPN.
dbus[8490]: arguments to dbus_message_iter_append_basic() were incorrect, assertion "_dbus_check_is_valid_path (*string_p)" failed in file ../../../dbus/dbus-message.c line 2776.
This is normally a bug in some application using the D-Bus library.
D-Bus not built with -rdynamic so unable to print a backtrace
[1] 8490 IOT instruction (core dumped) protonvpn-cli c
4.protonvpn-cli --get-logs
Generating logs...
Unable to generate logs: can't compare offset-naive and offset-aware datetimes
Protonvpn linux client doesn't connect while kill switch is on
1.protonvpn-cli --version
Proton VPN CLI v3.13.0 (protonvpn-nm-lib v3.14.0; proton-client v0.7.1)
2.protonvpn-cli ks --on
Kill switch has been enabled. Please reconnect to VPN to activate it.
3.protonvpn-cli c
Setting up Proton VPN. dbus[8490]: arguments to dbus_message_iter_append_basic() were incorrect, assertion "_dbus_check_is_valid_path (*string_p)" failed in file ../../../dbus/dbus-message.c line 2776. This is normally a bug in some application using the D-Bus library.
D-Bus not built with -rdynamic so unable to print a backtrace [1] 8490 IOT instruction (core dumped) protonvpn-cli c
4.protonvpn-cli --get-logs
Generating logs...
Unable to generate logs: can't compare offset-naive and offset-aware datetimes