Open Onebutterfly-67 opened 6 years ago
@jaimielives If you're constantly getting denied from the HTTP interface then it's most likely that you've not added the IP address of the machine you're trying to login from into allowed hosts
.
You can put it in with your existing list:
allowed hosts = 127.0.0.1,10.36.52.248,10.36.4.63,10.80.15.24,10.36.4.64,10.80.15.32,10.67.6.34,172.23.5.100
or you can add a specific one for the WEBServer:
https://docs.nsclient.org/reference/generic/WEBServer/#allowed-hosts_1
Is the IP you're connecting from in there?
Secondly, do you have NSClient running as a windows service at the same time that you're running nscp test
? That would explain all the IP binding failures
Thanks. I've done that. I've attempted from both localhost and other allowed addresses...
Jaimie
On Mar 10, 2018 17:21, "Rob Emery" notifications@github.com wrote:
@jaimielives https://github.com/jaimielives If you're constantly getting denied from the HTTP interface then it's most likely that you've not added the IP address of the machine you're trying to login from into allowed hosts .
You can put it in with:
allowed hosts = 127.0.0.1,aa.bb.52.248,aa.bb.4.63,aa.bb.15.24,aa.bb.4.64,aa.bb.15.32,aa.bb.6.34,172.aa.bb.cc
or you can add a specific one for the WEBServer:
https://docs.nsclient.org/reference/generic/WEBServer/#allowed-hosts_1
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/mickem/nscp/issues/554#issuecomment-372071755, or mute the thread https://github.com/notifications/unsubscribe-auth/AjeHJL2qSzB9Pui9nMI0oLtAl_y7hzSVks5tdFHbgaJpZM4SjXEF .
@jaimielives Sorry I edited my reply, you may not have seen the edit:
Secondly, do you have NSClient running as a windows service at the same time that you're running nscp test ? That would explain all the IP binding failures
Sorry for the delay in answering. I was away...
On my Windows 2008 box the service is named "ncsp" I was not attempting to run the ncsp test while the nscp service was running.
I have since attempted the installation again, on a new, fresh Win2K8 installation, and get the same basic results.
So, here's the problem... There isn't a problem per se, just an unfortunate collision of events involving another application...
If there is an issue, it's with the implementation of the installer and nsclient logger.
The msi installer is not programmed with a check to see if the default webserver port (TCP/8443) is in use by any other application during the install, does not write the configured port binding into ncsclient.ini, and the nsclient logger does not log the port bindings attempted into the nsclient.log. All in all, this makes it a bit tiresome for folks not familiar with NSClient to figure out what is actually happening.
When NSClient++ is installed, the installer attempts to install the services on TCP/8443 using SSL, but does not check to see if that port is in use, and it does NOT present an option to change the port binding during the install. In this case, the issues described here were caused because the Windows server being used has another corporate mandated background service related to security installed and bound to TCP/8443.
Additionally, the installer builds a sparse nsclient.ini file that does NOT list the port binding (because it's a default...). If the installer is not going to check to make sure the defaults are valid for the local system environment, then at least write ALL the in use configuration options into the ini file so they can be easily parsed and investigated when needed.
Also, the logger didn't give any information about what port binding was attempted... just the error "WEBServer.cpp:179: Failed to start server: failed to open listener". The logger should at least be programmed to include a hint at what was attempted ("failed to open listener on TCP/8443" for example).
So, this has been resolved. netstat -ab is your friend.
Seems we should fix the installer in that case to make it report better errors...
Issue and Steps to Reproduce
Describe your issue and tell us how to reproduce it.
WebUI will not load after install and basic configuration.
Default NSClient++ - 0.5.2.35 x64 install on Windows Server 2008 nscp web install --password myPassword nscp web add-user --user nscpuser --password myPassword nscp web add-role --role limited --grant nscpuser nscp test D core Loading plugin: WEBServer D web Using certificate: C:\Program Files\NSClient++/security/certificate.pem E web Failed to start server: failed to open listener c:\source\master\modules\WEBServer\WEBServer.cpp:179
And WebUI will not allow login. Auth dialog is repeatedly displayed following an http
Expected Behavior
Tell us what you think should happen.
Auth dialog presents, accepts username and password, loads WebUI
Actual Behavior
Tell us what happens instead.
Either the authentication dialog repeats in a loop, or a java exception is thrown. See log snippets below.
Details
Additional Details
NSClient++ nsclient.ini