Guide: How to run UniFi Controller on the Firewalla Gold

Follow

Comments

76 comments

  • Avatar
    theroninhunter

    Neither of those are options unfortunately, seems to be running fine currently. I'll keep an eye on it.

    0
    Comment actions Permalink
  • Avatar
    Glazer

    I can confirm Mariusz' experience. I had the UniFi controller running on my Purple for a little over a month. The first week went okay, but as I moved additional devices to my UniFi setup, the Purple froze more and more often. At the end I had to restart once a day. Since I moved the controller to a Cloud Key a week ago, the Purple has been stable again.

    So while it is possible to run the UniFi controller on the Purple, I would not recommend it.

    0
    Comment actions Permalink
  • Avatar
    Kenneth Conroy

    I was able to get this running just fine (with the caveat that it seems to only listen to http://www.unifi:8080 and not http://unifi:8080/.)  The github page for jacobalberty/unifi recommends running it in user mode by setting the docker run flag --user to unifi. This is my first time going anywhere near Docker.  How do we do that in Firewalla?  Or does Firewalla already handle this for us by default?

    0
    Comment actions Permalink
  • Avatar
    Abbas Jaffar Ali

    Trying to remove as many devices as I can and finally got around to moving the UniFi controller on my FWG.

    I have set up and moved all my UniFi devices and its all working great. But at step 5, I get an error. It can't create that file.

    ~/.firewalla/config/post_main.d/start_unifi.sh" E212: Can't open file for writing

    0
    Comment actions Permalink
  • Avatar
    Blake

    Try creating the file using a text editor on your computer, and then dropping it into that folder using an FTP client.  I found that method much easier since I don't really know linux well at all.

    0
    Comment actions Permalink
  • Avatar
    Stephen Neish

    A youtube tutorial of this would be super helpful

    0
    Comment actions Permalink
  • Avatar
    Michael Bierman

    @Abbass did you create the directory first? 

    @Stephen I don’t have a video, but I created a script that does pretty much everything for you. /github.com/mbierman/unifi-installer-for-Firewalla

    1
    Comment actions Permalink
  • Avatar
    Stephen Neish

    @michael, that made it way too easy.  Thank you

    1
    Comment actions Permalink
  • Avatar
    Abbas Jaffar Ali

    @Michael Bierman - I did but that didn't help. I've just left that last bit hoping I never have to restart my FWG. And if I do, then I'll manually start the UniFi controller. Not related but I've been eyeing the new Eero POE points. Who knows- I might replace my UniFi devices with that.

    0
    Comment actions Permalink
  • Avatar
    Michael Bierman

    @abbas, there is an uninstall script too. No reason not to run it properly. 

    honestly, Unifi is so much better than eero, I don’t know why someone would switch in that direction.

    0
    Comment actions Permalink
  • Avatar
    Aaron H

    I am not able to access the Unifi GUI in a browser, and pings from my computer time out. I can ping 172.16.1.2 from my Firewalla with no issues and I've added the routing rules as prescribed. 
    I also tried uninstalling and reinstalling using your script and everything comes up just as before, but still no access to the Unifi controller from the network.
    My main network is 192.168.1.0/24 .... Should I use that as the docker's network instead of the one used in this tutorial? 

    Any help is appreciated

    0
    Comment actions Permalink
  • Avatar
    Michael Bierman

    @Aaron,

    Try ssh to firewalla and then run this:

    sudo docker ps

    that will tell you if unifi is really running. If it is, try

    https://172.16.1.2:8443

    You need to specify the port. You will probably see a message about it not being secure and you have to accept that. 

    If you haven't put any rules in place, this should work. 

    0
    Comment actions Permalink
  • Avatar
    Blake

    Did you specify the port like this: https://172.16.1.2:8443/

    0
    Comment actions Permalink
  • Avatar
    Aaron H

    @Blake yes, I entered the IP and port exactly like that. I also tried http://172.16.1.2:8080/ and https://unifi:8443/ and http://unifi:8080. No hosts on my network are able to ping anything on Docker's 172.16.1.0/24 subnet. Only the FWG can reach it.

    I was able to use the Unifi controller when deployed to a portainer instance running on another server in the network. In that use case, the web app is accessed through Portainer's IP and :8443.

    Does this suggest something wrong with my application of the "ip route" command after the docker has been launched?

    0
    Comment actions Permalink
  • Avatar
    Michael Bierman

    @aaron did you modify the yaml file at all or use it asis? 

    0
    Comment actions Permalink
  • Avatar
    Aaron H

    @michael I copy/pasted your yaml as well as trying the uninstall/install scripts when it didn’t work the first time. In any case, ‘sudo docker ps’ shows unifi running with the correct IP.

    Just in case I had a rule in place preventing access, I ungrouped the PC im using to configure this, enabled emergency access in it, and am connected to the management vlan.

    Still unable to access it unfortunately. I’m currently running the controller from my portainer server but would definitely prefer to use the FWG for this if I can figure it out

    0
    Comment actions Permalink

Please sign in to leave a comment.