Anybody who has had the chance to work with the Ubiquiti Unifi products knows how great they are. Or do they? The coolest feature of the Unifi product is its ability to be managed from a cloud based controller. This allows the integrator to be able to manage the network with out having to leave the office. Also some testing can be done, like speed testing directly from the Unifi Security Gateway.  Another great benefit is that since Amazon provides free “Micro Server” instances, this entire process will quite literally cost you pennies a month!  Lets start by going over the first steps to getting you up and running within the Amazon AWS System.

Part 1

Creating the Instance

Ubiquiti Unifi Controller in the Amazon AWS Cloud

First you will need to setup an account for Amazon’s AWS Service.  Once you have registered for your account and logged into your Dashboard, you should select their “EC2 option to create a new “Virtual Server in the Cloud

In order to make this as simple as possible, select the North Virginia (N. Virginia) Region as it has pre-built servers meant for the Unifi System.

Ubiquiti Unifi Controller in the Amazon AWS Cloud

Our Unifi Controller will run on an Amazon Instance so we will need to create one before we can get started.  Start by clicking on Instances under the “Instances” on the left-hand menu (see the screenshot on the right).  You should see a new page here that has a large blue “Launch Instance” button available.  Click on that to continue to the next step.

 

Ubiquiti Unifi Controller in the Amazon AWS Cloud

This is where we can take a little bit of a shortcut to make the entire process a little bit easier.  Generally we would now have to create a new Instance, select an Operating System, install the Unifi Controller, and other steps.  However, Amazon’s AMI System allows us to quickly launch a pre-created instance of the server that we will need to make everything work properly.  Click on Community AMIs and type Unifi into the search.   We are looking for an Ubuntu based instance. This one pictured below works for sure, not all will.

A lot of the default options will work out just fine for us, so we will just click next as we move through the setup process. A Micro Instance is what we are looking to create, and it is covered under the Amazon Free Tier. So we just click Next: Configure Instance Details. The next page also does not require any changes, again we click Next: Add Storage.

 

Now for Storage, we want to take advantage of the Free Tier and upgrade our instance to an SSD which is included.Ubiquiti Unifi Controller in the Amazon AWS Cloud

Ubiquiti Unifi Controller in the Amazon AWS Cloud

Once we have made this change, we can click Next:Tag Instance. Tagging is not necessary for our instance to work, so we will skip this step. Next: Security Group.

Here will be adding some additional rules that will allow our controller to function from the cloud as if it were on our local network. Ubiquiti Unifi Controller in the Amazon AWS CloudWe will be adding a series of Custom TCP Rules and one Custom RDP Rule. All of these rules will have the Source set to Anywhere.

The TCP ports that we will add, will be 8080, 8088, 8443, and 8843. The UDP port will be 3478.

It should look like this once you have them all added. Then we click Review and Launch. And if everything looks good, we click Next again.

Ubiquiti Unifi Controller in the Amazon AWS CloudUbiquiti Unifi Controller in the Amazon AWS Cloud

This next part is Very Important!  We are about to create the .pem file which is our key file and is what we will use later on in order to SSH into the instance and update to the newest controller version. We will choose “Create a new key pair”, name the key pair and download it. Save this file in a place you will be able to find it later .

 

Now click “Launch Instance”. Your Instance should now be here in your EC2 Dashboard. We will want to create an Elastic IP for our Instance right away. Think of this as a Static IP so our controller is always at the same address. Under “Network & Security” click Elastic IPs. Up at the top click Allocate New Address. Then click Yes, Allocate.

 

 

Ubiquiti Unifi Controller in the Amazon AWS CloudUbiquiti Unifi Controller in the Amazon AWS Cloud

 

Then click on View Elastic IP.  Next click Associate Address. As soon as you click in the Instance field, your new Instance should show up. Click it. Then Click Associate down in the corner.

 

Ubiquiti Unifi Controller in the Amazon AWS CloudUbiquiti Unifi Controller in the Amazon AWS Cloud

Now back to our Instance. Under the Name, click the pencil and name it something so you can easily tell what it is in the future. This is especially helpful when you have more than one instance. By now, your Instance should be running and have completed its checks. Make a note of the Elastic IP address, this is how we will access the controller later. Click the box in front of your instance.

Ubiquiti Unifi Controller in the Amazon AWS Cloud

This next part is where we will SSH into our instance, so that we can upgrade the version of controller we will be running. There are a few different complications that can come along with this process. We used to suggest using Chrome in order to make this process as smooth as possible but Java support has changed. It may be easiest to use a different browser. You also want to make sure that you have Java and that it is up to date.

Update as of May 3, 2015

If using Chrome, an additional step has become necassary. It is described in full detail here.

 

Click the check box in front of your instance and from the Actions dropdown choose Connect. We want to connect using “A Java SSH Client”. So choose that option and then change the User Name to ubuntu.

Ubiquiti Unifi Controller in the Amazon AWS CloudUbiquiti Unifi Controller in the Amazon AWS Cloud

 

Ubiquiti Unifi Controller in the Amazon AWS Cloud

Now here comes the tricky part and where we will use that key pair from earlier.
We need to have the exact location of where that file is at on our computer. Navigate to that file and click on properties. Copy the complete file location. Paste that info into the “Private Key Path”. You also need to add the exact file name after the location. It should end up looking something like this.

C:\Users\Spin\Desktop\Integration Tools\Spin-Ubiquiti-unifi-contoller.pem

Click Launch SSH Client. If all goes well, you should see some kind of MindTerm Security Warning. Accept the risk and click Run. The first time you do this, you may get a couple messages along the way, go ahead and agree or click yes to any messages.

 

Then once you accept and run, you should get to this.

 

Ubiquiti Unifi Controller in the Amazon AWS CloudUbiquiti Unifi Controller in the Amazon AWS Cloud

Ubiquiti Unifi Controller in the Amazon AWS CloudOk, this next part may not be acceptable by the SSH standards of those smarter than us, but it works. Try this at your own risk, we don’t assume any responsibility, but if you screw something up, you just delete the instance and start over. No big deal

Ok, first command:

sudo su

<enter>

Next command:

 nano /etc/apt/sources.list

<enter>

You should see something like this.

Now arrow all the way to the bottom so we can add a new line. Type this exactly:

deb http://www.ubnt.com/downloads/unifi/debian stable ubiquiti

<CTRL X>

<Y>

<enter>

Next command:

apt-key adv --keyserver keyserver.ubuntu.com --recv C0A52C50 

<enter>

Next command:

apt-key adv --keyserver keyserver.ubuntu.com --recv 7F0CEB10

<enter>

Ubiquiti Unifi Controller in the Amazon AWS CloudNext command:

apt-get update

<enter>

Next command:

 apt-get install unifi

<enter>

Let it run and answer <Y> if prompted. Close the SSH. Open a browser tab and enter https://ElasticIP:8443/login. Replace Elastic IP with yours. There may be some initial setup requested when you first login. Then you should see this which means you are now running 4.2.0.

 

 Part 2

How to adopt a Unifi Device to your new Cloud Controller

 

If setting up a USG with PPPoE follow these steps first
  • Don’t adopt it to any controller yet
  • Plug it into power
  • Plug ISP to WAN
  • Plug laptop into LAN
  • Go to 192.168.1.1
  • Login if it asks 
  • From the drop down tab and choose PPPoE
  • Click save
  • Once you get internet you can proceed to adopt to AWS with theurc discover tool
  • If it doesn’t connect to the internet, power cycle only the modem
Ubiquiti Unifi Controller in the Amazon AWS Cloud

Using the Unifi Discover tool is simple. It can be downloaded here. Make sure to download the one for Unifi Switching and Routing. This one will support Unifi access points too.

 

We open it up, and let it find the Unifi devices that are on our network. They will automatically populate if they are on the local network with your computer. If you are trying to move a previously adopted Unifi product, it is easiest to just default the unit by holding the reset button. They can be adopted with out losing the settings, but you need to login to them first with the old controller and get the assigned username and password.

Ubiquiti Unifi Controller in the Amazon AWS CloudOnce your devices show up in the tool, there will be an option for “Manage”. Click that. Down at the bottom, there will be an IP address that they are looking to. Copy the Elastic IP address from your controller, which should be open in your browser at this point. But Copy only from before the “:”. Then Paste this into the Manage section IP address before the “:” that is there. It should look like this https://ElasticIP:8080/inform. This way you will be replacing the existing info with yours, while retaining the port number from Unifi.

 

Now in our Unifi controller, we will add a new site. Name this the job name, or however you will remember it. Click on Devices.

 

Ubiquiti Unifi Controller in the Amazon AWS Cloud

 

By now, your new device probably has already shown up. If not, press the refresh in the upper right. Next to your device, there will be an option for Adopt. Click that. It will go through a process of Adopting and then Provisioning. While this is happening, you can go into Settings (bottom left hand corner of controller) and add your SSIDs and such. Upgrading is the way to push updates to the devcies so if it becomes an option, you should do it.

Ubiquiti Unifi Controller in the Amazon AWS Cloud

You can add a custom map and place your AP’s appropriately to check coverage. And check network status as well as test speed from the USG
Ubiquiti Unifi Controller in the Amazon AWS CloudUbiquiti Unifi Controller in the Amazon AWS Cloud

Part 3

How to configure UPnP for the USG through the AWS controller

-This has been necassary to solve some issues related to the URC ZW-1

First, find the name of the site you need to turn on UPnP for

  • Go into the cloud controller
  • Pull up the site needing UPnP
  • Look at navigation bar – site name is as listed:
  • https://[cloudaddress]:8443/manage/s/[sitename]/dashboard

SSH into the cloud controller using Spins instructions

  • Sign into the aws.amazon.com site
  • Click EC2
  • Click Instances
  • Click Connect Connect with a Java SSH client directly from my browser
  • Username change to: ubuntu
  • Put in complete path to your private key
  • Launch SSH Client

Once in SSH, do the following commands:

sudo su

<enter>

 

nano /usr/lib/unifi/data/sites/[sitename]/config.properties

<enter>

config.igd.enabled=true

<CTRL X> <Y> <enter>

Quit the SSH session
Go back into the site in the cloud controller and get the USG to provision, changing the name of a port forward should force it to provision.

Part 4

Updating to new software

-This is not necessary if you have just completed your AWS instance setup. Updating is only needed when an update becomes available.

What if you have already done all this and are using this controller to manage all your clients and a software update becomes available with new great features? Not only is it possible to update the software without losing anything you already have, its easy. All you need to do is SSH back into your instance and run the update and install again.

First line:

sudo su

<enter>

Next command:

 nano /etc/apt/sources.list

<enter>

You should see something like this.

Now arrow all the way to the bottom so we can add a new line. Type this exactly:

deb http://www.ubnt.com/downloads/unifi/debian stable ubiquiti

<CTRL X>

<Y>

<enter>

Next command:

apt-get update

<enter>

Next command:

 apt-get install unifi

<enter>

Thats it, once your controller restarts, you should now be running the latest software.

 

This concludes the tutorial on how to setup a Unifi Controller in the Amazon Cloud

-Spin

 

Special thanks to Chris, Chad, Braden, and Aaron for their contributions


72 Comments

  • Joshua Edman

    February 2, 2015 at 2:06 am

    Amazing walkthrough & guide Justin! Thanks for the contribution.

  • Jack

    February 3, 2015 at 11:22 pm

    Thanks for the guide; it was very easy to follow. The wizard at the end of the guide (the one at the elastic ip for the controller) had me setup a username and password. But at the login screen, it says it’s invalid. Any idea what would cause that (I followed the guide to the T)? Thank you in advance!

    • Justin Spiniolas

      February 6, 2015 at 12:30 am

      That was my fault. Sorry about that. I didnt realize that what I typed changed when it went public. I have updated it to be correct and easier to read the ssh lines.

  • Chad Lang

    February 6, 2015 at 5:30 pm

    Thanks for the awesome guide. Super simple to follow. My only problem: the controller never asked me to setup a user name and password and I can’t log in to the controller. I tried ubnt / ubnt but it didnt work. Any suggestions?

    • Justin Spiniolas

      February 6, 2015 at 6:27 pm

      I have updated again suggesting to use that specific AMI that is pictured, It seems some people have had trouble with other ones.

      • Chad Lang

        February 6, 2015 at 7:19 pm

        Thanks Justin. Tried again following your updated information and it worked perfectly. Excellent instructions!

  • Jack Thompson

    February 10, 2015 at 4:21 am

    Thank you for the updated guide. I was having trouble with it until I re-read it tonight thanks to Chad Lang. I was using a different AMI, and that was my problem. I can log-in now; just need to discover the APs, which I will do tomorrow.

  • Mark

    February 11, 2015 at 10:17 pm

    I get as far as “launch ss client” where I input the file location but nothing,….any ideas?

    • Justin Spiniolas

      February 12, 2015 at 12:32 am

      This turned out to be an issue with Java security blocking the action. By adding https://console.aws.amazon.com to the Java security exceptions, this problem was resolved.

  • Justin Spiniolas

    February 22, 2015 at 5:22 pm

    On February 22, 2015 this was updated to reflect some changes that UBNT made with a new update. I have also added how to update to this newest software version.

    • Jack Thompson

      March 6, 2015 at 7:31 pm

      Justin, I followed your update instructions, but it said I had the latest version. So I am assuming I did it correctly. Thanks again.

  • Sam

    March 24, 2015 at 11:47 pm

    I tried to follow every step however the UniFi AMI wasn’t available so I set it up with a compatible Ubuntu AMI recommend by Ubiquiti and I got through all the steps like you said but now I am trying to get to https://ElasticIP:8443/login with my ElasticIP and its not able to connect do you have any suggestions?

    • Justin

      March 25, 2015 at 12:21 am

      Connect to the instance through SSH and check to see if Unifi installed properly by running this command “sudo service unifi status”. If it returns that “unifi is running” then you should be fine. Otherwise something didnt work. Check to make sure your region is set to N.Virginia in order to have access to the premade AMIs for Unifi. Report back as much information as you can.

  • Steve

    April 2, 2015 at 6:21 pm

    I am not getting the Part 2 of the tutorial , to adopt the Ap in the cloud, can you assist . I am seeing the AP in the controller adopted that is on my computer but not on the cloud.
    thanks

    • Justin

      April 2, 2015 at 7:38 pm

      You wont be able to adopt a Unifi that is already adopted. You will need to default whatever you are trying to adopt if it has already been adopted to a local controller.

  • Steve

    April 2, 2015 at 8:47 pm

    OK i got that part to work but now when it adopted it saying upgrading and reboots all the time Thanks for the help

    • Justin

      April 2, 2015 at 8:51 pm

      It is normal for it to reboot after the upgrade process. Be patient, it should come back online after an upgrade.

  • Steve

    April 2, 2015 at 10:00 pm

    Thank for your response but for the past hour its showing UPGRADING for 3 mins then REBOOTS then upgrading , then 3 mins again then reboots. in a continuous cycle.

  • Steve

    April 2, 2015 at 11:30 pm

    anyway theses are the changes i made i ssh into the console and get unifi , not the beta and the Ap connects fine now . The problem i got now the guest page is port 8880 and i dont know how to add that port in the instance . Is there a way to edit that that

  • Steve

    April 2, 2015 at 11:36 pm

    Thanks alot i got it i added the port and it works

  • Gary

    April 7, 2015 at 1:07 pm

    I followed these instructions, and used the exact same AMI, but was never able to log in to the controller. I get all the way through setting up the username and password upon first controller launch, then it asks me to login, and just says invalid. I looked in MongoDB, and the username/password pair is correct. The UniFi controller just acts like I typed it incorrectly. Started over with a new instance… same thing. Bizarre, as I’ve never had a UniFi controller do this.

    Uninstalled it… cleaned the Mongo entries… installed rapid release instead of Beta, etc. Nothing works.

  • Gary

    April 7, 2015 at 2:25 pm

    My fix was to abandon Ubuntu 10, as its EOL. Set up a fresh Ubuntu 14 instance, then manually installed Unifi and mongodb. All works perfectly.

  • Steve

    April 9, 2015 at 4:32 pm

    I have a problem i would like you to help me with. The AP is no longer in my position and I want some help to customize the guest portal from another location its working fine with your tutorial here. But i need some help to customize the portal page remotely. Thanks

  • Brian

    April 10, 2015 at 8:54 pm

    I am having trouble with part 2 the discovery within AWS.. I got the controller installed and can access via elastic IP and all works fine. From what i understood was we should have installed it to our computer as well to do the discovery, then add the AWS Public DNS or Elastic IP into the inform URL box with port 8080 and the /inform switch. MY Cloud instance doesn’t find the discovery or any devices. my computer is plugged into the same network as the AP and I can get them to populate on a local controller, however not the cloud controller. . I have reset the AP but still not ale to get anything to show in the cloud. am I missing something that anyone can answer?

    • Justin

      April 11, 2015 at 4:13 am

      Brian, It sounds like you are doing everything right. Triple check that you are entering the elastic IP in the Discover Tool correctly. I like to copy and past in order to avoid mistakes here. Make sure you have it as https://. Also to be noted, you cannot adopt a Unifi device to the Cloud controller if it is adopted to a local controller already, it would have to be defaulted. But that doesn’t sound like your problem here, as you would get an error trying to remanage an already adopted device. I would also check your security ports that you have 8080 included. Hope this helps.
      -Justin

      • Alan

        April 16, 2015 at 10:07 pm

        I have the same problem as Brian. I have the uniFi controller up and running but after setting the “Inform” address in the UniFi-Discover tool, nothing ever shows up in the UniFi controller. I figure it musty be something simple, but I keep going over the steps many times, and same results… Do I have to do the software update before I can do the adoption in the controller? I skipped this step because I could not make that work either. Any help or suggestion is appreciated.

        • Justin

          April 17, 2015 at 12:22 am

          Alan,
          The update is only for when an update becomes available. If you just set up your instance, it is already running the latest version. It must be something simple that you are missing. There are a large number of us involved with DashOS that are using these controllers everyday. As I told Brian, make sure you are using https:// and your elastic IP but leave every after the : as it is. What I do is open my instance in my browser, copy the https://elaticIP: and paste it into the appropriate place in the Discover Tool. Then I refresh my instance, and my device is there ready for adoption.
          Hope this helps,
          Justin

          • Alan

            April 17, 2015 at 7:48 am

            Thanks Justin. I’ve tried it so many times. Everything works until I want to adopt the AP’s. I just tried it again with a different controller and it worked. Go figure! Thanks again and thanks for the tutorial and helpful guidance.

  • Chris

    April 13, 2015 at 12:57 pm

    Ho… Le.e… Crap… this stuff is WAYYYY over my head. Had no idea what ANY of the steps meant, but I just followed and typed like a monkey, and it worked. Just had to add the Amazon AWS to the Java secure site list like you mention above. Thanks so much–I would have been lost without this guide.

  • Will

    April 19, 2015 at 10:10 am

    Worked perfectly, thanks! Now I am trying to modify my portal page with SFTP and it won’t let me upload ( Cyberduck fails). I have changed permissions etc.

    A df -h shows I’m at 100%? – Does this really use all of the 8GB instance?

    Anyone else experience this?

  • Barry

    April 24, 2015 at 4:39 pm

    I ran into a issue with Guest access. I did some searching on the internet.
    Found out I had to open port 8880 .
    I found this answer here https://community.ubnt.com/t5/UniFi-Wireless/Problems-with-voucher-portal-not-displaying-on-UniFI-deployed-on/td-p/750698

  • Rod

    April 25, 2015 at 4:58 am

    Is it important to use the North Virginia region. When I’m at the instance creation, only US West (Oregon) region is available and I can not see anywhere to change it…

    • Justin

      April 25, 2015 at 5:01 am

      In the upper right hand corner next to your name.

      • Rod

        April 25, 2015 at 5:43 am

        Thanks Justin. I had actually got a fair way through when connected to Oregon, but I was not able to SSH using JAVA SSH client. That was not a displayed option…

  • Daniel

    April 26, 2015 at 5:06 pm

    Thanks for this great tutorial. Worked well. Love it! Thanks!

  • Michael

    April 30, 2015 at 12:35 pm

    Hi.

    I tryed to follow this guide, but got stuck at the SSH login part.
    I do not have the option to connect via JAVA SSH client. Ony remote
    desktop. And the RD does not work at all.
    I have updatet to latest Java on my PC.

    What am I doing wrong?

    Regards
    Michael.

  • John Kucera

    April 30, 2015 at 5:13 pm

    A few notes. When the instructions show:
    1: Then click on View Elastic IP. Next click Associate Address. As soon as you click in the Instance field, your new Instance should show up. Click it. Then Click Associate down in the corner.
    Here you have to make sure you see your new Instance, which you should have already named in the Instance field. You may have to wait a little until it shows up, but then select it then Click Associate.
    2. When requesting to download the UniFi Discovery tool, after downloading make sure you actually open the UniFi Discovery tool on the local PC. (I kept trying to find manage with the Unifi Controller which was my problem). Also please note, that if you already have the UniFi Controller already associated with the access points on site, you will HAVE TO either use the rest button on the WAP, or using the UniFi Controller, Forget This Access Point option in Devices under each WAP. Then you can change the settings in the UniFi Discovery Tool. Note this is how I did it and all my settings for each WAP were lost so I would try first the rest button on the device as instructions say it will not lose those settings when you reset.

    On another note, thanks for the instructions as the older ones since everything had changed I could never use the service…

  • Benjamin

    May 4, 2015 at 10:23 am

    I am not able to find the link on the download page to download the discovery tool.

    • Benjamin

      May 4, 2015 at 11:38 am

      all good using putty to do it instead and makes it easy too. thank you for the guide above, has helped a lot

  • Ron

    May 12, 2015 at 10:05 pm

    Thanks for the great instructions. I am a novice at virtual services and you made it easy.

  • Fabian Toro

    May 13, 2015 at 3:35 pm

    Gracias por la informacion

  • Richard

    May 18, 2015 at 11:27 am

    Good Afternoon Justin, I have setup my instance a few months ago and it works well, I then came to update using step 3 and I get this error? and pointers for me?

    apt-get install unifi-beta
    Reading package lists… Done
    Building dependency tree
    Reading state information… Done
    The following packages will be upgraded:
    unifi-beta
    1 upgraded, 0 newly installed, 0 to remove and 130 not upgraded.
    Need to get 187MB of archives.
    After this operation, 147kB of additional disk space will be used.
    E: You don’t have enough free space in /var/cache/apt/archives/.

  • cbp@outlook.com

    June 8, 2015 at 5:18 pm

    Let me share that after digging the net I found a way to log into AWS Ubuntu as root. This allows you to upload your custom portal easily with filezilla: http://ram.kossboss.com/ubuntu-loginenable-root-user-normal-ubuntu-amazon-ec2/

  • dru.clifton@innovatedns.com

    June 11, 2015 at 6:01 pm

    How do you get the the WWW, WAN, LAN to go green on the Dashboard, rather than being gray? When using a 3rd party Hardware, like CIsco

    • Joshua Edman

      June 11, 2015 at 9:48 pm

      Those require the Ubiquiti USG units otherwise they will stay gray.

  • john@carnsorebroadband.com

    June 25, 2015 at 5:17 pm

    Thanks for the great walkthrough. It worked and all my APs are up and running. I want to set the system
    up in hotspot mode and make a stripe payment gateway, the option does not seem to be available with
    the controller version installed is it possible to upgrade to 3.2.10 which seems to be the latest controller version any help here would be appreciated.

    • Justin

      June 25, 2015 at 5:27 pm

      Thanks John. If you followed the walkthrough, then you are probably running beta version 4.6.3 which is the latest available.

  • martin57290@gmail.com

    July 14, 2015 at 7:42 am

    4.6.6 has been out for a couple of weeks and this upgrade command says no upgrade available.. Is there a different upgrade command? Thanks

    • Justin

      July 14, 2015 at 12:28 pm

      The file is located in a different location now, use deb http://www.ubnt.com/downloads/unifi/debian stable ubiquiti

  • Justin

    July 14, 2015 at 12:32 pm

    Part 4 has been updated to reflect the changes that came with 4.6.6

    • martin57290@gmail.com

      July 15, 2015 at 8:40 pm

      Great Thank you!

  • ajones@wehandleit.com

    August 20, 2015 at 8:19 pm

    Thank you, so much! This was so helpful! You might want to update the instructions for Part 1 relating to where it pulls the apt-get from. Just in case anyone knows, I’m having trouble now with my clients using the URL redirect feature on their Guest WiFi. It connects, gets an IP, etc. but the Internet won’t work

  • shaneklaas@hotmail.com

    August 21, 2015 at 2:37 am

    Thanks for these great instructions! I am having one challenge I hope you can help me with. I followed your instructions, but the Controller did not update to the new one. I then followed step 4 and it at first looks like the new version, but I cannot log in. I enter my credentials then press “Login” and after a few seconds the screen refreshes and it asks for my login again. HELP! I have terminated that instance 3 times and retried this 3 times to no avail.

    • Justin

      August 21, 2015 at 3:12 am

      I will update the instructions to reflect some changes.

    • Justin

      August 21, 2015 at 3:16 am

      Ok, its updated to reflect changes from 4.6.6 in Part 1

      • mail@wachs.org

        September 3, 2015 at 12:15 am

        Well, for one, this tutorial is fantastic! Got the instance up and running and it’s a duplicate of the controller I had running at home. However, I seem to have the same issue trying to provision an AP. I “forgot AP” in my old controller. I then launched the UniFi discover utility. Found my AP, did a factory reset on it, re logged in and changed my inform URL to: https://52.22.120.xxx:8080/inform

        It now shows as “Pending” in the discovery utility but it never shows up in the controller. I SSH’d into the AP and set the inform that way. No change. I tried “http” and “https” but neither work. I can log into my controller via the web just fine. Everything seems to be working but the provisioning.

        A few others have had the same comments here. What did they do to fix it??

        • Joshua Edman

          September 3, 2015 at 12:18 am

          My personal guess would be that you should restart the Access Point and try again. I ran into something similar today actually as I was setting up our Cloud-Hosted Service.

        • mail@wachs.org

          September 3, 2015 at 12:32 am

          Ugh…. Had a ds-nat rule in my firewall for port 8080. Pulled that and it works. Doh!

  • satheesh@exeqt.org

    January 28, 2016 at 5:09 pm

    Thank you for the walkthrough. Can you explain a little about two things I’d like to know:

    1. Backup of the installation
    2. How to move a site from an already existing controller.

    Thanks in advance!

    • Justin

      January 28, 2016 at 10:36 pm

      In the controller under settings>maintenance is where you can find the ability to backup the controller. There are a couple ways of transferring devices to a new controller, but the easiest is just by defaulting them as I mentioned in the above tutorial. There are other ways, but I have heard people having trouble trying them. I have personal been successful with accessing the username and password from the existing controller and using that to remanage the devices to the new controller.

      • satheesh@exeqt.org

        January 29, 2016 at 6:43 am

        I was maybe a little unclear about the backup, but I meant the virtual instance itself. Although I haven’t really seen anywhere how to restore a UniFi backup file.

        So the only way is to make a new site on the new controller (config, networks, settings, etc), reset/default the UniFi device and lastly adopt it to the new controller. I was hoping I didn’t have to redo all the site configurations somehow.

        Or am I missing something? I wish you could adopt the device and it would create a site with the configuration from the device itself.

        Thanks again for your help btw.

  • satheesh@exeqt.org

    February 5, 2016 at 9:44 pm

    UniFi – 4.8.12 is released by the way. I tried updating, but I got a lot of errors. Luckily I created a snapshot beforehand and was able to mount back the volume.

    Anyone tried to upgrade it to the newest version?

Leave a Comment

You must be logged in to post a comment. Click here to login.

Welcome to the Dash OS Blog! TCL Commands