Supported versions · Ubuntu, Debian or Fedora for the packaged tool; for profiles, any distribution able to run WireGuard or OpenVPN.
Install and switch on
- 1Settle the VPN pass in your cart from your balance.
- 2From the Get the apps tab in My info, grab the .deb (Ubuntu, Debian) or the .rpm (Fedora).
- 3Install it through apt or dnf with sudo.
- 4Run the CoxVPN login command; use the email and password or account token you registered with.
- 5Print the server list and settle on a country or city.
- 6Bring the tunnel up with one command, then check with the status command that traffic leaves through CoxVPN.
CLI tool or a profile file?
People who hop between locations tend to prefer the CLI tool: a single command lands you in another city, and --help after any command prints its flags.
Profiles require nothing new on the system. wg-quick reads the WireGuard version; OpenVPN or NetworkManager reads the .ovpn. A profile is pinned to a single endpoint, so a different city calls for a different download.
Headless and always-on machines
A home server or any box nobody watches should run with the kill switch on. If the tunnel dies at night, packets wait rather than leaving over your real IP.
Using a profile? Leave its DNS line in place. That line points at our resolver; delete it and your ISP starts answering lookups again even with the tunnel up.
DNS stays the same, or WireGuard won't come up
On systems with systemd-resolved, lookups can keep going to the old resolver after connecting. Adding the resolvconf compatibility package, or importing the profile via NetworkManager, solves it most of the time.
When wg-quick reports a missing module, an outdated kernel is the likely culprit. Upgrade everything, reboot, and confirm wireguard-tools is installed.