Let’s get you connected.

ntwire-gui is currently unsigned. Download it only from the official ntwire release, then control-click the app, choose Open, and confirm. This is the expected first-run path for the current release. The GUI app is for Apple-silicon Macs.

Download only from the official ntwire release. Select “More info”, verify the app is ntwire-gui from that release, then choose “Run anyway” if your organisation has approved it.

Some Linux desktop environments do not show StatusNotifier tray items by default. On GNOME, install and enable a compatible tray extension, then restart ntwire-gui.

Your administrator must provide it. It is usually an HTTPS address. ntwire cannot discover a private server on its own.

Confirm the server address and the sign-in method. For SSH, ask the administrator whether they received and approved your public key. For SSO, confirm you signed in with the account your organisation granted.

Ask your server administrator to verify the fingerprint before accepting it. A changed fingerprint for a server you used before should be investigated; it can be caused by a server rebuild, but you should not accept it blindly.

Enter the passphrase that protects the private key. It is not your SSO password. If you do not know it, create or obtain a new approved SSH identity from your administrator.

Open the dashboard and verify the tunnel appears there. Use the local address and port shown by ntwire, not the internal service address. If the tunnel is absent, the server administrator may need to grant it to your identity.

Stay connected if possible; ntwire can use a secure fallback when a network blocks UDP. If it continues to fail, try another network and share the displayed connection error and approximate time with your administrator.

Keep ntwire-gui running and use the “Open dashboard” action from the connected profile. The dashboard link is local to your device and cannot be opened from another computer.