Bigfix on TenableSC

Usage and Config
21

Can you post a screenshot of the error. Thanks.

22

image
image1896×742 40.5 KB

23

you are still lucky. Mine is showing that i never configured ivr 4.1.

24

Ok, so Julius, I don’t have a good feel that you ran ‘ivrNext --setup’ or if you did that WebUI could connect to it. During the phase when you run ‘ivrNext --setup’ WebUI needs to connect to it on port 8099, so ensure you have a firewall rule for it. After setup, the ivrNext service will listen on port 9011, so ensure you have a 2nd firewall rule for that.

Rich, you require the Patches sites enabled, Computers subscribed to those sites, and current evaluations of those patch Fixlets by the subscribed Computers. I had exactly the same blank report as you did, as my data was really, really old, but as soon as I powered on the subscribed Computers and got a refresh of their applicability to patch Fixlets, my IVR app in WebUI immediately showed me the expected data.

25

Hi. Yes, i did all of that. Actuallh IVR is pulling data and download going to its SQL BFIvr database my problem is if i will check ivr data in webui app IVR it saying likei never yet set up ivr. BFRetrirver servive is also running.

26

In addition, all bigfix application are all in one server. Only databases are on a separate server.

27

Julius, check your database for this entry, and if it does not exist, you need to go through the setup steps again.

image

28

Ok. Yes, i saw this in the log. Btw how this token generated? We repeated tge setup3 t8mes already. Thanks.

29

I do have the Patches sites enabled. This worked with 2.x before I upgraded.

image
image832×482 12.2 KB

30

There was no result found. I donr know how that being generated. I ran the ivr setup but still the query has no result

31

You should probably.open a support incident so the team can review your logs and configuration.

32

Yes. HCL support still figuring out the issue. Actually this is our first ivr implementation with tenableSC which my assumption is the token or private key was created in the lower version of IVR. So i am not sure if we are the first one to implement ivr.4 and tenablesc with previous ivr version installed.

33

2025-03-14T19:44:43.708Z bf:ivr:cache:debug No IVR private key found in WebUI Data
2025-03-14T19:44:43.708Z bf:ivr:cache:debug IVR private key not found

34

Hi Guys,

We already resolved our issue. You’re correct We used server signed cert but we used differenent webui site that was on our F5 load balance instead of the server certificate.

Thank you!