Cisco 140AC Missing Action Button on Management Interface

[ronb7gens]

I have 18 Cisco 140ac access points in one of my schools.  I am having problems with some of the APs unjoining and then rejoining.  When this happens, the unjoined AP shows as "Mesh Extender", then that goes away when it rejoins.  I don't have Mesh Extenders set for any of the APs. I looked at the logs and found some errors, and found some suggestions on this forum in this post:

https://community.cisco.com/t5/wireless/cbw140ac-un-joins-every-few-minutes/td-p/4664934

Another post suggest checking each AP:

https://community.cisco.com/t5/wireless-small-business/cbw240ac-subordinate-ap-offline-issue/td-p/4690878

However, when I log in to the Management IP address, there is no "Action" Button where I can edit each AP.  Tried Chrome and Edge, same issue, so don't think it is a browser issue.  

Note:  Originally AP01 was primary AP, I gave it a management address which I use to access the APs.  However, AP14 shows as primary in the AP list, but a check on "Primary AP Information" still shows AP01 (all APs are listed as Primary Capable).  I am accessing via browser, as I am using VPN to the school network (ciscobusiness.cisco connection won't work from my office).  Firmware version 10.6.1.0., there are later versions available. 

Would accessing via ciscobusiness.cisco make a difference and show me the Action button?  I need to get the edit action working so I can see what is going on.  I will be going to the school next week (it is a 1.5 hour trip each way, so I can't just go check it quickly).  

Thanks in advance for any ideas or suggestions.

[Rich R]

Chrome & Edge are both based on the Chromium browser engine so not much difference so try Firefox including older versions.

Updating to latest available software version is essential to ensure you have the fixes for any known bugs that have been fixed.

Shortcuts like ciscobusiness.cisco will only work locally when you are actually connected to the device because they are designed to intercept the request and redirect it to the device.  I wouldn't expect it to make any difference but you won't know until you try.