Lots of people struggle with installing the agent – which is why we are working on improving the process, but until then, we hope you find this article helpful.

Outlined below are some steps that we believe – if followed carefully – should remediate the installation issue(s) you're facing. Please bear in mind, it can take a few minutes for the internal system to show on your targets page. If, by the end of this article, you're still having trouble, then please get in touch and we'll enlist the help of our security team. 💪


Do you have enough licenses?

The internal system won't show if you don't have enough licenses to cover scanning the device (and any other active targets listed). If you're unsure about your current license count, then please head to the targets page, and hover over the circle on the far right – clicking on that button will show you what targets are consuming licenses, and when they'll be up for release (and can be used on new targets – more on that, here).

If you're out of licenses, then you can update your license count by following the instructions in this article.

Trial users: Please note that the trial entitles you to three licenses, which can be used to scan three targets (internal or external) as many times as you like for 30 days. Deleting the target will not release the license. If you have already used all three and would like to test the internal scanner, please get in touch with a member of the team via the chatbot.


Do you need to reboot your system?

Sounds simple – but sometimes turning your machine off and back on again, can do the trick.


Is your internal system connected to the internet?

The agent needs to be able to reach out to cloud.tenable.com on port 443.
If you're not sure, try checking the agent status.

If it is connected to the internet, the command will return:

Linked to: cloud.tenable.com:443
Link status: Connected to cloud.tenable.com:443

If it hasn't connected to the internet, the command will return:

Linked to: None
Link status: Not linked to a manager


Did you install using the installation wizard? (Windows)

If you opted for the installer, rather than following the steps then you will need to unlink your agent and relink 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)

  1. Open the command terminal again – as Administrator

  2. Run the link command below

    nessuscli agent link --host="cloud.tenable.com" --port="443" --key="819652a91d674e8d5be08e21299f1a3c69bd9806c72e24bc05df6b32b8db7fe1" --name="[DeviceName]"

    * Make sure that you have replaced DeviceName with your unique device name – instructions for this can be found at the bottom of the page.👇)

  3. Check out targets page to see if it has appeared.


Was the original installation successful?

It sounds obvious but we often find that installation issues are typically related to accidental missteps, or unintentional typos. If you're not sure whether it was successful or not, try checking the agent status.

If it installed correctly, the command will return:

Linked to: cloud.tenable.com:443
Link status: Connected to cloud.tenable.com:443

If it installed incorrectly, the command will return:

Linked to: None
Link status: Not linked to a manager

If it hasn't been successful will you need to start again – making sure that you follow the relevant guide as carefully as possible:

MacOS

Linux

Windows


Agent is 'Running', but I still can't see the internal target. Why?

Running: Yes

Linked to: None
Link status: Not linked to a manager

Although it says 'running', the link status here tell us that something has gone wrong during the installation. To resolve this, just need to follow the steps below:

Install, configure and link (again):

  1. Open the command terminal again – as Administrator

  2. Run the link command below

    nessuscli agent link --host="cloud.tenable.com" --port="443" --key="819652a91d674e8d5be08e21299f1a3c69bd9806c72e24bc05df6b32b8db7fe1" --name="[DeviceName]"

    * Make sure that you have replaced DeviceName with your unique device name – instructions for this can be found at the bottom of the page.👇)

  3. Check out targets page to see if it has appeared.


It was successful (and linked), but still isn't showing. What now?

If you agent status confirmed the following:

Linked to: cloud.tenable.com:443
Link status: Connected to cloud.tenable.com:443

and yet the target still isn't showing on your targets page. At this point we would recommend unlinking the agent, and then linking again. To do that simply follow the steps outlined below:

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)

  1. Open the command terminal again – as Administrator

  2. Run the link command below

    nessuscli agent link --host="cloud.tenable.com" --port="443" --key="819652a91d674e8d5be08e21299f1a3c69bd9806c72e24bc05df6b32b8db7fe1" --name="[DeviceName]"

    * Make sure that you have replaced DeviceName with your unique device name – instructions for this can be found at the bottom of the page.👇)

  3. Check out targets page to see if it has appeared.


Still not working?

Have you triple-checked your linking command is correct? If so, it's becoming more likely that you have an issue with your Anti Virus software, or an internet proxy/filter is getting in the way.

The best thing to do now, would be:

  • Pop a note in the chatbot confirming that you have read this article and eliminated all of the above

  • Send over a copy of your 'linking command'

  • Hang tight whilst the team investigate.


How do I figure out my DeviceName?

Open the Targets page > Add Targets > Internal targets

Click 'View configuration keys'

Copy the 'Prefix'

Your DeviceName is comprised of your Prefix and your TargetName
(what you'd like the target to be named in the portal).

👇
DeviceName = Prefix_TargetName (eg. DQEGBQUAAAc_paul-laptop).



Did this answer your question?