Jump to content

Looking for some help


G+_Jason Perry
 Share

Recommended Posts

Looking for some help. I am setting up a unifi controller on digital ocean following the guide on crosstalk Solutions YouTube page and I have hit a wall. I configured Ubuntu and installed the controller, but when I go to the site I get a connection refused error. I have tried with the url and the IP address as well as with and without the firewall. Any suggestions?

Link to comment
Share on other sites

Right now I am at work and didn't get chance to upload my rsa key to my phone so I am going to have to try playing with settings on the server when I get home

 

So far I have tried

https://unifi.url.com:8443 (connection refused)

http://unifi.url.com:8443 (connection refused)

https://unifi.url.com (timed out)

http://unifi.url.com (timed out)

Link to comment
Share on other sites

Jason Perry Just took a look at what Digital Ocean was and it looks very interesting. Am I guessing you got this working on hardware local to your site? Is it Digital Ocean or some change made to the software by Unifi?

I know my last update I can no longer log in and download the beta software for viewing the timeline. Here is the error I get. I am set up on a laptop locally.

23512%20-%20failedUpgradeUnifi2.png

Link to comment
Share on other sites

Jason Perry Making progress at least. Does going to https://IP:8443 show anything? Also might want to run an nmap scan on the server.

 

I actually just setup a controller in my home lab yesterday and didn't have an issue with it, but I also haven't gotten any APs imported yet. I wonder if the instructions you used were out of date, or just wrong.

Link to comment
Share on other sites

So going over the setup I followed here is what I did differently.

I did not obviscate the ssh port

I did not specify my wan IP address because I have a dynamic IP and don't want to lock myself out. Ports that he tied to an IP were 22 and 8443

 

I also noticed he doesn't have IPv6 rules for ports 22 and 8443

 

And now that I went through the instructions again it still doesn't work. Boohttps://plus.google.com/photos/112174847498581086778/albums/6574870963320794769/6574870965037145970

Link to comment
Share on other sites

i just ran 'systemctl status unifi' and this is what i am up against

 

? unifi.service - unifi

Loaded: loaded (/lib/systemd/system/unifi.service; enabled; vendor preset: enabled)

Active: inactive (dead) since Thu 2018-07-05 23:19:21 UTC; 13s ago

Process: 5090 ExecStop=/usr/lib/unifi/bin/unifi.init stop (code=exited, status=0/SUCCESS)

Process: 4975 ExecStart=/usr/lib/unifi/bin/unifi.init start (code=exited, status=0/SUCCESS)

 

Link to comment
Share on other sites

Jason Perry That line with 'Active: inactive (dead)' tells us the service isn't running, so, yeah. Won't work so well.

 

Are you comfortable installing and securing a base OS? I used Debian Sarge as a base, and then just used the installation instructions from Ubiquiti. help.ubnt.com - UniFi - How to Install & Update via APT on Debian or Ubuntu

 

I use Wazuh, even for my personal stuff, which takes care of a BUNCH of stuff for you on the client, but is a bit of a pain to setup. Fail2ban and ufw should be the only things you really need after getting a base OS installed. Or just fail2ban if using Fedora (I shy away from CentOS because of how old and slow most of the software in it's repos is today, and yes, that reflects RedHat's current status as well.)

Link to comment
Share on other sites

David Alitz thanks. Do you remember what was causing the problem with mongodb?

 

I think my biggest problem is, I am still very much a novice. I have done plenty of Ubuntu installs and I have followed plenty of people's instructions; but, I haven't sat down and learned why commands do what they do or what tags go with them.

Link to comment
Share on other sites

Sorry I am not familiar with how you are trying to setup Unifi controller software but will contribute this; have not been able to download any firmware updates since 3.9.6.

Might be totally unrelated but thought I would offer it up. Good luck.

Link to comment
Share on other sites

I'm afraid I don't recall what was causing mongodb to fail. I have a vague recollection of having the default ubuntu version installed instead of the unifi ppa version -- but that could just be one of the paths I investigated.

You can check the mongodb status with 'systemctl status mongodb'

Link to comment
Share on other sites

quick update for anyone following along.

 

the unifi controller hasn't even created a log file so nothing to go from there.

 

I looked at the log file for mongodb and noticed the line

got signal 15 (Terminated), will terminate after current cmd ends

I am going with this is my problem and am going from there.

Link to comment
Share on other sites

 Share

×
×
  • Create New...