Help
Troubleshooting Vigilance
Updated 7 Nov 2026
Find the problem you see, then take the one step next to it. Most steps are a short message to the user of the computer. Your Portal has a button that copies that message for you.
A computer does not show in the Portal
Check the link
Each user must open your company's join link on their own computer. A link from an old email can be one you replaced with Make a new join link.
Install again
Ask the user to open the join link again and run the installer. At the end, a window says Vigilance is on.
Write to us
Still not there? Write to support@vigihq.com.
Vigilance runs on a Mac, Windows, Linux and a Chromebook. It does not install on a phone or a tablet.
Problems the Portal names for you
No report for 3 workdays
"Vigilance got no report from Ana's MacBook Air after Nov 3." Saturday and Sunday do not count. A computer that is off cannot download, so ask Ana to turn on the computer and connect it to the internet. On holiday or leave? Press Ana is away and set the date.
Vigilance turned off
"Vigilance was turned off on Ben's Windows laptop today at 10:14." You hear about it the same day. Ask Ben to restart the computer. If Vigilance does not start, ask Ben to install it again with your join link.
An old version
"Raj's ThinkPad runs an old Vigilance version." Ask Raj to restart the computer. Vigilance updates when it starts.
A question waits
"Vigilance asked Mei a question on Mei's iMac, and it waits for an answer." Ask Mei to answer the Vigilance window.
Each of these has a Copy a message button in your Portal. Every step is in what each status means.
Installs fail for a short time
If the Vigilance program stops, installs can fail for about 2 minutes. Then a small helper puts the old package settings back, and installs go ahead with no check. We email you the same day.
If our service does not answer, Vigilance uses its saved list for up to 7 days. After that, installs go ahead unchecked.
On Linux
If the terminal says "curl: not found", install curl with your package manager, then paste the command again. Installs you run with sudo are not checked. Run npm and pip as yourself.
Chromebook and Linux in WSL
Chromebook
Vigilance runs in Linux on the Chromebook. Turn on Linux in Settings, About ChromeOS, Developers. Then paste the command from the join page in the Terminal app, under penguin. It runs while Linux runs, on a 64-bit Intel, AMD or Arm chip.
Linux in WSL
The Windows installer offers to add Vigilance to each Linux in WSL. Linux in WSL counts as part of its Windows computer, so your bill does not change. In the Portal it shows under its Windows computer.
The full steps for each system are in install Vigilance on your computer.
The Portal does not load
If the Portal says it did not load, wait a minute and press Try again. A sign-in link works once and stops working in 15 minutes, so ask for a new one if it is old. If it keeps happening, write to support@vigihq.com.
FAQ
Why does a computer not show in my Vigilance Portal?
The install did not finish, or it used another join link. Ask the user to open your join link again on that computer and run the installer. If it still does not show, write to support@vigihq.com.
Why does the Portal say it got no report from a computer?
The computer sent no report for 3 workdays. Saturday and Sunday do not count. A computer that is off or has no internet sends no report. Ask the user to turn it on and connect it, or mark it as away until a date.
Does Vigilance work on a Chromebook?
Yes, in Linux on the Chromebook. Turn on Linux in Settings, then paste the command from the join page in the Terminal app. Vigilance checks what you install in Linux and runs while Linux runs.
Still stuck?
Reply to any Vigilance email, or write to support@vigihq.com.