NSX Intelligence Installation succeeded but admin user cannot see anything

[KaBalint]

Hello Everyone!

I am trying to install and get some hands on experience with the brand new NSX-Intelligence, but i've ran into an issue.
After the successful appliance deployment, when i've open the Plan & Troubleshoot -> Discover & Take Action or Recommendation tabs, it says "The application server is unable to fulfill your request due to insufficient privileges. You do not have the privileges to access NSX Intelligence. (403 Forbidden)". I am trying to reach this view/menu with my default enterprise admin user (admin).
Actually i also started to debug the issue the time syncron is okay, the checksums of the images also correct, and also started to check the logs, on the web interface i can see the nsx-intelligence certificate at the system tab and there is the nsx-intelligence user too.
Is there anybody who had experienced something like this?

Kind Regards,

KB

[mauricioamorim · Accepted solution]

There's a known issue that is in the release notes that might explain your problem:

Issue 2410224 - After completing NSX Intelligence appliance registration, refreshing view may return a 403 Forbidden error.

One other thing that can give this error is if you are using CA-signed certificates for the NSX Manager. If you are or have changed the certificate of Principal Identity you should revert to the default self-signed certificates.

[KaBalint]

Hi mauricioamorim,

Yes i have found that known issue, i waited one night. it does not solved the problem.

Actually i found out the self-signed CA was the issue, i forgot to write under this thread.

Thanks for your answer!

Kind Regards,

KB

[KaBalint]

Does anybody configured the NSX Intelligence with an NSX-T which is integrated with VMware Enterprise PKS ?

Because of this product would have the big value in the nearly real time traffic monitoring and firewall rule recommendations, but as i can see it is not working with changed certificate.

But the first step says when you configure the Bosh directory with NSX-T to give an NSX CA Certificate, I made exactly the same as the KB says, but it is still not working.

[mauricioamorim]

NSX-T 2.5.1 was released last week and includes a workaround for the certificate change issue. Haven't tested it yet, but it should work.

Look at issue 2436302 in the release notes: VMware NSX-T Data Center 2.5.1 Release Notes