07-14-2025 06:00 PM
Run the nso 6.5 local-install, ncs-setup --dest ncs-run commands
The default ncs.conf is set as follows:
I set a static IP to access the webui on the same network band.
When I access the webui with a fixed IP, 400 Bad Request occurs.
Even if you set the IP to 0.0.0.0 and connect, the same 400 bad request occurs when connecting with the IP.
How can I connect with an IP other than localhost?
Thank you in advance for your reply.
07-15-2025 01:37 AM
This should "just work". Do you get any error messages in the logs? Can you upload a (possibly censored) version of your config so that I can test?
07-15-2025 12:01 PM
Note that as of NSO 6.5, host name matching is enabled by default.
https://nso-docs.cisco.com/guides/whats-new#web-server-hostname-matching
Details:
https://nso-docs.cisco.com/guides/administration/management/system-management#exposed-interfaces
Default ncs.conf values:/ncs-config/webui/match-host-name (boolean)
[true]
/ncs-config/webui/server-name (string) [localhost
You can set match-host-name to false in your ncs.conf while developing. See link to docs above why it is recommended to enable it when deploying.
08-12-2025 07:58 AM - edited 08-12-2025 08:10 AM
Hi!
As per the suggested comments by user "cohult", indeed to make it "work" in a development/testing environment, set the match-host-name to FALSE. The webui config portion at the ncs.conf file (for testing) should look like this:
<webui>
<enabled>true</enabled>
<match-host-name>false</match-host-name>
...
</webui>
Please follow the suggested documentation as this is not intended for a production setting.
https://nso-docs.cisco.com/guides/whats-new#web-server-hostname-matching
Hope it helps.
Regards,
AR
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide