On Fri, 16 Aug 2019 22:02:32 -0600 James Alton <[email protected]> wrote:
> Secondly, I'd learn how to find what port things run on, regardless if > instructions are being provided. > > $ ps aux | grep unifi > > Replace pid below with the pid: > $ sudo lsof -p pid -i | grep LISTEN > > You should find that the unifi daemon is listening on port 8443. Thanks. That and Olli Ries' reply got me further along. A browser on the same ip network got me to a warning of invalid certificate. Come on, guys! Accepting that got me in. The setup went OK from there. It did not find the AP, possibly because of firewalling issues. The VM and the AP are on different class C networks. I noticed that the Unifi software couldn't even correctly detect the network it is on. My initial reaction is that this stuff is fine for a large network, say a corporation or big office. It is way overkill for what I want to do, and the further time and effort I would have to put into configuring the VM and the Unifi software just aren't worth it. So back goes the AP. Thanks for the support, folks. -- "When we talk of civilization, we are too apt to limit the meaning of the word to its mere embellishments, such as arts and sciences; but the true distinction between it and barbarism is, that the one presents a state of society under the protection of just and well-administered law, and the other is left to the chance government of brute force." - The Rev. James White, Eighteen Christian Centuries, 1889 Key fingerprint = CE5C 6645 A45A 64E4 94C0 809C FFF6 4C48 4ECD DFDB https://charlescurley.com /* PLUG: http://plug.org, #utah on irc.freenode.net Unsubscribe: http://plug.org/mailman/options/plug Don't fear the penguin. */
