linux-cli VS protonvpn-nm-lib

Does it look like this issue? https://github.com/ProtonVPN/linux-cli/issues/43

All this to say, the Linux app, both CLI and GUI is broken, hasn’t been addressed (till very recently), does not have feature parity to the other apps and this isn’t opinion, it’s observable and validated fact from the community and Proton themselves: https://github.com/ProtonVPN/linux-cli/issues/64

Here I am, still waiting for a proper ProtonVPN client for Linux which supports all the features, and isn't buggy...

Basically, I assume Proton has already abandoned their Linux client (both gui and cli). Look at their github repositories (https://github.com/ProtonVPN/linux-app and https://github.com/ProtonVPN/linux-cli). Their last commit was half year ago, while windows, android, ios and mac client are still actively maintained.

I suspect there's something wrong with the network services/daemons but I'm not sure what. There an issue on github but nobody figured out the problem it seems: https://github.com/ProtonVPN/linux-cli/issues/61

Newer official Python CLI that should actually be used: https://github.com/ProtonVPN/linux-cli

The original file has a classifiers section that looks like this:

If you dig through ProtonVPN clients' source code (such as the linux client's code) you can see that for their apps, verify-x509-name is used (on other platforms it seems they use their own implementation of TLS name verification for servers), and each server has a unique name. It's likely that it's not used in their openvpn config files because of risk of breakage resulting in bad UX.