[04:01] <mybalzitch> rip his array
[10:06] <tomreyn> daevski: hmm. looks like you installed NM as a snap (is it no longer available through apt then?). i'm not sure this has anything to do with the wireless not authenticating. I'd be willing to rather bet on a badly supported wireless chipset. which chipset is it? does it work fine with the same ubuntu release and kernel version and of ubuntu desktop (in case you tried)? have you ever used this very wireless chipset successfully under Linux?
[10:07] <tomreyn> lspci -knn | grep -EA3 '(Network|Ethernet) controller'     would provide us with information on the network device
[10:09] <tomreyn> also, the first threee bytes of the access point you're trying to connect to aren't registered to any manufacturer e0:22:04:... can you tell us more about this device?
[10:16] <tomreyn> http://standards-oui.ieee.org/oui/oui.txt lists organization unique identifiers (of the first three bytes of MAC addresses) in the nn-nn-nn format (rather than the nn:nn:nn format).
[10:18] <tomreyn> So while E0-22-04 isn't registered, E0-22-02  is registered to ARRIS group, a CPE vendor for devices often providing a wireless AP.
[12:37] <daevski> tomreyn, `product: BCM4331 802.11a/b/g/n`. same issues on desktop edition through the gnome interface, but the wifi works perfectly well in Kali linux. 
[12:39] <daevski> kali has a bit more in the box  than is needed for a docker container server, so ive been spending several days trying to fogure this out. 
[12:44] <daevski> i think i can actually work around this issue. the server is installed and ether net works. i can drop this macmini next to the router after setting a static ip for it. thanks for taking the time to look at it with me!!