cURL call to NCPA port returned invalid JSON

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
Locked
huntrace
Posts: 2
Joined: Tue Apr 07, 2020 10:03 am

cURL call to NCPA port returned invalid JSON

Post by huntrace »

Hello Forum,

installed Nagios XI Appliance latest version (5.61.12), trying to monitor a Hyper-V host.
Installed NCPA-Client on Hyper-V host with default parameters - latest version 2.2.1.

I'm able to connect via web-browser to https://ip:5693 by giving the API-Token.
Works fine.

If i try to use configuration wizard on Nagios XI GUI I get an error "cURL call to NCPA port returned invalid JSON".

All machines are in same subnet, no firewall between machines.
Maybe this is a problem with self-signed certificates (I guess created by NCPA)?

Regards
Michael
benjaminsmith
Posts: 5324
Joined: Wed Aug 22, 2018 4:39 pm
Location: saint paul

Re: cURL call to NCPA port returned invalid JSON

Post by benjaminsmith »

Hi Michael,

Welcome to the Support Forum and thank you for trying out Nagios XI! Do you have special characters in the token that maybe getting passed incorrectly, and would you be able to test again with a simplified password?

If that's not the issue, can you post the output to the following test command ( run from Nagios XI terminal)?

Code: Select all

curl -k "https://<ip address>:5693/testconnect/?token=<your token>" -v
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.

Be sure to check out our Knowledgebase for helpful articles and solutions!
huntrace
Posts: 2
Joined: Tue Apr 07, 2020 10:03 am

Re: cURL call to NCPA port returned invalid JSON

Post by huntrace »

Hi Benjamin,

thanks, you did it - there was a "#" in the Token.
I substituted these special-character and it worked fine.

Thank you,
Michael
scottwilkerson
DevOps Engineer
Posts: 19396
Joined: Tue Nov 15, 2011 3:11 pm
Location: Nagios Enterprises
Contact:

Re: cURL call to NCPA port returned invalid JSON

Post by scottwilkerson »

huntrace wrote:Hi Benjamin,

thanks, you did it - there was a "#" in the Token.
I substituted these special-character and it worked fine.

Thank you,
Michael
Great!

Locking thread
Former Nagios employee
Creator:
Human Design Website
Get Your Human Design Chart
Locked