Troubleshooting

Work down this list — it is roughly in order of likelihood:

• Give it five seconds. The scanner runs on a 5-second cycle, and a server that is still booting is not listening yet.
• Check the Network tool. If the port is there but the row is not, the process was filtered rather than missed — privileged ports and OS services never reach the Servers list.
• Check the port number. Anything below 1024 is treated as the operating system's business.
• Check for elevation. A server started from an administrator terminal is visible but marked, and it behaves differently — see below.

Still nothing? Tell us the runtime and the port — what to include. Detection gaps are bugs, and they get fixed.

The server was not started from inside a git repository, so there is no ref to read. A short hash rather than a name means a detached HEAD. More on how branches are read.

That process was started elevated, and Pip runs unelevated by design. Stop it from the terminal that started it, or from an administrator Task Manager. Why Pip does not ask for administrator rights.

SmartScreen does that for installers it has not seen signed by a known publisher. Choose More info, then Run anyway — and if you would rather verify than trust, check the SHA-256 fingerprint first.

• Check the key. Paste it rather than retyping; a trailing space from an email client is the usual culprit.
• Check the seat. One licence covers one machine at a time. If it is still activated somewhere else, free the seat first.
• Check the connection. Activation is the one call Pip makes; a corporate proxy blocking it will fail exactly here and nowhere else.

Lost the key entirely? Have it re-sent.

Windows hides tray icons it considers inactive. Click the chevron next to the clock to open the overflow area, then drag the bird back onto the tray so it stays put.