@forrest 

Thank you, that was the problem.   This should be documented in the instructions.  Using an admin account for everday work is not exactly a good idea.

The controller has now launched correctly, though it did show that a DB had not started.  Once it launched the browser, I got a certificate error from Firefox.   I bypassed that, and now I'm into the controller.  I was able to create an account.

My next problem is that it does not find the AP, which is sitting comfortably on my network, happily displaying a green light.

Any ideas on that?

My admin machine is connected to my router, which is connected to a switch, and the AP is connected to the switch.

Hi @Baronius ,

We are happy that you can launch the Omada Controller now. But as you said, the DB server is not started, it means the Omada Controller doesn't run successfully. Please re-open it and have a try. When it launch successfully, it should be like this: 

For the certificate error, it is normal, please don't worry about it. Actually, the Omada Controller is using a self-signed certificate, so the browser cannot identify the certificate and tell us the certificate error. You can also change the certificate if you have one, please refer to the following faq: https://www.tp-link.com/en/support/faq/866/

After you run the Omada Controller successfully, if you still cannot find the EAP, please close the firewall or anti-virus and have a try.

@forrest 

Thank you, that did the trick.  I had to allow the controller through the firewall, and then it saw the AP.  We're up and running now.  Thanks for the help!

If those items were mentioned on the quick start documentation it would probably save a lot of questions.