LogoLogo
  • NoPorts Documentation
  • Getting Started
  • Installation
    • Quick Start from macOS or Windows
    • Connecting from macOS
      • macOS to macOS
      • macOS to Linux
      • macOS to Windows
    • Connecting from Linux
      • Linux to macOS
      • Linux to Linux
      • Linux to Windows
    • Connecting from Windows
      • Windows to macOS
      • Windows to Linux
      • Windows to Windows
    • Cloud Installation Guides
      • Automated Installation on Amazon Web Services (AWS)
      • Automated Installation on Google Cloud Platform (GCP)
      • Automated Installation on Microsoft Azure
      • Automated Installation on Oracle Cloud Infrastructure (OCI)
    • OpenWrt Installation Guide
    • Manual Installation Guides
      • Device Installation
        • Tmux session
        • Standalone Binaries
        • Systemd Unit
        • Headless
      • Client Installation
    • Custom OS/Device Installs
      • IPFire
    • Installs at Scale
    • Upgrading NoPorts Software
      • NoPorts Client Upgrade
      • NoPorts Daemon Upgrade
    • Available Releases
  • Use Cases
    • SSH
    • SFTP
    • RDP
    • Web Server
    • SMB
    • Be your own VPN
  • Usage
    • npt Usage
    • sshnp Usage
      • Client Additional Configuration
    • sshnpd configuration
      • Daemon Additional Configuration
  • Integrations
    • OpenSSH Config
    • PuTTY config
  • Resources
    • How to activate an atSign
    • Reuse your client atSign on another machine
      • Generate a new set of cryptographic keys
    • How to name a device
    • How to generate SSH keys
    • Why activate the device atSign on the client?
  • Product Information
    • The NoPorts Philosophy
    • NoPorts Desktop Application
    • NoPorts Policy Service
    • Frequently Asked Questions
    • How It Works
    • Under The Hood
    • Sequence Diagram
  • Related Pages
    • Main Site
    • GitHub
Powered by GitBook
On this page
  • Upgrade sshnp
  • Verify the Upgrade
  • Troubleshooting the Upgrade
Edit on GitHub
Export as PDF
  1. Installation
  2. Upgrading NoPorts Software

NoPorts Client Upgrade

PreviousUpgrading NoPorts SoftwareNextNoPorts Daemon Upgrade

Last updated 13 days ago

Upgrade sshnp

Upgrading to the latest version of sshnp follows the same process as installation, as the installer automatically replaces existing binaries with the new ones.

To upgrade, follow the up to Step 3, then return to this page to verify the upgrade.

Verify the Upgrade

To check the current version of sshnp installed on your machine simply execute the binary:

sshnp

The first line of output should contain the version information:

Version : x.x.x
sshnp

The first line of output should contain the version information:

Version : x.x.x
sshnp.exe

The first line of output should contain the version information:

Version : x.x.x

Troubleshooting the Upgrade

If you continue to get an old version number, it's likely that there's an old binary which wasn't replaced on the machine. Try the following to debug your binary location:

First, use this command to locate the sshnp binary:

command -v sshnp

The command should output the location of the binary which is on the PATH. Try deleting this binary then rerunning the installer.

rm "$(command -v sshnp)"

First, use this command to locate the sshnp binary:

command -v sshnp

The command should output the location of the binary which is on the PATH. Try deleting this binary then rerunning the installer.

rm "$(command -v sshnp)"

Since Windows doesn't include a dedicated installer, upgrading should be as simple as moving the new binary to wherever you installed the previous one.

installation guide