NCPA - '[Errno 104] Connection reset by peer'

[nagiostra]

I'm stuck on the fact that it was working and then stopped working. Clearly something changed on the Windows host. I'm happy to help but from where I'm sitting it's difficult for me to begin to know what that change might have been. Anything you can think of might help. I don't really have a next step to suggest other than uninstall/reinstalling the ncpa software.

[nagiostra]

I'll keep digging. We'll figure it out.

[nagiostra]

Not knowing your environment I don't know if you can do this... If you can, temporarily turn off (disable) the firewall on the Windows host??

[nagiostra]

The token field is empty. That's the field ncpa uses for authentication. Can I give you some good advice? You'd be doing yourself a huge favor if you dig into the documentation on their website. For just about anything you need to do, there's plenty of info.

[nagiostra]

Did adding the token resolve your issue?

[hdurans]

Hi, I have the same issue,

[XXX@XXXX ~]$ /usr/local/nagios/libexec/check_ncpa.py -H **** -t ***** -M disk -l
UNKNOWN: An error occurred connecting to API. (Connection error: '[Errno 104] Connection reset by peer')

with nmap the port is open


PORT STATE SERVICE
5693/tcp open rbsystem

$ curl -v https://****:5693
* Rebuilt URL to: https://****:5693/
* Trying ****...
* TCP_NODELAY set
* Connected to ****(****) port 5693 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile: /etc/pki/tls/certs/ca-bundle.crt
CApath: none
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to ****:5693
* Closing connection 0
curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to ****:5693

you have any solution?

Thanks

[jmichaelson]

Are you able to connect to the NCPA client with a browser? i.e., go to https://ip address:5693/?

Ignore the ssl warning that will appear, and use your token to log in.

[hdurans]

Are you able to connect to the NCPA client with a browser? i.e., go to https://ip address:5693/?

Ignore the ssl warning that will appear, and use your token to log in.

Yes, I try to other server and url respond and I log in sussessfully