The scenarios and troubleshooting steps below should help resolve internal agent installation issues. Follow them carefully, and keep in mind that the internal system can take a few minutes to show up on your targets page.
If, by the end of this article, you're still having trouble, please get in touch with the team by sharing a screenshot of your most recent agent status output and the linking command you ran.
Is your linking command correct?
There are three attributes that you need to update in order for the target to link correctly and show up in your portal:
The prefix
The device name
The key.
If you omit any of these, your linking command won't work.
MacOS
sudo /Library/NessusAgent/run/sbin/nessuscli agent link --name=[Prefix_DeviceName] --cloud --key=[KEY]
Windows
msiexec /i "NessusAgent-[version]-x64.msi" NESSUS_SERVER="cloud.tenable.com:443" NESSUS_KEY=[KEY] NESSUS_NAME=[Prefix_DeviceName] /qn
Linux
sudo /opt/nessus_agent/sbin/nessuscli agent link --name=[Prefix_DeviceName] --key=[KEY] --cloud
⚠️ What next?
If your original linking command is missing any of these, you'll need to unlink and link again.
Did you run the linking command in the right directory?
It must be run in the directory where the agent was downloaded to.
⚠️ What next?
Re-run the command in the correct directory.
The installer downloads to the default folder on your machine. For example, on Windows:
C:\Users\[your username]\Downloads
If the installer was downloaded from a browser, hit the dropdown button and click 'Show in folder' (Windows) or 'Show in Finder'. (macOS) You'll then be able to copy the exact path.
If you need to move directory (e.g. if you moved the installer to your desktop), you can use the cd command to move into the appropriate directory before running the installer. For example:
cd C:\Users\[your username]\Desktopmsiexec /i "C:\Users\Intruder\Desktop\NessusAgent-[version]-x64.msi"
If you don't know the directory, on Windows, you can try the following:
Open Command Prompt (Administrator)
cd %userprofile%\Downloads
Did you use the same DeviceName as an existing target?
If you did, it won't be added to your account:
What next?
To remedy this, we'd recommend following the steps in this article.
Is your internal system connected to the internet?
The agent needs to be able to reach out to cloud.tenable.com on port 443 to return the results to the platform. To test this, open your browser and type:
Do you need to reboot your system?
Sounds simple – but sometimes turning your machine off and back on again can do the trick.
(Windows only)
Did you launch the agent installer correctly?
If you launched the installer after downloading it (step 1), rather than via the install command (step 3), you will need to unlink your agent and relink it again.
Unlink
In the terminal, as Admin, run the following command:
nessuscli agent unlink
Check that the unlink command worked
Run the agent status, it should return:
Linked to: None
Link status: Not linked to a manager
Link the agent (again)
Open the command terminal again – as Administrator
Run the link command below
(Make sure you are in the right folder and added your prefix & device name)nessuscli agent link --host="cloud.tenable.com" --port="443" --key=819652a91d674e8d5be08e21299f1a3c69bd9806c72e24bc05df6b32b8db7fe1 --name=[Prefix_DeviceName]
Check out the targets page to see if it has appeared.
Do you have anti-virus enabled?
If the answer is yes and you have an IT department, we'd recommend taking a screenshot of the process name in your task explorer (usually something like "nessusagent", "neagent" or similar) and sending it over to them; along with a note that says the agent needs to be able to reach out out to cloud.tenable.com on port 443.
None of these applicable?
Your best bet at this point would be to do the following:
Send our support team a message confirming that you have read this article and eliminated all of the above.
Include screenshots of your agent status command output and the exact linking command you ran (the very first time)