Hi,
I tried installing it in a toolbox, then later tried layering it with rpm-ostree install.
I always got this message after typing ‘nordlayer login’ and entering my organization:
Failed to get login info: connection error: desc = "transport: Error while dialing: dial unix /run/nordlayer/nordlayer.sock: connect: no such file or directory"
They don’t have a flatpak. Assuming it’s just not going to work and it’s designed for traditional non atomic linux?
Thanks
I assume you’ve used the .rpm package provided on the download page. Does it work on a non-atomic Fedora desktop (e.g. Fedora Workstation 42, maybe tested in a VM)?
I’ve seen some issues with RPMs provided by similar app’s developers trying to use read-only file locations, specific to atomic desktops, but the errors were usually seen at install time.
Hi - yes that’s correct. I got the .rpm for x86_64 from the site you linked. It did work with Fedora Workstation, but I recently switched to Silverblue. Thx
Nord products are no good on atomic fedoras. And won’t be supported anymore. This is why I moved to proton. Really old version on Nord products still can be installed, but never gets updates anymore
That’s what I figured, like it expects to write to some directory that’s immutable or something. Thanks
Like nordVPN 18.5 is latest to be working on fedora atomic ones after that they cleaned code and removed stuff and after that no more atomic ones… so basically they made there products not to be used on atomic ones since older ones was still working as should.
I talked long to support and finally got answer and it was not what I wanted. Answer was atomic ones was never officially supported platforms and we not gonna support it in future too
Not sure if Nord allows you to create manual Wireguard .conf files? I’m using Surfshark, create manual Wireguard VPN, export the file, then just import the .conf using Settings > Network > VPN > Add
Very clean & light, very reliable on the Feodra Atomics, KDE & Gnome I’ve used.
The con of this would be you will lose any extra functionaility provided by the client, but if basic VPN fits your needs, a good resolve.
To then configure the newly added VPN to autostart, these commands
nmcli connection show
nmcli connection modify YOUR_VPN_NAME autoconnect yes
You can also try the community sysext: nordvpn-gui | extensions.fcos.fr (Community)