Unifi AP issues

[Mokester]

So...wanted to set the inform to point to my VPS. For the life of me, cannot get the AP to be recognized in the discovery tool...can't CLI into it either.

Setup a test network with just my computer and the AP hardwired...double NAT for now but whatever. Firewalls off, no VLANs or any craziness...I've heard good things about this company but so far it's been nothing but headaches.

Tried 2 of 3 APs. All the CLI says is connection refused. Light is solid amber so it hasn't been adopted yet. Discovery tool finds nothing and just sits there spinning...not to mention I had to uninstall Java 8 and install 7 just to install the software...Java 8 it would run but then error on javaw.exe not being found.

Anyone got any ideas or am I missing something really basic?

 

[YeOldeStonecat]

What do you mean double NAT? Well..I know what double NAT is...but your network...the AP and your workstation are on the same subnet, right? Like behind a second router is all you mean? So both have the same subnet like 192.168.1.xxx?

Can you find the AP's IP address? Either look for the lease from DHCP or run a quick IP scanner?

What version of controller software?

 

[Mokester]

Yes...I was having issues so I isolated the computer I'm using the discovery tool on and the AP to a brand new router sitting behind my sonicWALL.

Got the IP address...both on same subnet. Tried SSH and no joy...I can't ping it either...but not sure if it's set default to not respond. Controller software on VPS and on computer used for discovery is 3.2.7

 

[Mokester]

Well...uninstalled java 7...installed java 8...one of the forum posts (not gonna look up url...it's on my other computer) said it was okay to do so.

Failed to launch discovery...looking for javaw.exe

Uninstalled java 8, reboot, reinstall java 7 from offline installer. Discovery tool still not working but looks like I can SSH into the second one...gonna try and set inform and then try the first one again. Frankly, if this is how all 3 are going to go, not sure if I want to put this in place at client sites.

 

[karloz]

On the VPS side of things, have you added a DNS entry to resolve 'Unifi' to the IP of your VPS? Just thinking if you could get the AP's added to the controller, then update them to get yourself back in business?

 

[Mokester]

Hmmm....Mac version works on my Mac Air...think I may just go that route for testing...thanks for the help stone.

 

[Mokester]

@karloz - The issue is I can't set inform so DNS is a moot point...but it is setup correctly already on my DNS host...got the mac version of the controller software to work...so I guess all is good? Maybe if I feel up to it I'll take one of the spare laptops I have laying around and do a clean install of 7 and see if my laptop is causing some type of funky issues as I've had bad luck today with computers...setting up RDP access via local SonicWALL user took over 2 hours due to some security updates on the local PC which causing RDP to crash and her home Mac incompatibility with SonicWALL due to Java 8...had to roll her back to 7...

 

[YeOldeStonecat]

You need good name resolution for the controller....and for just a couple of computers behind a router...unless the router does DHCP and has its own local DNS table, the APs won't find the controller. if the router only does DNS forwarding/relay to whatever it obtains for DNS on the WAN...you'll be out of luck. But the discovery tool should find the AP fine.

 

[Mokester]

Yeah...installed the controller software only for the discovery tool...haven't even launched the controller on the computer...the VPS is setup properly and I'm testing to see if it adopts now.

Will test the other APs and then setup that ZH to see how that works...and some other functions of them as well.

 

[phaZed]

Well...uninstalled java 7...installed java 8...one of the forum posts (not gonna look up url...it's on my other computer) said it was okay to do so.

Failed to launch discovery...looking for javaw.exe

Uninstalled java 8, reboot, reinstall java 7 from offline installer. Discovery tool still not working but looks like I can SSH into the second one...gonna try and set inform and then try the first one again. Frankly, if this is how all 3 are going to go, not sure if I want to put this in place at client sites.

You have to change the path in your shortcuts for the Unifi tools, even on a new install. Java 8 changed where javaw.exe is located. Used to be you would find it in C:\Windows\System32\javaw.exe but NOW it is located in the Program Files directory where you installed it. Since the controller software is not aware of the Java 8 changes it assumes the javaw location and makes shortcuts as such... sure an update from Ubiquiti to fix that annoyance is on the way.

Here's Ubiquiti's take on Java 8 and the fixes.

If your running the UniFi controller as a service you will need to basically set that up again too.

I recently had problems at two sites I have AP's at. Both times problems upgrading the firmware and Controller software. Some AP's are seen, some were not. Some started working when I turned off windows firewall, some did not. I had to SSH into a few, etc. I have never had a problem before now and I regarded the setup very robust but I spent a day just mucking around. Definitely some bugs in their software regarding automatic discovery ATM.

 

[Mokester]

Yeah...was able to set the inform address...status changed to adopting...but it's never seen on the vps...I gotta run to coach basketball so maybe later tonight or this weekend I'll take another crack at it but not too thrilled atm.

 

[Moltuae]

Have you tried resetting the APs?

Had similar problems with one batch I ordered recently ... turns out some suppliers are preconfiguring the APs, pointing them to cloud management servers (presumably to make installation simpler). If that's the case, you're either going to need to find out the config details or reset the devices.

I have found the discovery tool to be a little temperamental. I would try accessing them with PuTTY first. Just open PuTTY, enter the IP and port 22 (default). If the APs are reset to factory, they should respond and accept the default login credentials (user: ubnt, pass: ubnt, from memory).

 

[altrenda]

I was configuring some LR's and was having trouble with the wireless uplink.

Downloaded the 3.2.8 Beta Controller and let it update the firmware in the AP's and all was good. Might be worth checking out.

 

[Mokester]

Okay, got most of it sorted out. Still not sure why the windows version of the discovery software doesn't work properly but I got the Mac software working like a charm.

The issue with it not showing up in the management console was me working on it late at night...it's an issue with the security group I applied in AWS not being assigned properly to the VM...DOH

Guess I'll buy an Air, Parallel Win7 and call it a day if I like using the software. Anyone here set it up as a service so the controller is running 24x7? Or are all of you just RDP to the server and launch the controller when you want to make changes?

I'm assuming the controller would need to be running in order for ZH to work properly...unless the hand-off happens within the APs? Not sure on this and need to dig further. Thinking later this week I'll play around with ZH and see how it works.

 

[YeOldeStonecat]

Anyone here set it up as a service so the controller is running 24x7? Or are all of you just RDP to the server and launch the controller when you want to make changes? .

To make it incredibly easy on ourselves....we took an hour to build a cloud controller. To manage all of our clients from just one quick portal. The cloud controller run on an Ubuntu Server instance, when the Unifi APs come in, we quickly provision their Inform URL to point to our cloud controller..and then ship or deliver them onsite. Soon as you plug them in and they get internet access...BAM, they show up in the cloud controller, you adopt them in the clients subsite..and provision their config.

 

[Moltuae]

Anyone here set it up as a service so the controller is running 24x7? Or are all of you just RDP to the server and launch the controller when you want to make changes?

I run it as a service on an AWS EC2, but presently I only fire the system up when its needed.

I plan to move the controller to one of my home/office servers eventually, where it will run 24/7, but I'm in the process of reworking all my home/office network and servers right now.

 

[Mokester]

To make it incredibly easy on ourselves....we took an hour to build a cloud controller. To manage all of our clients from just one quick portal. The cloud controller run on an Ubuntu Server instance, when the Unifi APs come in, we quickly provision their Inform URL to point to our cloud controller..and then ship or deliver them onsite. Soon as you plug them in and they get internet access...BAM, they show up in the cloud controller, you adopt them in the clients subsite..and provision their config.

Kinda what I was thinking too. Have you worked with the Zero Handoff function or the integration for billing for internet hours? Think that is about the only things I have left to dive into but so far I'm really liking the range and speed of the APs as well as the config options.

 

[PCSupportGlasgow]

The windows discovery tool can be a bit temperamental with windows firewall, turn window firewall off for few seconds and it will discover the APs without any fuss.

 

[Mokester]

@ PCSupportGlasgow - Tried that. Still didn't work and wouldn't find the APs. As I stated earlier in the thread, I'll try installing it on a fresh build, though I doubt that will solve the problem...my windows laptop was bought around the time my company started and only does work stuff so it's pretty bare. Only been around for 7-8 months also.

 

[PBComputer]

The windows discovery tool can be a bit temperamental with windows firewall, turn window firewall off for few seconds and it will discover the APs without any fuss.

I recently had a issues with my unifis window firewall was the culprit. Was going to post it, just too manic in the shop.