Skip to main content
Eijyyy
New Member
March 5, 2026
Question

Can't access the NAC GUI

  • March 5, 2026
  • 3 replies
  • 246 views

I am trying to deploy an FNC-CA-500F.

I changed the IP address of my network card to 192.168.1.10 so it matches the default address 192.168.1.99 of the NAC. I was able to access the device via PuTTY, and I configured allowaccess https-adminuiin port1.

The ping to 192.168.1.99 is successful, but I am unable to access the graphical user interface (GUI).

Do you know why this might be happening?

 

3 replies

AEK
SuperUser
SuperUser
March 5, 2026

Just in case you missed it, the WebUI is listening on port 8443, not 443.

AEK
Eijyyy
EijyyyAuthor
New Member
March 5, 2026

yes i tried it many times , https://192.168.1.99:8443

ebilcari
Staff
Staff
March 10, 2026

It usually take some time for the FNAC application to start 5-10 minutes. To check the status of the processes you can use the following command:

 

fnac76 # diagnose tail -f output.processManager
2026-03-10 13:37:29.552 +0100 [main] INFO yams.CampusManager - [isSystemOK] latest predefined result true custom health check result true, final result true
2026-03-10 13:37:29.855 +0100 [main] INFO yams.CampusManager - Loaders are running.
2026-03-10 13:37:29.855 +0100 [main] INFO yams.CampusManager - Processes are running

 

If something is preventing the services from starting you can also check this log files:

 

fnac76 # diagnose tail -f output.master

fnac76 # diagnose tail -f messages

Emirjon
Thought Leadership Security Summit. Outpace New Threats with AI - enhanced defense. Tuesday, Septmeber 15, 8:30 AM - 2:30 PM PT. The Golf Club at Newcastle, WA.
Virtual event | September 2026. SASE summit. The age of autonomous trust. Register here!