08-11-2015 11:25 AM
In a sense it is your password. You need to use the -i option. command would look like this:
ssh -i "???.pem" ubuntu@IPOfController
Im on Filezilla FTP manager.
08-11-2015 05:37 PM
Here is information on how to convert your AWS key to work with Filezilla (I use FZ as well): http://stackoverflow.com/questions/16744863/connect-to-amazon-ec2-file-directory-using-filezilla-and...
10-14-2015 12:32 PM
Package repo as of 14 Oct 2015 can be derived here:
04-11-2016 05:57 AM
Everything went okay untill entering https://publicdns:8443 in the browser, this doesn´t work.
I forwarded all the ports like in the walkthrough, but when I use an online port checker only port 22 is open, the rest stays closed.
Does somebody have a solution for this?
07-07-2016 04:47 AM
Step 2. Find the "Set Inform" step and change the Set Inform URL to the following: "https://<Public DNS or Elastic IP>:8080/inform
^^^^ Regards this step.
Is there anyway to get the Set Form part automated from a script so once the devices are plugged into a network switch, we can automatically add this to gain remote control?
07-07-2016 05:29 AM
yes, you need to set a DHCP option.
refer to https://help.ubnt.com/hc/en-us/articles/204909754-UniFi-Layer-3-methods-for-UAP-adoption-and-managem... for all the details.
07-07-2016 10:50 AM - edited 07-07-2016 10:51 AM
Yes, using the Unifi Option on Edgemax Router is great, I've done this.
Yes, using DHCP Opption 43 also works, assuming the DHCP server is something that is configurable (ie, not a SOHO router) and assuming you have control over (not always the case, client routers, etc).
What I am curious about like the original poster you replied to, and issues I have run into, is that I will adopt and configure a UAP on my cloud controller on my own network, but then when I disconnect and either ship or install at another network (ie, the client's network/site) the Controller "loses" the UAP. The only way to get it back on the controller is to do a factory reset, or while on the client's network, have the controller "foget" the UAP, then use the UBNT discovery utility and re-set the inform.
With all that said, what I am trying to do, is ship, ready to go UAPs (read: adopted), that clients can just plug into their network without any work, configuration, and without having to tamper with their network (router, DHCP server, etc).
Is this possible ?
07-08-2016 07:33 AM
Get a device ready-to-ship to a customer site and before you do, ssh into the device, run mca-cli, and then run the info command.
you'll likely see:
Status: Connected (http://unifi:8080/inform)
Note that the Status entry just says "unifi" for a hostname - this is because the domain I'm handing back via DHCP is also the domain where "unifi.domainname" is pointing to my controller. If I take this AP to another site where the DHCP server hands back a different domain name such that the host unifi.differentdomain.com doesn't exist, the AP will never talk to the controller.
there's 2 fixes for this -
- SSH into the AP, run mca-cli, and then run set-inform http://unifi.yourdomain.com:8080/inform
- or, even better, UBNT makes a really easy firmware change - when the AP finds http://unifi.<dhcpdomain> exists, set the inform URL to the full domain, not just "unifi".