What to expect from NordVPN 6.0 for Linux
Over time, the NordVPN Linux app CLI gained different commands that could be used for similar or overlapping purposes. For example, connection technology and protocol had separate settings even though both controlled how the VPN connection was established. NordVPN 6.0 simplifies these controls and provides one clear way to configure each setting, while also streamlining how you use obfuscated servers, P2P connections, auto-connect, and other CLI features. Let’s take a closer look at the key changes coming with NordVPN 6.0 for Linux and what they mean for you.
A simpler way to choose your VPN protocol
Previously, the Linux CLI used separate “technology” and “protocol” settings. This meant, for example, that you could select OpenVPN as the technology and then use another command to choose TCP or UDP.
In NordVPN 6.0, these choices are handled through “nordvpn set protocol.” Instead of configuring technology and protocol separately, you choose the VPN protocol and its available variant through one setting.
The separate “nordvpn set technology” command is therefore being removed.
This change avoids conflicting combinations and gives you one place to choose how NordVPN establishes your VPN connection.
NordWhisper now handles obfuscation
NordVPN 6.0 also changes how obfuscation works on Linux. Previously, CLI users could turn obfuscation on or off separately using:
With version 6.0, the separate obfuscation toggle is removed. Instead, NordWhisper provides obfuscation through the “Obfuscated servers” group.
NordWhisper is a VPN protocol designed to work on restrictive local networks where standard VPN connections may be difficult to establish, such as networks that use VPN filtering.
This change means you no longer need to enable obfuscation separately before using it. Instead, you need to change your protocol to NordWhisper, and then you can select the “Obfuscated servers” group for connecting.
P2P no longer needs its own server group
NordVPN 6.0 also removes the separate P2P server group and related P2P connection commands.
This change does not mean P2P traffic is being removed or restricted. P2P traffic works on regular VPN connections, so you no longer need to choose a dedicated P2P group before connecting. Instead of using commands such as “nordvpn connect P2P,” you just connect to a standard location.
The same applies to auto-connect configurations that specifically target the P2P group. In NordVPN 6.0, you can set auto-connect to a country or city or use the standard auto-connect option.
Virtual server selection is now handled automatically
The “nordvpn set virtual-location” setting is also being removed. You don’t need to replace it with another command. Virtual servers are no longer separated from other servers, so this behavior is handled by default.
One name for “allowlist” commands
NordVPN 6.0 removes the “whitelist” alias, leaving “nordvpn allowlist” as the command for managing traffic that you want to exclude from the VPN connection. The functionality itself isn’t going away. The change simply gives the feature one consistent name.
On Linux, the allowlist lets you exclude selected ports, port ranges, or subnets from the VPN connection. If a script still uses the “whitelist” alias, replace it with the corresponding allowlist command before upgrading.
Protection commands are getting a simpler name
NordVPN 6.0 also updates the command used to manage real-time protection. If your scripts or automations currently use “nordvpn set threatprotectionlite,” you’ll need to replace it with:
The “tplite” and “cybersec” aliases are also being removed. The functionality remains available — only the CLI command used to manage it is changing.
NordVPN 6.0 CLI command changes
If you use the Linux CLI directly — particularly in scripts, “cron” jobs, “systemd” units, containers, or other automations — check your configuration for these commands before upgrading.
| Previous command or option | What to use in NordVPN 6.0 | Why it’s changing |
|---|---|---|
nordvpn set technology | nordvpn set protocol | Protocol and technology choices are combined into one setting. |
nordvpn set obfuscate | NordWhisper through the “Obfuscated servers” group | Obfuscation no longer requires a separate toggle. |
nordvpn set virtual-location | No replacement needed | Virtual servers are no longer separated from other servers. |
nordvpn groups P2P / nordvpn connect P2P | Connect to any standard location | Standard servers support P2P traffic. |
P2P-specific commands for: nordvpn set autoconnect | Auto-connect to a country or city, or use standard auto-connect | A dedicated P2P group is no longer needed. |
nordvpn set autoconnect <specific-server-by-id> | Auto-connect to a country or city | Auto-connect to individual named servers is no longer supported. |
nordvpn whitelist | nordvpn allowlist | The feature now uses one consistent name. |
nordvpn set threatprotectionlite / nordvpn set tplite / nordvpn set cybersec | nordvpn set protection enabled | Protection settings now use consistent naming. |
Do you use NordVPN in scripts? Update them before upgrading
The CLI updates in NordVPN 6.0 are breaking changes. If a script calls a command that has been removed, that command will return an error after you update.
This error is particularly important if you use NordVPN with:
- Shell scripts or other custom scripts.
- “cron” jobs.
- “systemd” services.
- Ansible or other configuration management tools.
- Docker or other containerized setups.
- Headless Linux servers.
Search your configurations for the commands listed in the migration table and replace them with their NordVPN 6.0 equivalents where necessary.
Pay particular attention to auto-connect configurations. Auto-connect to an individual named server is no longer supported in NordVPN 6.0. If your setup pins a particular server hostname, change it to a supported country or city before updating. For example, rather than automatically connecting to an individual server, you can configure NordVPN to connect to your chosen country or city.
Back up your settings before moving to NordVPN 6.0
We also recommend saving your current NordVPN configuration before installing version 6.0.
Run the following command and save the output somewhere outside the NordVPN app:
NordVPN 6.0 introduces changes to how its settings are stored, and settings from version 6.0 are not backward compatible with earlier versions. The migration of settings from the previous version to 6.0 works automatically. However, if you have some custom configurations, check them with “nordvpn settings” before upgrading, so in case of a downgrade to 5.x.x version, you can manually enter them again.
Fewer commands, simpler configuration
NordVPN 6.0 for Linux cleans up CLI controls that had begun to overlap as more connection options and features were added to the app.
Instead of configuring protocol and technology separately, you make one protocol choice. Instead of turning on obfuscation with a separate switch, you use NordWhisper through Obfuscated Servers. And instead of choosing a dedicated P2P group, you can use standard server locations.
If you primarily use the NordVPN Linux GUI or system tray, most of the CLI changes won’t affect how you use the app. You’ll still see the changes to how obfuscation and server options are presented, but you won’t need to update any CLI commands unless you also use them separately.
If you use the CLI, scripts, or automations, check your setup before upgrading. Save your current settings, replace any commands that are being removed, and make sure your automations use the new syntax.
Overall, NordVPN 6.0 for Linux gives you fewer overlapping controls and one clear way to configure each setting.
Online security starts with a click.
Stay safe with the world’s leading VPN
