How to install the Ubiquiti UniFi Controller on Debian 9.1
-
@jaredbusch said in How to install the Ubiquiti UniFi Controller on Debian 9.1:
@bigbear said in How to install the Ubiquiti UniFi Controller on Debian 9.1:
Trying to update the thing with sudo so and then upgrade - firmwarelink and it says upgrade is an invalid command?
You have a USG? It had to be adopted to a controller already. Or is this a new USG? One of the things I hate about the USG is initial adoption sucks balls.
Got a new USG, the other site I setup I ended up giving up and deploying on a local machine. Setup a cloud Unifi controller, updated the new USG firmware, tried to set inform URL - just not showing up on the remote cloud controller at all. Not showing up in the apps either (chrome and ios app)
-
@bigbear said in How to install the Ubiquiti UniFi Controller on Debian 9.1:
@jaredbusch said in How to install the Ubiquiti UniFi Controller on Debian 9.1:
@bigbear said in How to install the Ubiquiti UniFi Controller on Debian 9.1:
Trying to update the thing with sudo so and then upgrade - firmwarelink and it says upgrade is an invalid command?
You have a USG? It had to be adopted to a controller already. Or is this a new USG? One of the things I hate about the USG is initial adoption sucks balls.
Got a new USG, the other site I setup I ended up giving up and deploying on a local machine. Setup a cloud Unifi controller, updated the new USG firmware, tried to set inform URL - just not showing up on the remote cloud controller at all. Not showing up in the apps either (chrome and ios app)
Weird, you did all the right things. Never had a problem with set-inform. Just feel it is a pain in the ass.
-
@jaredbusch said in How to install the Ubiquiti UniFi Controller on Debian 9.1:
@bigbear said in How to install the Ubiquiti UniFi Controller on Debian 9.1:
@jaredbusch said in How to install the Ubiquiti UniFi Controller on Debian 9.1:
@bigbear said in How to install the Ubiquiti UniFi Controller on Debian 9.1:
Trying to update the thing with sudo so and then upgrade - firmwarelink and it says upgrade is an invalid command?
You have a USG? It had to be adopted to a controller already. Or is this a new USG? One of the things I hate about the USG is initial adoption sucks balls.
Got a new USG, the other site I setup I ended up giving up and deploying on a local machine. Setup a cloud Unifi controller, updated the new USG firmware, tried to set inform URL - just not showing up on the remote cloud controller at all. Not showing up in the apps either (chrome and ios app)
Weird, you did all the right things. Never had a problem with set-inform. Just feel it is a pain in the ass.
Ironically what just worked, in an instant was setting the inform-url for SSH. Showed up instantly...
-
well, At least its "adopting".. fingers crossed
-
In SSH, I went back and did a set-inform again (as the first time it gave this feedback below) then in about 10 seconds it started provisioning...
So maybe that is the best way to hard set it?
Adoption request sent to 'http://x.x.x.x:8080/inform'.
- please adopt it on the controller
- issue the set-inform command again
- <inform_url> will be saved after device is successfully managed
-
@bigbear said in How to install the Ubiquiti UniFi Controller on Debian 9.1:
In SSH, I went back and did a set-inform again (as the first time it gave this feedback below) then in about 10 seconds it started provisioning...
So maybe that is the best way to hard set it?
Adoption request sent to 'http://x.x.x.x:8080/inform'.
- please adopt it on the controller
- issue the set-inform command again
- <inform_url> will be saved after device is successfully managed
This is always how I do it with any UniFi device that needs manually pointed to the controller.
-
Now that the controller has taken over I lost my second WAN port. Christ...
-
@bigbear said in How to install the Ubiquiti UniFi Controller on Debian 9.1:
Now that the controller has taken over I lost my second WAN port. Christ...
Dual WAN? I would never even attempt to use a USG in that scenario. Not even sure it can.
-
Second LAN port, typo...
I was using the lan/wan as a second port and once provisioning USG decided it would be disabled.
-
When I run this command
apt-key adv --keyserver keyserver.ubuntu.com --recv 06E85760C0A52C50
I get this message:-
Executing: /tmp/apt-key-gpghome.8Iu0CA5dVp/gpg.1.sh --keyserver keyserver.ubuntu.com --recv 06E85760C0A52C50 gpg: keyserver receive failed: No keyserver available
-
Maybe should add installing on Debian9 (followed Jared's guide) on internal VM internally.
-
@hobbit666 said in How to install the Ubiquiti UniFi Controller on Debian 9.1:
Maybe should add installing on Debian9 (followed Jared's guide) on internal VM internally.
Did you run this as root or use sudo?
-
@jaredbusch ur yes lol.
-
@jaredbusch
SSH into my server via putty. Logged in as the user unifi01 when at the prompt did thesu -
ran all the commands above but had the error on the key import.
I'll try running direct on the VM console.
-
Still the same on console
-
@hobbit666 said in How to install the Ubiquiti UniFi Controller on Debian 9.1:
Still the same on console
Very odd as it works jsut fine for me even with sudo.
jbusch@deb9-demo:~$ sudo apt-key adv --keyserver keyserver.ubuntu.com --recv 06E85760C0A52C50 [sudo] password for jbusch: Executing: /tmp/apt-key-gpghome.DyMKqzXPlf/gpg.1.sh --keyserver keyserver.ubuntu.com --recv 06E85760C0A52C50 gpg: key 06E85760C0A52C50: "UniFi Developers <[email protected]>" not changed gpg: Total number processed: 1 gpg: unchanged: 1 jbusch@deb9-demo:~$
-
@hobbit666 let me blow this system back to snapshot and do it again.
Side note: I said to
su -
to root because you cannotcat
the apt list file fromsudo
and there are so few commands to set this up. Technically it can all be done from your user withsudo
if you usenano
orvi
to create the list file. -
SOLVED!!!!
Changed the router, firewall must of been blocking. -
When using Vultr is it just https://unifi.hostname.vultr.com:8443 ?
-
@ccwtech said in How to install the Ubiquiti UniFi Controller on Debian 9.1:
When using Vultr is it just https:\unifi.hostname.vultr.com:8443 ?
If you have a vultr hostname then yes, otherwise you create a DNS record pointing to your Vultr WAN IP.